15 open-source alternatives ranked by real activity

Open-source Mezmo alternatives

A curated, ranked list of the 15 best open-source alternatives to Mezmo.

The best open-source alternative to Mezmo is OpenObserve. If that doesn't suit you, other good options are SigNoz, Grafana Loki, Vector and Kibana.

Commercial alternatives to Mezmo include Axiom, Loggly, Papertrail and Coralogix. See all 18.

Mezmo alternatives are mainly monitoring & observability tools, but some are also data pipeline & ETL tools and analytics tools. 15 of them shipped code in the last 30 days, 15 can be self-hosted, and 8 use a permissive licence.

Last updated November 13, 2026 · ranked by GitHub stars, growth and recent commits

OpenObserve

A cloud-native observability platform covering logs, metrics, traces, RUM and LLM monitoring, with Parquet columnar storage on S3 and a pitch against Datadog and Splunk.

GitHub stars
23k
Last commit
today
Latest release
v1.2.0-rc2
Licence
AGPL-3.0
Self-hosted
Yes
Hosted version
Available
openobserve.aiOpenObserve homepage screenshot

OpenObserve, often shortened to O2, is open-source observability software spanning logs, metrics, traces and analytics, real user monitoring on web, Android and iOS, session replay, pipelines, SLOs and AI and LLM observability. It is pitched as a lower-cost option next to Datadog, Splunk and Elasticsearch for teams that want complete observability without the complexity or price.

Its architecture uses Parquet columnar storage and an S3-native design, which the project says can cut storage costs by up to 140 times compared with Elasticsearch, with petabyte-scale capacity. Topics reference OpenTelemetry, Prometheus, Jaeger and Kibana, showing the standards and tools it interoperates with. The README has sections on architecture, comparisons, production readiness, security and compliance, and an enterprise edition.

OpenObserve is AGPL-3.0 licensed, with a hosted cloud option and a self-hosted deployment, and documentation and a Slack community are provided. It suits engineering teams looking to consolidate logging, metrics and tracing in one tool while keeping storage costs under control.

Key features

  • Logs, metrics and traces in one platform
  • Real user monitoring and session replay
  • LLM and AI observability
  • Parquet columnar storage on S3
  • OpenTelemetry and Prometheus compatibility
  • Pipelines and SLO tracking

Pricing: Self-hosting is free. Cloud is pay-as-you-go at $0.50 per GB ingested plus $0.01 per GB queried, with unlimited users and a 14-day trial; Enterprise is custom.

SigNoz

An open-source observability platform built on OpenTelemetry that unifies APM, logs, metrics, traces, alerts and dashboards in one tool, self-hosted or in the cloud.

GitHub stars
33k
Last commit
today
Latest release
v0.149.0
Self-hosted
Yes
Hosted version
Available
signoz.ioSigNoz homepage screenshot

SigNoz is an observability platform, open source and built on OpenTelemetry. It aims to replace a fragmented monitoring stack with a single place for logs, metrics, traces, alerts, exceptions and dashboards, and it presents itself as useful for both engineering teams and their AI agents.

The APM view follows how each service performs, covering latency, error rate, throughput, Apdex, the busiest endpoints, and calls to databases and external services. Log management supports ingesting, searching and correlating logs with traces and metrics through a visual query builder. Dashboards can be built with a query builder, PromQL or ClickHouse SQL, infrastructure monitoring covers Kubernetes clusters, pods, nodes and host resources, and LLM and AI observability traces prompts, tool calls, tokens, latency and cost.

You can choose how to run it. SigNoz Cloud is fully managed, with a 30-day free trial and usage-based pricing that starts at $49. Enterprise options cover cloud, bring-your-own-cloud and self-hosted deployments with extra support and controls. The free Community edition runs in your own infrastructure via Docker, Kubernetes or Linux. The repository license is listed as 'Other' on GitHub.

Key features

  • OpenTelemetry-native logs, metrics and traces
  • APM with latency, error rate and Apdex
  • Log management with a visual query builder
  • Dashboards via query builder, PromQL or SQL
  • Kubernetes infrastructure monitoring
  • LLM and AI application observability
  • Alerts and exception tracking

Pricing: Self-hosted Community is free. SigNoz Cloud Teams starts at $49 per month including $49 of usage, then usage-based per GB; Enterprise is custom and starts at $4000 per month.

Grafana Loki

Grafana Loki is a horizontally scalable log aggregation system that indexes labels instead of log contents, inspired by Prometheus.

