Logz.io

Logz.io is a cloud log management and observability platform built on OpenSearch, Grafana and Jaeger, priced by daily usage for engineering teams.

Logz.io collects the logs, metrics and traces a software team produces and keeps them in one searchable account. An engineer chasing a fault works from one place instead of switching between separate tools. The company calls the platform Open 360, and it runs on open source projects: OpenSearch Dashboards for logs, Grafana for metrics and Jaeger for traces. Logz.io was founded in Tel Aviv in 2014, and its operating company is Logshero Ltd. Log Management centres on Explore, where engineers write Lucene queries with autocomplete and watch new lines arrive through Live Tail. Patterns collapses repeated messages into single rows so the unusual ones stand out. Logs from common platforms are parsed on arrival, and the Parsing Rules Hub covers formats that need rules of their own. Drop filters keep noisy logs out of the index, and LogMetrics turns a query into a metric. Archive and Restore moves older logs to Amazon S3 or Azure Blob and brings them back when needed. Infrastructure Monitoring, Distributed Tracing and Kubernetes 360 add metrics, traces and cluster views, while Agentic Observability brings AI agents into the same account. The platform is aimed at engineering, DevOps and SRE teams that want hosted open source observability instead of operating OpenSearch, Grafana and Jaeger clusters themselves. It suits teams migrating from a self-managed ELK Stack and teams working to shorten the time to resolve incidents. Companies built on AWS, Google Cloud or Azure connect through ready-made integrations. Teams watching what their observability data costs use drop filters and warm and cold storage tiers to decide what they keep. Security teams can bring the same data into Cloud SIEM. During an outage, an on-call engineer filters Explore down to the failing service and follows a log line straight into its Jaeger trace. After a release, the team watches Live Tail and lets an alert fire when an error query crosses its threshold. OrionIQ adds a chat panel beside the log table for questions about what Explore shows. Data arrives through the Telemetry Collector, and through OpenTelemetry, Prometheus and Fluentd for teams that already run them. When an investigation reaches back past the retention window, archived logs return from S3 into a temporary account for searching.