What it does
Logz.io Infrastructure Monitoring offers centralized metrics through a managed Prometheus-as-a-Service, with the broader Logz.io platform also collecting logs and distributed traces. Teams can send data with its Telemetry Collector or other documented integrations, then explore service and infrastructure behavior in the hosted dashboards. It is a monitoring service rather than a self-hosted metrics database: customers supply their telemetry, account credentials, and expected retention and volume.
Start with one telemetry source
Logz.io's quick-start guide describes creating an account and sending data through the Telemetry Collector or another supported integration. For infrastructure metrics, the product page describes Prometheus-based collection, dashboards, and filtering unneeded series; logs and traces can use their own shipping paths. A practical first task is to connect a test service or host, check that its metrics arrive, and then add a dashboard or alert for one operational signal. The guide also directs users to the distributed-tracing interface and account tokens.
The service helps users see and investigate telemetry; it does not repair the monitored application. An account and a data-shipping token are part of the documented setup, and ingestion volume and retention need to be planned before forwarding production data.
The public pricing page offers both consumption and subscription options. Its consumption examples list logs at $0.92 per ingested GB per day with seven days of retention, metrics at $0.40 per 1,000 time-series metrics per day with a displayed $0.20 rate for new consumption plans starting October 1, 2026, and traces at $0.16 per million spans per day with ten days of retention. The page says existing plans keep their current metrics rate. Additional retention and account terms can change the bill, so use the current rate card and estimate the workload before enabling high-volume ingestion.
Strengths
- A managed platform brings infrastructure metrics together with log management and distributed tracing.
- The quick-start guide documents a Telemetry Collector and multiple integration paths for sending data.
- The pricing page publishes per-volume and per-retention examples for consumption plans.
Watch out for
- The service needs a data source, shipping configuration, and credentials before its dashboards can show useful telemetry.
- Ingestion and retention are cost drivers, and a high-volume workload can require careful filtering and budget controls.
Best for
- Teams that want hosted Prometheus-style infrastructure metrics with logs and traces in one service
- Operators using Prometheus or OpenTelemetry integrations who prefer not to manage a telemetry backend
- Organizations that can plan data volume and retention for consumption-based monitoring
Sources
- Centralized Metrics at Scale with Prometheus-as-a-Service | Logz.io (Oct 25, 2026)
- Getting Started with Logz.io (Oct 25, 2026)
- Agentic Observability Pricing | Logz.io (Oct 25, 2026)