Skip to content

Conversation

@tijmenbruggeman
Copy link
Collaborator

@tijmenbruggeman tijmenbruggeman commented Jan 6, 2026

We had two customers reporting two different issues which we could not figure out. Often times this is due to setup configurations but it is hard to figure out.

Having some diagnostics and logs should make it easier to troubleshoot these issues.

This PR will also:

  • set the timeout for the entire request to 120 seconds
  • set the timeout to connect to the server to 8 seconds

Good to know

  • Max 2MB log file, if limit is reached, old log will be deleted and new one will be created. This is the simplest method and prevents from adding rotation;
  • Turn on logs will clear any previous logs;
  • Requires ziparchive to download;
  • No sensitive data will be logged;
  • Logging will slow down performance as it will open and write the log entry each time something compresses;

Screenshots
Screenshot 2026-01-06 at 16 51 45
Customers can turn on logging and download a diagnostics zip file from within settings

image _Logs are formatted nicely_


// Set API request timeout to prevent indefinite hanging
$options[ CURLOPT_TIMEOUT ] = self::API_TIMEOUT;
$options[ CURLOPT_CONNECTTIMEOUT ] = self::API_TIMEOUT;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the connecttimeout should be shorter (like 10 seconds)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Currently set to 8. Let me know if this is okay.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants