Visualize how your website and API requests perform in a microservices-based application with the Trace details page.

When you run a check against your website or API, there are a few services that respond in your backend; normally, there’s at least a database, a cache, and a router. You can now analyze how a specific check performs in your backend as it flows through your internal services.

With Checkly Traces you can see exactly the PostgreSQL query that took longer than it should and which connection_string and statement it was using. When uploading files to an s3 bucket, you’ll see the exact socket connection that timed out.

Overall, you can access all the DB queries, attributes and details on the right side of your the Trace details page, coming from the Open Telemetry Instrumentation in your application.

Send the individual link to a given span to share the root cause of a failed check with your colleagues and they’ll open up the exact span selected in blue with the attributes on the right side:

Join our Slack community to discuss observability for your checks. We can help you setting up OpenTelemetry instrumentation for the first time and updating your OpenTelemetry Collector.

Happy monitoring!