GitHub stars
29k
Last commit
yesterday
Latest release
v3.7.9
Licence
AGPL-3.0
Self-hosted
Yes
Hosted version
Available
grafana.comGrafana Loki homepage screenshot

Loki is a log aggregation system from Grafana, described as Prometheus for logs. It is horizontally scalable, highly available and multi-tenant. Instead of indexing the contents of log lines, it indexes a set of labels for each log stream and stores the compressed log text, which the project says makes it simpler to operate and cheaper to run. It is written in Go and released under the AGPL-3.0 license.

Because Loki reuses the labels familiar from Prometheus, you can move between metrics and logs using the same label sets, and it has native support in Grafana. It works especially well for Kubernetes pod logs, since metadata such as pod labels is scraped and indexed automatically. A typical stack has three parts: Alloy as the collection agent, Loki for storage and queries, and Grafana for exploration. Alloy replaces Promtail, which is considered feature complete. Unlike Prometheus, Loki receives logs by push.

Key features

  • Label-based indexing instead of full-text indexing
  • Horizontally scalable, multi-tenant architecture
  • Native Grafana integration for querying logs
  • Automatic Kubernetes pod label indexing
  • Grafana Alloy agent for log collection
  • Single-binary deployment option

Pricing: Free and open source under the AGPL-3.0 license.

Vector

A Rust-based observability data pipeline from Datadog's open-source team that collects, transforms and routes logs and metrics to any destination.

GitHub stars
23k
Last commit
today
Latest release
v0.61.0
Licence
MPL-2.0
Self-hosted
Yes
vector.devVector homepage screenshot

Vector is a high-performance observability data pipeline that works both as an agent and as an aggregator. It collects logs and metrics from many sources, transforms them, and routes them to whichever vendors or storage systems you choose, so you can switch or combine backends without changing how data is collected.

The project argues that this gives you control over your telemetry: you can cut costs by filtering and shaping data before it reaches a paid vendor, enrich events in new ways and apply data security where you need it rather than where it is most convenient for a vendor. It also claims to be substantially faster than comparable tools. Built in Rust, its primary design goal is reliability, and topics mention traces, stream processing and ETL.

Datadog's open-source engineering team maintains Vector, which is licensed under MPL-2.0. The README offers a quickstart, installation guides, integrations and container images. Because it is software you run yourself, it needs no hosted service, and it suits platform and SRE teams that manage large volumes of logs and metrics.

Key features

  • Collects logs and metrics from many sources
  • Transforms and enriches events in flight
  • Routes data to multiple destinations
  • Runs as agent or aggregator
  • Written in Rust for reliability
  • Container images and install guides

Pricing: Free and open source under the MPL-2.0 license.

Kibana

Kibana is the web interface for querying, visualizing and managing data stored in Elasticsearch, used for dashboards, observability and analytics.

GitHub stars
21k
Last commit
yesterday
Latest release
v9.5.6
Self-hosted
Yes
Hosted version
Available
elastic.coKibana homepage screenshot

Kibana is the user interface that sits on top of Elasticsearch. It lets people query, analyze, visualize and manage the data stored there, turning indexes into charts, metrics views and dashboards. It is part of the Elastic Stack and is commonly used for log analysis, observability and general analytics work.

Teams build visualizations and assemble them into shared dashboards, explore documents with search, and use the interface to manage parts of an Elasticsearch deployment. The project advises running Kibana and Elasticsearch at the same version, with major versions required to match, because mismatches can cause problems and support may ask for an upgrade first.

The code is written in TypeScript. The repository lists its license as 'Other' rather than a standard SPDX identifier, so the license files should be read for the exact terms. Kibana can be downloaded and run on your own infrastructure, and Elastic also offers a hosted version through its Cloud service.

Key features

  • Query and explore Elasticsearch data
  • Visualizations and metrics charts
  • Shared dashboards for monitoring
  • Observability views for logs and metrics
  • Management tools for Elasticsearch data
  • Hosted option through Elastic Cloud

Telegraf

Telegraf is a plugin-driven agent that collects, processes and forwards metrics, logs and other data, shipping as a single static Go binary with TOML configuration.

GitHub stars
18k
Last commit
2 days ago
Latest release
v1.40.3
Licence
MIT
Self-hosted
Yes
influxdata.comTelegraf homepage screenshot

