docs: clarify metrics not included in Coralogix integration #157
Conversation
Add 'What's included' section listing traces, HTTP instrumentation, and correlation metadata. Add note clarifying that metrics are not included and linking to Prometheus integration for metrics export.
tdehan86
requested review from
Dgiordano33,
Dnhem and
ragog
and removed request for
Dgiordano33
guolau
left a comment
guolau
left a comment
There was a problem hiding this comment.
Thanks Thomas! Good thing to clarify for this integration. I left a few small nits 🙂
| 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. |
There was a problem hiding this comment.
Should this line be moved to above the "What's included" section (to line 57)? Seems like it's separated from the relevant section currently
There was a problem hiding this comment.
This still needs to be moved up, I think?
| 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. | ||
|
|
||
| ### What's included |
There was a problem hiding this comment.
Should this content be at the beginning of the "Open Telemetry tracing integration" section?
It seems like we're just summarizing what the Coralogix OTel integration includes. I feel like it makes more sense to have this at the beginning of the section (so users can skim and see what's included) rather than at the end?
There was a problem hiding this comment.
The idea is to make sure customer understand what level f integration he will get from default CX integration
There was a problem hiding this comment.
Fair enough 🙂 I still think it would be better at the start of this section, but not a strong preference either way. Feel free to resolve this comment.
Make sens to keep names closer to what we have Co-authored-by: Laura Guo <48332483+guolau@users.noreply.github.com>
| 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. |
There was a problem hiding this comment.
This still needs to be moved up, I think?
| 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. | ||
|
|
||
| ### What's included |
There was a problem hiding this comment.
Fair enough 🙂 I still think it would be better at the start of this section, but not a strong preference either way. Feel free to resolve this comment.
Added a "What's included" section to clarify that the Coralogix OTEL integration only sends traces, not metrics.
Users who want metrics in Coralogix can use the Prometheus integration + OTEL Collector.