Observability and Data Architecture

12 Questions

What is the purpose of Coralogix's next-gen architecture?

To help make sense of ever-growing data

What is the name of Coralogix's stateful streaming data platform?

Streama

How does Coralogix support OpenTelemetry?

By collecting and exporting telemetry data from applications

What is the purpose of OpenTelemetry?

To provide a vendor-neutral observability framework

What is the outcome of Monday.com using Coralogix?

They were able to centralize and standardize their logs

What is the assumption about the user's application?

It has been instrumented with OTel SDKs and has a receiver set up

What is the primary benefit of using Coralogix's OpenTelemetry Chart for Kubernetes Observability?

Simplifying the collection of logs, metrics, and traces from pods to cluster-level components

What is the maximum size limit for a single request to Coralogix endpoints after decompression?

10 MB

What is the recommended approach for metric temporality in Coralogix?

Using Cumulative Temporality for metric sums

What is the purpose of the Delta Cumulative Converter in Coralogix?

To convert Delta metrics to Cumulative metrics

What is the advantage of batching telemetry requests in Coralogix?

Reducing networking overhead and improving performance

What is the significance of the 2048 unit limit in Coralogix's batch size configuration?

It is a hard limit on the batch size to balance networking overhead and performance

Study Notes

Observability and Coralogix

Coralogix offers a next-gen architecture to help make sense of ever-growing data.
The platform provides courses to advance knowledge and practical skills in observability, including expert insights, best practices, and solutions.

Streama and 3 "S" Architecture

Streama is the foundation of Coralogix's stateful streaming data platform, based on the 3 "S" architecture: source, stream, and sink.
Monday.com uses Coralogix to centralize and standardize their logs, allowing for easy searching across their entire stack.

OpenTelemetry and Integration

OpenTelemetry is a vendor-neutral, open-source observability framework for instrumenting, generating, collecting, and exporting telemetry data (traces, metrics, and logs).
Coralogix supports OpenTelemetry to collect telemetry data from applications and infrastructure.
OpenTelemetry provides a collection of APIs, SDKs, and tools to collect and export observability data to Coralogix.

Instrumentation and Setup

To use OpenTelemetry with Coralogix, customers need to instrument their application with OTel SDKs and set up a receiver for their data.
Examples of automatic instrumentation are provided for various languages.
Coralogix offers Kubernetes Observability using OpenTelemetry for comprehensive Kubernetes and application observability.

OpenTelemetry Metrics and Compatibility

OpenTelemetry metrics are broadly compatible with Coralogix dimensional metrics.
Coralogix supports OpenTelemetry metrics v1.x.
Supported metric types include an independent set of associated attributes that map directly to dimensions for filtering metric data during queries.

Temporality and Best Practices

Coralogix supports Delta Temporality in addition to Cumulative Temporality, but encourages the use of Cumulative Temporality as a best practice.
The OpenTelemetry Metrics Data Model and SDK support both Cumulative and Delta Temporality.
Cumulative Temporality is commonly used for monotonic sums, while Delta Temporality is used for metric sums.

Configuration and Performance

Configuration parameters in the Delta Cumulative Converter should be noted by customers using Delta Temporality.
The sizing ensures that telemetry sent to the Coralogix backend is batched into larger requests, reducing networking overhead and improving performance.
Limits apply to single requests, with a max of 10 MB after decompression.