Get telemetry flowing without a code rewrite
Get telemetry flowing quickly. Connecting data to Better Stack starts by naming a source, choosing a region and platform, then selecting an ingestion method. This streamlined setup gets you to data collection fast.
Better Stack Collector simplifies Kubernetes and Docker integration using eBPF. This gathers data without application code changes. For Docker, installation is a single generated command, including a collector secret, eliminating manual instrumentation overhead.
Alternatives exist: the official OpenTelemetry Collector integrates if you’re already invested in OTel or prefer not to use eBPF. Pure log forwarders like syslog offer simple, standards-compliant logging. Language-specific client libraries collect data directly from applications.
The right choice depends on your existing instrumentation and deployment needs. Better Stack supports diverse ingestion paths for maximum flexibility, whether you prioritize zero-code eBPF, OpenTelemetry compatibility, or basic log forwarding.
Turn raw signals into a map of your system
connecting the Collector transforms raw telemetry into a dynamic system map. Better Stack automatically discovers services, hosts, and processes. A visual service map immediately shows inter-service relationships, providing an instantaneous overview of your infrastructure topology.
Inspect RED metrics—Rate, Errors, and Duration—at the service level. This enables immediate performance assessment. Simultaneously, view live logs and traces for granular debugging, accelerating root cause analysis.
Better Stack also creates automatic host dashboards for critical metrics like CPU and memory utilization. Each discovered service gains its own metrics dashboard, providing a focused view of its specific operational data. This workflow demonstrates powerful zero-configuration capabilities for common environments.
Cut noise before it turns into a bill
Cut costs and sensitive data at the source. Better Stack leverages Vector Remap Language Language (VRL) directly within its ingestion agents, enabling real-time telemetry transformation at the edge. Drop unwanted events before ingestion, ensuring you only store actionable data. Mask sensitive fields, such as personally identifiable information (PII), preventing its exposure in logs and traces.
This pre-ingestion filtering directly reduces unnecessary stored data, cutting your observability bill. It also limits PII exposure, bolstering compliance. Always test VRL transformations thoroughly to avoid inadvertently discarding critical diagnostic evidence.
Collector setup also allows adjustable log and trace sampling. This provides granular control, letting you balance cost and data volume against diagnostic detail. Both sampling and VRL filtering represent deliberate tradeoffs, optimizing your observability for both budget and operational insight. For more on optimizing your stack, visit Better Stack: Observability and Incident Management Platform.
Enjoying this? Get one like it in your inbox each morning.
one email a day · unsubscribe in two clicks · no third-party tracking
Build useful metrics from logs and traces
Derive metrics from existing telemetry. Better Stack automatically creates metrics from logs or spans, or define custom metrics using JSON or SQL expressions. SQL expressions leverage native ClickHouse functions, allowing powerful aggregations. Once defined, connect these metrics to custom dashboard charts for focused visualization.
This approach offers flexibility. Start with Better Stack’s Collector, which provides built-in views of critical infrastructure metrics, host performance, and service RED metrics. This gives immediate visibility without upfront configuration.
As monitoring needs evolve, implement targeted transformations with Vector Remap Language Language and custom metrics. This iterative process optimizes both observability depth and ingestion costs, ensuring you only pay for the data that drives actionable insights.
Frequently Asked Questions
What is Better Stack?
Better Stack is an observability and incident-management platform for collecting and working with telemetry such as logs, metrics, and traces.
How does the Better Stack Collector gather data?
The Collector can use eBPF to gather telemetry from Kubernetes or Docker environments without requiring application code changes. Better Stack also supports OpenTelemetry, syslog, and language-specific libraries.
Can Better Stack filter telemetry before ingestion?
Yes. Vector Remap Language transformations can drop unwanted events or modify data, including filtering sensitive information, before it is ingested.
Can I use OpenTelemetry with Better Stack?
Yes. Better Stack supports the official OpenTelemetry Collector, making it an option for teams already using OpenTelemetry.