Helios is an open source observability platform built to unify metrics, traces, and logs across distributed systems. It provides a scalable way to monitor modern infrastructure while maintaining flexible deployment options for teams of all sizes.
The following overview highlights key dimensions of Helios, including its architecture, deployment model, and primary capabilities for managing observability data at scale.
| Dimension | Description | Key Attribute | Impact |
|---|---|---|---|
| Architecture | Modular backend with horizontally scalable components | Distributed processing | Supports high cardinality and large metric volumes |
| Deployment | Available as open source and enterprise distributions | Self-managed or cloud-managed | Flexible for on premises and hybrid environments |
| Data Model | Unified metrics, traces, and logs with consistent labels | Correlation across telemetry types | Simplifies root cause analysis and troubleshooting |
| API & Integration | Native Prometheus remote write, OpenTelemetry export, and Grafana compatibility | Standard protocols and exporters | Easier migration and integration with existing stacks |
| Operations | Automated storage management, retention policies, and multi tenant support | Fine grained access control | Secure multi tenant visibility for organizations |
Architecture and Scalability of Helios
Core components and data flow
The architecture of Helios is designed around decoupled ingestion, storage, and query layers. Ingestion pipelines handle metrics, traces, and logs, while a distributed storage layer optimizes for both real time queries and long term retention.
Horizontal scaling and performance
By sharding data across multiple nodes, Helios can sustain high write and query throughput without sacrificing query latency. Teams can add capacity linearly as infrastructure and telemetry demands grow, making it suitable for large scale environments.
Deployment Models and Integration
Self managed and cloud options
Helios supports both self hosted deployments and managed cloud offerings. This flexibility allows organizations to choose the model that best aligns with their operational policies, compliance requirements, and team expertise.
Compatibility with OpenTelemetry and Prometheus
Built in support for OpenTelemetry collectors and Prometheus remote write ensures straightforward migration from existing monitoring tools. Native exporters and service level integrations reduce the friction of adoption.
Operational Management and Security
Retention, compaction, and cost control
Configurable retention policies and efficient storage compaction help control long term storage costs. Administrators can define rules that align data retention with business and regulatory needs.
Multi tenant security and access control
Role based access control and tenant isolation mechanisms protect sensitive telemetry. Fine grached permissions ensure that teams only access the data they are authorized to view or modify.
Operational Best Practices and Recommendations
- Plan retention and compaction policies based on compliance and cost targets
- Use OpenTelemetry collectors to standardize telemetry ingestion across services
- Monitor ingestion and query performance to right size cluster capacity
- Implement role based access control to enforce least privilege for teams
- Leverage native Prometheus and Grafana integrations for faster onboarding
FAQ
Reader questions
How does Helios handle high cardinality metrics at scale?
Helios uses distributed storage and efficient indexing to manage high cardinality workloads, minimizing performance impact while preserving query accuracy.
Can Helios be deployed in air gapped environments?
Yes, the open source distribution can be installed in air gapped environments, with all necessary components available for offline installation and updates.
What observability data formats does Helios accept natively?
Helios natively accepts metrics via Prometheus remote write, traces and logs through OpenTelemetry exporters, and additional structured log ingestion via compatible adapters.
How does multi tenant isolation work in Helios?
Multi tenant isolation is enforced through namespace level permissions, resource quotas, and dedicated storage partitions, ensuring data separation and controlled access between teams.