1. Confirm the tracer is configured
The Go agent does not readATATUS_* environment variables on its own. Your application must read them and assign them to the tracer at startup:
main.go (or equivalent entry point) for this setup.
2. Check the environment variables are set
Make sure the following variables are exported in the shell, service file, or container that actually runs your application, not just in a local.env file that your process manager ignores:
A missing or incorrect
ATATUS_LICENSE_KEY is the most common reason no data shows up in the dashboard.3. Verify your routes are instrumented
Automatic instrumentation in Go only applies to the routes and handlers you explicitly wrap with the framework module (for exampleatgin.Middleware, athttp.Wrap, or the equivalent for your framework). A request to a route that is not wrapped will never appear as a transaction. See Routes or handlers not showing up as transactions to check this.
4. Sync your dependencies
After adding or updatinggo.atatus.com/agent and its framework module, run:
go.sum can cause the build to silently use a stale copy of the agent.
5. Enable debug logging
Set the agent’s log level todebug and point it at a writable log file:
6. Check your Go version
The Go agent supports Go 1.8 and above. If you are building with an older toolchain, upgrade Go before continuing.Still no data?
If you have gone through the steps above and still see nothing in the dashboard, send the following to success@atatus.com:- The agent log file from step 5.
- The framework or module you are using (Gin, net/http, gRPC, and so on).
- Your
go.modentries forgo.atatus.com/agentand its modules.