OpenTelemetry is a vendor-neutral, open-source observability framework for instrumenting, generating, collecting, and exporting telemetry data such as traces, metrics, and logs. Use OpenTelemetry’s collection of APIs, SDKs, and tools to collect and export observability data from your environment to Coralogix.
Instrumentation
Coralogix supports OpenTelemetry to get telemetry data (traces, logs, and metrics) from your app as requests travel through its many services and other infrastructure.
We provide a few alternative scenarios for setting up OpenTelemetry and sending your data to Coralogix. Documentation related to the configuration and installation of the v0.64.0 release of OpenTelemetry Collector for different deployments can be found below.
OpenTelemetry metrics are broadly compatible with Coralogix dimensional metrics. We currently support OpenTelemetry metrics v0.19. All of the supported metric types include an independent set of associated attributes which map directly to dimensions customers can use to filter metric data during your query. While Coralogix now supports Delta Temporality in addition to Cumulative Temporality, we encourage the use of Cumulative Temporality as a best practice.
Temporality
The OpenTelemetry Metrics Data Model and SDK are designed to support both Cumulative and Delta Temporality. It is important to understand that temporality will impact how the SDK manages memory usage.
The use of Cumulative Temporality for monotonic sums is common, exemplified by Prometheus. The use of Delta Temporality for metric sums is also common, exemplified by Statsd.
Delta Temporality
While Coralogix supports Delta Temporality in addition to Cumulative Temporality, we encourage the use of Cumulative Temporality as a best practice.
Those customers using Delta Temporality should take note of the following configuration parameters in our Delta Cumulative Converter:
Coralogix supports monotonic Sum and Histogram data points.
Coralogix keeps all metrics in our data store for 24 hours. If values for the same metric arrive in intervals greater than 24 hours, they will be recorded, but treated as “resets.”
Your data points may not always arrive consecutively. When a data point is missing, the time series with a missing data point will be delayed for 60 seconds. You have the option to retry sending us missing data points during this window.
If a second data point does not arrive after the first, your time series will restart from the third data point.
Be cautious about properly setting up your retry or reset series, as the OTEL Exporter can potentially miss data points and may need to resend them.
Oh no!We didn’t find anything for “”,
