I appreciate Coralogix for having the query layer and cost controls in one place, which simplifies my work. DataPrime is impressively fast, allowing me to use it for real incident work beyond just dashboards. The events-to-metrics feature efficiently turns noisy logs into affordable time series data. The Kubernetes operator is a standout feature, letting our alert definitions be reviewed like our infrastructure and ensuring consistent alert sets across environments. I really value the TCO tiering, as it enables us to manage trace and log volumes cost-effectively by routing routine traffic to a low tier while keeping essential data in a high tier for alerts and daily searches. The integration with OpenTelemetry was particularly straightforward, which made the initial data setup easy. Overall, Coralogix provides a one-tool solution for handling alerts, logs, and traces efficiently, and the cost controls are crucial as we continue adding environments. Review collected by and hosted on G2.com.
The Kubernetes operator fails silently too often. An alert missing label filters is accepted and never fires. One missing a notification group reports as configured but never reaches the remote side. An alert description over the length limit is dropped without an error. You end up writing your own checks to confirm what landed. Quota and capacity planning per region also takes more attention than I'd like. Mainly: have the operator reject or flag an invalid alert at apply time and report the real remote sync status on the resource, so "configured" means it actually exists and can fire. A warning in the alert editor when an alert depends on data routed to a tier alerts can't see would also save time. Review collected by and hosted on G2.com.
