Skip to main content
Each AgentCat SDK can write a log that shows whether track() worked, whether each event reached AgentCat, and why a send failed. The log is the fastest way to check a new setup or to find out why events do not show up in the dashboard. The SDKs never write their log to stdout, because stdout carries the JSON-RPC messages of a stdio server.

The log in each language

Most SDKs always write their log, so they have no debug option. Three SDKs write a log file only when you turn it on:

Reading the log file

You can follow the log while your server runs:
Each reference page lists the useful log lines of its SDK. The “Testing your setup” section of each setup page shows which line confirms that an event reached AgentCat.

When the log helps

The log is useful when:
  • Events do not show up in the AgentCat dashboard
  • You want to verify that tracking is set up correctly
  • You need to confirm that user identification works
  • You troubleshoot exporter or delivery issues
In Python, Go, and Ruby, we recommend the log file for development and troubleshooting, and leaving it off in production to save disk writes.