Telegraf is an agent for gathering, processing, aggregating and writing metrics, logs and other kinds of data. It comes from InfluxData and is commonly paired with InfluxDB, but it can write to many other destinations, so it works as a general-purpose collector in monitoring pipelines.

Its strength is a library of more than 300 plugins that cover devices such as OPC UA and Modbus, logs from files and directories, messaging systems like AMQP, Kafka and MQTT, monitoring standards such as OpenTelemetry and Prometheus, networking gear, and system metrics for CPU, memory, disk, network, S.M.A.R.T., Docker and Nvidia GPUs. Universal plugins like Exec and HTTP let you run your own code to collect or transform data. Telegraf compiles to a standalone static binary with no external dependencies, and it is configured in TOML.

The project, written in Go and MIT licensed, has more than a thousand contributors. It is run on the machines you want to monitor, and suits sysadmins, IoT engineers and observability teams that want one flexible agent instead of many specialized exporters.

Key features

  • 300+ input, processor and output plugins
  • Static binary with no dependencies
  • Configuration written in TOML
  • Custom collection through exec plugins
  • System, Docker and GPU metrics
  • Support for Kafka, MQTT and OpenTelemetry

Pricing: The Telegraf agent is open source and free to run yourself. Telegraf Enterprise has custom pricing with plans starting at $18,000 per year.

Quickwit

A cloud-native open-source search engine for observability data, built in Rust to index logs and traces on object storage with an Elasticsearch-compatible API.

GitHub stars
12k
Last commit
today
Latest release
v0.9.3
Licence
Apache-2.0
Self-hosted
Yes
quickwit.ioQuickwit homepage screenshot

Quickwit is an open-source, cloud-native search engine designed for observability, covering log management and distributed tracing, with metrics support listed on the roadmap. It is written in Rust, builds on the Tantivy search library, and is meant to search large volumes of data kept in cheap object storage.

It provides full-text search and aggregation queries, schemaless or strict-schema indexing, and a RESTful API that is compatible with a large subset of the Elasticsearch and OpenSearch APIs, so existing clients can often be reused. It is native to Jaeger and OpenTelemetry, works as a Grafana data source and can ingest from Kafka, Kinesis and Pulsar. Compute and storage are decoupled, with stateless indexers and searchers, and data can sit on Amazon S3, Azure Blob Storage or Google Cloud Storage.

Operational features include multi-tenancy with many indexes, partitioning, retention policies and delete tasks for GDPR use cases, and a Helm chart for Kubernetes. Quickwit is licensed under Apache-2.0 and you run it yourself. It suits teams looking for lower-cost log and trace storage with a familiar search API.

Key features

  • Full-text search and aggregation queries
  • API compatible with Elasticsearch clients
  • Native Jaeger and OpenTelemetry support
  • Search directly on cloud object storage
  • Decoupled compute and storage
  • Ingestion from Kafka, Kinesis and Pulsar
  • Retention policies and GDPR delete tasks
  • Helm chart for Kubernetes

Pricing: Free and open source under the Apache-2.0 licence.

Logstash

Logstash is a server-side data processing pipeline that ingests data from many sources, transforms it and sends it to destinations such as Elasticsearch.

GitHub stars
15k
Last commit
2 days ago
Latest release
v9.5.6
Self-hosted
Yes
elastic.coLogstash homepage screenshot

Logstash is part of the Elastic Stack alongside Beats, Elasticsearch and Kibana. It is a server-side data processing pipeline that ingests data from many sources at once, transforms it, and then ships it to a storage destination, with Elasticsearch being the natural target in Elastic's own stack. It is built with Java and JRuby.

Its functionality comes from plugins. The project says Logstash has over 200 plugins, hosted in separate repositories under the logstash-plugins GitHub organization, and each plugin is a self-contained Ruby gem published to RubyGems.org. Writing your own plugin is described as easy, with documentation on developing and testing them.

Official binaries and Debian and RPM packages are available from the downloads page, and documentation, a forum and Elastic support channels are listed. Development of the core requires JDK 21. The repository lists the license as 'Other', so the license files should be reviewed for exact terms.

Key features

  • Ingests data from many sources at once
  • Transforms and enriches events in a pipeline
  • Over 200 plugins
  • Plugins distributed as Ruby gems
  • Debian and RPM packages
  • Part of the Elastic Stack

HyperDX

An open-source observability platform that unifies logs, traces, metrics and session replays on top of ClickHouse and OpenTelemetry, a Kibana-style experience for ClickHouse.

