Skip to main content
Checkly connects to Coralogix in three ways. Each one works on its own.
  • OpenTelemetry tracing: every API check, URL monitor, Browser check and Multistep check run arrives in Coralogix as a trace, linked from the check result page.
  • RUM: Browser checks and Multistep checks send Coralogix RUM data labeled Checkly: true, so you can compare synthetic and real users.
  • Alert channel: your Checkly alert notifications arrive in Coralogix Logs.

​
OpenTelemetry tracing

  • A plan that includes the Coralogix integration.
  • A Coralogix account where you can create Send-Your-Data API keys.
  1. In Coralogix, create a Send-Your-Data API key under Settings > Users and Teams > API Keys. See the Coralogix API keys documentation.
  2. In Checkly, open Settings > Integrations and click Add Coralogix integration.
  3. Pick the region of your Coralogix tenant and enter your team name. The region selects the ingest endpoint. The team name only builds the permalink shown on the check result page.
  4. Select Enable sending traces to Coralogix, paste the API key and save the integration.
Coralogix integration form in Checkly Export to Coralogix depends only on the Coralogix integration being enabled. Import Traces and Export Traces on Settings > Traces do not need to be on. Checkly adds traceparent and tracestate headers to the requests your checks make, so spans from your instrumented backend join the same trace. The OTLP page documents both headers. Checkly traces in the Coralogix Tracing view The check result page shows the trace ID and a permalink to the trace in Coralogix. Coralogix trace link on a Checkly check result

​
What is sent

Exported spans carry the checkly.* attributes documented on the OTLP page: checkly.account.id, checkly.check.id, checkly.check.result.id, checkly.check.name, checkly.check.type, checkly.check.runtime, checkly.check.session.id, checkly.check.location, checkly.check.tags and checkly.check.status. It also carries two Coralogix resource attributes: When the Coralogix integration and the generic export on Settings > Traces are both on, these cx.* resource attributes may also reach your generic endpoint from API checks, URL monitors, Browser checks and Multistep checks.

​
Custom trace header

If your backend reads a header other than traceparent, set its name in the Custom trace header field. When it is set, API checks and URL monitors send the custom header instead of traceparent, even when the generic OTLP export is also on, so backend spans no longer join those check runs by traceparent. Browser checks and Multistep checks send both headers unless every enabled export has a custom header.
Check metrics, such as response times and availability, are not sent through this integration. To get them into Coralogix, scrape the Prometheus endpoint and forward the metrics with an OpenTelemetry Collector.

​
RUM

With RUM enabled, Checkly injects the Coralogix RUM SDK into your Browser checks and Multistep checks. Their RUM data reaches Coralogix with the label Checkly: true. Coralogix RUM settings in Checkly
  1. In Coralogix, create a Send-Your-Data API key with the SendRUMData role preset under Settings > Users and Teams > API Keys. The Coralogix RUM documentation covers the Coralogix side. RUM integration keys in Coralogix
  2. In the Coralogix integration in Checkly, select Enable Coralogix RUM and pick the RUM Region of your tenant.
  3. Set the RUM application name to the application your checks target, for example my-website.
  4. Paste the key into RUM API key and save the integration.
You do not need to install the RUM SDK in your application or upload source maps. If your application already loads the Coralogix RUM SDK, the injected copy skips its own initialization. If your checks target several applications, set the environment variable CORALOGIX_RUM_APP_NAME on a check to override the application name for that check.

​
Alert channel to Coralogix Logs

Coralogix can receive your alert notifications as logs. This alert channel works without the tracing and RUM integrations.
  1. In Checkly, go to Alert channels, click + Add more channels (New alert channel if you have none yet), find Coralogix and click Add channel.
Coralogix in the Checkly alert channel list
  1. In Coralogix, create a Send-Your-Data API key under Settings > Users and Teams > API Keys. Paste it into the channel form.
  2. Name the channel and enter the Coralogix Logs API endpoint for your region, for example https://ingress.eu2.coralogix.com/logs/v1/singles. Make sure the right checks subscribe to the channel and the Send when rules fit, then click Save Coralogix webhook.
Coralogix alert channel settings in Checkly