Open-source Loggly alternatives

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.

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.

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.

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.

Graylog is a log management server written in Java and described by its maintainers as free and open. It centralizes log data from many systems so teams can search, view and analyze events in one place instead of connecting to each machine individually.

The repository topics point to support for common log formats and transports, including GELF and syslog, along with Kafka and AMQP inputs. Topics also place the project in log analysis, log collection, secure logging and SIEM territory, which reflects its use for monitoring and security work. Specific features were not available when this entry was written, because the vendor website could not be read.

ClickVisual is a lightweight, browser-based platform for log analysis and search, built on top of the ClickHouse database. It was created by the team at ShimoDocs and positions itself as a simpler tool for working with logs stored in ClickHouse, in the space where people often reach for Kibana and the ELK stack.

The interface offers a visual query dashboard with a histogram and raw log view, SQL-based querying, and percentage breakdowns for chosen fields. A VS Code style configuration board lets you push Fluent Bit configuration to a Kubernetes ConfigMap. It includes alarm workflows, and the documentation mentions login through GitHub and GitLab.

ClickVisual is written in Go and released under the MIT licence. It can be deployed with kubectl, which the project describes as out of the box, or installed with Docker or directly on a host, and documentation is published on its website. It suits platform and SRE teams that already collect logs into ClickHouse and want a straightforward UI for searching them without heavy infrastructure.

Telescope is an MIT-licensed web application for exploring log data. It gives developers and operations teams a single interface for searching logs that live in different places, including ClickHouse and StarRocks databases, Docker container logs read through the Docker API, and Kubernetes pod logs.

Administrators create and manage source connections, choose which fields are used, suggested, hidden or autocompleted, and control which users and groups can access each source. A data explorer adds dynamic visualizations alongside filtering and search, giving the same querying experience across all source types. ClickHouse and StarRocks serve as the main backends for structured log storage, while Docker and Kubernetes sources suit local development, ephemeral environments and cloud-native setups.

The backend is written in Python with Django and the front end uses Vue. It can be run locally with Docker, and a live demo instance with GitHub login is available for trying the end-user features. The project is at an early version number, so expect frequent change.