Merge pull request #157 from checkly/docs/coralogix-metrics-clarification

docs: clarify metrics not included in Coralogix integration

Author: tdehan86

integrations/observability/coralogix.mdx

@@ -58,6 +58,18 @@ ingested into Coralogix as traces.
 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.
 
+### What's included
+
+- Traces for every check execution
+- HTTP request instrumentation with W3C headers
+- Trace correlation metadata
+
+<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.
+</Note>
+
 ## RUM integration
 
 In addition to the Open Telemetry tracing, Checkly can also send RUM data to Coralogix for all Browser checks. This enables
@@ -105,4 +117,4 @@ of your Coralogix dashboard. Copy and paste the API key.
 `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**.
 
-![coralogix integration step 4](/images/docs/images/integrations/coralogix/coralogix_step4.png)
+![coralogix integration step 4](/images/docs/images/integrations/coralogix/coralogix_step4.png)