GitHub stars
10k
Last commit
today
Latest release
cli-v0.9.0
Licence
MIT
Self-hosted
Yes
Hosted version
Available
hyperdx.ioHyperDX homepage screenshot

HyperDX is an open-source observability platform for working out why production is broken. It brings logs, metrics, traces, errors and session replays into one place, and works as a search and visualization layer on top of ClickHouse and OpenTelemetry, which the authors compare to Kibana for ClickHouse. It is a core component of ClickStack.

It is schema agnostic and can sit on top of an existing ClickHouse schema. Searching uses full-text and property syntax such as level:err, with SQL as an option, events can be compared with event deltas, high-cardinality events can be charted on dashboards, and alerts can be set up in a few clicks. Live tail shows the newest logs and traces, JSON strings can be queried natively, OpenTelemetry works out of the box, and APM views cover HTTP requests down to database queries.

One deployment option is ClickStack, a bundle of ClickHouse, HyperDX, an OpenTelemetry Collector and MongoDB, and HyperDX can instead be pointed at your own ClickHouse instance. It can also be used with ClickHouse Cloud. The project is MIT licensed and written in TypeScript.

Key features

  • Unified logs, metrics, traces and session replays
  • Schema-agnostic search on ClickHouse
  • Full-text and property search syntax
  • Alerts and event delta analysis
  • Live tail for logs and traces
  • OpenTelemetry support out of the box
  • Dashboards for high-cardinality events

Pricing: Free plan stores up to 3 GB a month. Starter is $20 per month flat with 50 GB included and $0.40 per extra GB; Enterprise is custom. No per-seat or per-host billing.

OpenTelemetry Collector

The OpenTelemetry Collector is a vendor-agnostic service that receives, processes and exports traces, metrics and logs so one agent can feed many observability back-ends.

GitHub stars
7.8k
Last commit
today
Latest release
v0.165.0
Licence
Apache-2.0
Self-hosted
Yes
opentelemetry.ioOpenTelemetry Collector homepage screenshot

This entry covers the OpenTelemetry Collector, the component of the OpenTelemetry project that handles telemetry data in transit. It is a vendor-agnostic implementation for receiving, processing and exporting telemetry, so teams do not need to run separate agents or collectors for each open-source telemetry format such as Jaeger or Prometheus when sending data to several open-source or commercial back-ends.

The project's stated objectives are to be usable, with sensible default configuration and support for popular protocols, performant and stable under varying loads, observable itself, extensible without touching the core code, and unified, with a single codebase that can run as an agent or a collector for traces, metrics and logs. Documentation covers getting started, configuration, security and monitoring.

The Collector is written in Go, licensed under Apache-2.0 and is part of the CNCF ecosystem, with a special interest group that meets weekly. You deploy it yourself next to your applications or as a central gateway. It suits platform and SRE teams standardizing telemetry pipelines.

Key features

  • Receives telemetry in many protocols
  • Processes and transforms traces, metrics and logs
  • Exports to open-source and commercial back-ends
  • Runs as an agent or a gateway
  • Extensible through components
  • Sensible default configuration

Pricing: Free and open source under the Apache-2.0 licence.

5 more Mezmo alternatives

Commercial Mezmo alternatives

Hosted, closed-source products that compete with Mezmo. Showing 12 of 18.

See every Mezmo alternative on its tool page

Mezmo alternatives: questions

What is the best open-source alternative to Mezmo?
OpenObserve is the top-ranked open-source alternative to Mezmo on Enlisted: A cloud-native observability platform covering logs, metrics, traces, RUM and LLM monitoring, with Parquet columnar storage on S3 and a pitch against Datadog and Splunk. Other strong options are SigNoz, Grafana Loki, Vector and Kibana.
What are the best commercial alternatives to Mezmo?
Axiom, Loggly, Papertrail, Coralogix and Cribl are among the hosted, closed-source alternatives to Mezmo listed on Enlisted, which lists 18 in total. Compare their pricing and features on each tool page.
Are these Mezmo alternatives free?
All 15 are open source, so the code is free to use under its licence, and all of them can be self-hosted on your own server or computer. 5 also offer a paid or managed cloud version if you'd rather not host it yourself.
How is this list of Mezmo alternatives ranked?
By a score built from GitHub stars, star growth over the last 30 days and how recently the code changed. 15 of these projects shipped code in the last 30 days. Data is refreshed daily, and nobody can pay to move up.

People also look for alternatives to…

View all