Coralogix

Coralogix is most useful once a team has decided which telemetry it wants to keep and how it will send it. The onboarding guide offers two routes: connect a cloud provider account for managed-service metrics, logs, and resource metadata, or deploy an OpenTelemetry collector for applications, containers, and hosts. The latter is a practical starting point for a service team already using OTel; the documentation says the collector can be deployed without changing application code. Connecting an AWS account requires permission to create a CloudFormation stack, while the documented AWS account connection is marked Preview. Azure and Google Cloud are configured one service at a time rather than through that account-connection route.

Investigate the signal, not just the notification

After telemetry arrives, Explore can start from a preset such as log volume or error logs, or from a dataset, recent query, or saved view. Users can filter and aggregate records with the Query Builder or write DataPrime queries, visualize the results, and drill into individual logs or spans. That sequence separates detection from diagnosis: an alert flags a condition, while the query and record details provide evidence for an engineer to interpret.

For cases that need context attached to the alert, a responder can add a DataPrime enrichment query to the alert's Notification step. The query runs when a Case activates and places its results alongside the notification. This is not available for signal-based alert notifications, runs asynchronously, and does not rerun just because the Case is updated. It can save repeated investigative queries, but the team still chooses what question the query answers and determines what the returned rows mean.

The pricing page describes usage-based charges for telemetry, with different units for logs, traces, metrics, and AI. Coralogix advertises a 14-day trial without a credit card; the full workload cost and any contract-specific terms still depend on the actual data mix and configuration.