Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions communicate/dashboards/overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,8 @@ Dashboards allow you to do the following:
- Show the availability and p95 / p99 metrics over the last 24 hours, 7 days and 30 days.
- Communicate custom incident messages and maintenance messages.

To build dashboards in Grafana or another tool, scrape your check metrics from the [Prometheus endpoint](/integrations/observability/prometheus).

You can create multiple, distinct dashboards based on your plan. Edit your dashboard by clicking on
the **Dashboards** button on the Checkly dashboard page.

Expand Down
2 changes: 1 addition & 1 deletion detect/uptime-monitoring/heartbeat-monitors/overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,7 @@ Heartbeat monitors provide different metrics and insights than other types of ch
- **Alert Timeline**: When alerts were triggered and resolved
- **Source Tracking**: Which systems or processes sent pings

Heartbeat metrics are also available via the [Prometheus V2 integration](/integrations/observability/prometheus-v2#heartbeat-metrics), including dead man's switch gauges for alerting in Grafana when a ping is overdue.
Heartbeat metrics are also available via the [Prometheus integration](/integrations/observability/prometheus#heartbeat-metrics), including dead man's switch gauges for alerting in Grafana when a ping is overdue.

<Warning>
Remember: Heartbeat monitors detect when jobs fail to complete, but they can't tell you why a job failed. Combine heartbeat monitoring with application logging and error tracking for complete observability.
Expand Down
54 changes: 47 additions & 7 deletions docs.json
Original file line number Diff line number Diff line change
Expand Up @@ -344,10 +344,7 @@
{
"group": "Exporting",
"pages": [
"resolve/traces/export/grafana-tempo",
"resolve/traces/export/honeycomb",
"resolve/traces/export/new-relic",
"resolve/traces/export/dash0"
"resolve/traces/export/overview"
]
},
{
Expand Down Expand Up @@ -463,9 +460,28 @@
{
"group": "Observability",
"pages": [
"integrations/observability/prometheus",
"integrations/observability/prometheus-v2",
"integrations/observability/coralogix"
"integrations/observability/overview",
{
"group": "Metrics",
"pages": [
"integrations/observability/prometheus"
]
},
{
"group": "Traces",
"pages": [
"integrations/observability/traces/otlp",
"integrations/observability/coralogix",
"integrations/observability/traces/chronosphere",
"integrations/observability/traces/clickstack",
"integrations/observability/traces/cribl",
"integrations/observability/traces/dash0",
"integrations/observability/traces/datadog",
"integrations/observability/traces/grafana-tempo",
"integrations/observability/traces/honeycomb",
"integrations/observability/traces/new-relic"
]
}
]
},
{
Expand Down Expand Up @@ -2441,6 +2457,30 @@
"source": "/detect/synthetic-monitoring/playwright-checks/private-packages-and-internal-registries",
"destination": "/detect/synthetic-monitoring/playwright-checks/internal-registries"
},
{
"source": "/resolve/traces/export/grafana-tempo",
"destination": "/integrations/observability/traces/grafana-tempo"
},
{
"source": "/resolve/traces/export/honeycomb",
"destination": "/integrations/observability/traces/honeycomb"
},
{
"source": "/resolve/traces/export/new-relic",
"destination": "/integrations/observability/traces/new-relic"
},
{
"source": "/resolve/traces/export/dash0",
"destination": "/integrations/observability/traces/dash0"
},
{
"source": "/resolve/traces/export/to-chronosphere",
"destination": "/integrations/observability/traces/chronosphere"
},
{
"source": "/integrations/observability/prometheus-v2",
"destination": "/integrations/observability/prometheus"
},
{
"source": "/platform/rocky-ai",
Comment on lines +2482 to 2485

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Blocker: The merge dropped the end of this redirect object and the start of the next one. docs.json no longer parses, which fails the Mintlify deployment and static-docs-checks (Expected ',' or '}' after property value ... line 2483 column 7).

Suggested change
"destination": "/integrations/observability/prometheus"
"source": "/platform/rocky-ai",
"destination": "/integrations/observability/prometheus"
},
{
"source": "/platform/rocky-ai",

"destination": "/ai/rocky-ai"
Expand Down
Binary file modified images/docs/images/integrations/coralogix/cx_otel_int1.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified images/docs/images/otel/export-traces/dash0-token.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified images/docs/images/otel/otel_export_traces_settings.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
133 changes: 48 additions & 85 deletions integrations/observability/coralogix.mdx
Original file line number Diff line number Diff line change
@@ -1,121 +1,84 @@
---
title: 'Export Metrics & Data via Coralogix'
description: 'Deep integration with Coralogix for OpenTelemetry tracing, RUM monitoring, and alert notifications'
title: 'Send traces, RUM and alerts to Coralogix'
description: 'Send check runs to Coralogix as OpenTelemetry traces, add Coralogix RUM to Browser checks and Multistep checks, and send alerts to Coralogix Logs.'
sidebarTitle: 'Coralogix'
canonical: 'https://www.checklyhq.com/docs/integrations/observability/coralogix/'
---

Checkly deeply integrates with [Coralogix](https://coralogix.com/) in three ways:
Checkly connects to [Coralogix](https://coralogix.com/) in three ways. Each one works on its own.

1. Checkly can automatically instrument all check executions with **OpenTelemetry tracing** and send the data to Coralogix
as traces.
2. Checkly can automatically instrument your Browser checks with **Coralogix RUM (Real User Monitoring)**.
3. Checkly can send **alert notifications** when checks pass and/or fail to **Coralogix Logs**.
- **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 integration
## OpenTelemetry tracing

To set up the OpenTelemetry tracing integration, first enable the Coralogix integration in your Checkly account in the
[integrations section](https://app.checklyhq.com/settings/account/integrations).
<Accordion title="Prerequisites">
- A [plan](https://www.checklyhq.com/pricing/) that includes the Coralogix integration.
- A Coralogix account where you can create Send-Your-Data API keys.
</Accordion>

![coralogix otel integration](/images/docs/images/integrations/coralogix/cx_otel_int1.png)
1. In Coralogix, create a Send-Your-Data API key under **Settings > Users and Teams > API Keys**. See the [Coralogix API keys documentation](https://coralogix.com/docs/user-guides/account-management/api-keys/api-keys/).
2. In Checkly, open [Settings > Integrations](https://app.checklyhq.com/settings/account/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.

1. Pick the region of your tenant and enter the team name. We use this to determine the correct trace ingest endpoint for Coralogix.
2. Create a "Send Your Data" API key in your Coralogix account, you can find these in the **Data Flow > API Keys** section
of your Coralogix dashboard. Copy and paste the API key.
![Coralogix integration form in Checkly](/images/docs/images/integrations/coralogix/cx_otel_int1.png)

The integration is now active and Checkly will start doing two things
Export to Coralogix depends only on the Coralogix integration being enabled. Import Traces and Export Traces on [Settings > Traces](https://app.checklyhq.com/settings/account/traces) do not need to be on.

1. Send a trace for every check run to Coralogix.
2. Instrument all HTTP requests generated by the check with the following headers:
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](/integrations/observability/traces/otlp#trace-headers) documents both headers.

| Header | Value | Description |
|---------------|------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------|
| `traceparent` | `{version}-{trace_id}-{span_id}-{trace_flags}` | A trace parent ID in [the canonical w3c format](https://www.w3.org/TR/trace-context/#traceparent-header-field-values) |
| `tracestate` | `checkly=true` | A vendor specific header so you can recognize traces originating from Checkly |
![Checkly traces in the Coralogix Tracing view](/images/docs/images/integrations/coralogix/cx_otel_int2.png)

![coralogix checkly traces in coralogix](/images/docs/images/integrations/coralogix/cx_otel_int2.png)
The check result page shows the trace ID and a permalink to the trace in Coralogix.

Moreover, it will show a **trace ID** and a **permalink** to the recorded trace in the check result page, so you can easily
correlate the check run with the trace in Coralogix.
![Coralogix trace link on a Checkly check result](/images/docs/images/integrations/coralogix/cx_otel_int3.png)

![coralogix link in checkly result](/images/docs/images/integrations/coralogix/cx_otel_int3.png)
### What is sent

Each trace will have the following metadata added to it as **tags**:
Exported spans carry the `checkly.*` attributes documented on the [OTLP page](/integrations/observability/traces/otlp#what-is-sent): `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:

| Tag | Description |
|----------------------------|---------------------------------------------------------------|
| `checkly.account.id` | The ID of the Checkly account the check belongs to. |
| `checkly.check.id` | The ID of the Checkly check that generated the trace. |
| `checkly.check.name` | The name of the Checkly check that generated the trace. |
| `checkly.check.type` | The type of the Checkly check that generated the trace. |
| `checkly.check.runtime` | The runtime ID of the Checkly check that generated the trace. |
| `checkly.check.session.id` | The unique ID of the check session the check belongs to. |
| `checkly.check.result.id` | The unique result ID of the check run. |
| `checkly.check.location` | The location ID of where the check was run, i.e. `us-east-1`. |
| Attribute | Value |
|---|---|
| `cx.application.name` | `checkly-<type>-check` |
| `cx.subsystem.name` | `<type>-check` |

Using these tags, you can create filters, dashboards and slice & dice your Checkly data as your runs are executed and
ingested into Coralogix as traces.
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.

If you are using a different trace header than the standard `traceparent`, you can configure this header in the *custom
trace header* field in the integration settings.
### Custom trace header

### What's included

- Traces for every check execution
- HTTP request instrumentation with W3C headers
- Trace correlation metadata
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.

<Note>
Check **metrics** (response times, availability, etc.) are not sent through this integration. To send these metrics
to Coralogix, scrape them via the [Prometheus integration](https://www.checklyhq.com/docs/integrations/observability/prometheus-v2/)
and forward to Coralogix using an OpenTelemetry Collector.
Check metrics, such as response times and availability, are not sent through this integration. To get them into Coralogix, scrape the [Prometheus endpoint](/integrations/observability/prometheus) and forward the metrics with an OpenTelemetry Collector.
</Note>

## RUM integration

In addition to the OpenTelemetry tracing, Checkly can also send RUM data to Coralogix for all Browser checks. This enables
tracking your Playwright-powered checks to be recorded as (semi) real users, so you can compare and contrast the performance
between synthetic and real users.

![coralogix rum integration](/images/docs/images/integrations/coralogix/cx_rum_int1.png)

1. Click **Enable Coralogix RUM** and pick the region of your tenant.
2. Set the global name of the application you will be targeting with your checks, e.g. "Acme webshop".
3. Create a new RUM integration in your Coralogix account via **Data Flow > Integrations > Real User Monitoring**

![rum api key area](/images/docs/images/integrations/coralogix/cx_rum_api_creation.png)

4. You will need to create an **Integration Key** and a **SourceMap Upload Key**.
Copy and paste the integration key into Checkly.

> Only the integration key is needed for the Checkly integration.
## RUM

5. As Checkly automatically injects the Coralogix RUM SDK to each Browser check run, uploading and setting up the SourceMap is not required. You can **skip** the **Install & setup Browser SDK Package** step and finish the set up there.
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`.

If you are targeting multiple applications with your checks, you can override the global application name by adding the
environment variable `CORALOGIX_RUM_APP_NAME` to your Browser check. You can find the Browser check specific environment
variables under **Settings** > **Environment variables** in the Browser check editor.
![Coralogix RUM settings in Checkly](/images/docs/images/integrations/coralogix/cx_rum_int1.png)

After enabling the RUM integration, Checkly will start sending RUM data to Coralogix for all Browser checks.
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](https://coralogix.com/docs/user-guides/rum/sdk-installation/javascript/npm-browser/) covers the Coralogix side.
![RUM integration keys in Coralogix](/images/docs/images/integrations/coralogix/cx_rum_api_creation.png)
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.

> Note that you do not need to install the RUM SDK in your application, Checkly will automatically inject the necessary
> JavaScript snippet into your Browser checks. However, if you have installed the SDK we will use the existing installation and not inject the snippet.
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.

## Alert channel → Coralogix Logs integration
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.

You can set up Coralogix as an alert channel destination, so Coralogix receives any alert notifications you have set up as logs.
Note that you can use this integration separately from the other two integrations mentioned above.
## Alert channel to Coralogix Logs

1. In Checkly, navigate to [alert settings](https://app.checklyhq.com/alerts/settings/). Click the **Add more channels**
button, find Coralogix on the list, and click **Add channel**.
Coralogix can receive your alert notifications as logs. This alert channel works without the tracing and RUM integrations.

![coralogix alert channels](/images/docs/images/integrations/coralogix/coralogix_alert_channels.png)
1. In Checkly, go to [Alert channels](https://app.checklyhq.com/alerts/settings), click **+ Add more channels** (**New alert channel** if you have none yet), find Coralogix and click **Add channel**.

2. Create a "Send Your Data" API key in your Coralogix account, you can find these in the **Data Flow > API Keys** section
of your Coralogix dashboard. Copy and paste the API key.
![Coralogix in the Checkly alert channel list](/images/docs/images/integrations/coralogix/coralogix_alert_channels.png)

2. Give your channel a name, and provide the correct Coralogix Logs API endpoint for the appropriate region, e.g.
`https://ingress.eu2.coralogix.com/logs/v1/singles` Make sure that the right checks are subscribing to the channel and
that the **Send when** rules are correctly set, then hit **Save Coralogix Webhook**.
2. In Coralogix, create a Send-Your-Data API key under **Settings > Users and Teams > API Keys**. Paste it into the channel form.
3. 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 integration step 4](/images/docs/images/integrations/coralogix/coralogix_step4.png)
![Coralogix alert channel settings in Checkly](/images/docs/images/integrations/coralogix/coralogix_step4.png)
Loading
Loading