Better Stack collector gives you eBPF traces and metrics for all your services without code changes. Send OpenTelemetry SDK traces, logs and metrics through the same collector for more control and flexibility. They show up alongside the eBPF traces.
Open the OpenTelemetry ports on the collector:
Then turn it on in Better Stack:
All services can now send OpenTelemetry data to Better Stack via the open ports.
Instrument your services with OpenTelemetry:
Skip this step and send the OpenTelemetry SDK data to Collector.
Install OpenTelemetry Operator to your cluster.
Create an Instrumentation resource to make sure OpenTelemetry data is sent to Better Stack collector:
Annotate your workloads to enable auto-instrumentation:
Replace inject-python with the annotation for your language: inject-java, inject-nodejs, inject-dotnet, or inject-go.
See all available languages in the Operator documentation.
Then add service and host attributes to the same workloads.
Configure your OpenTelemetry SDK to send data to the Better Stack collector. In Kubernetes, use the node's IP address to reach the collector's host ports:
For Docker Compose and Docker Swarm, point your services to the Collector via localhost, for example http://localhost:4318 for HTTP or http://localhost:4317 for gRPC.
Set OTEL_SERVICE_NAME and OTEL_RESOURCE_ATTRIBUTES on all services instrumented with OpenTelemetry SDK. service.name groups traces and logs by service in Better Stack dashboards, while host.name and container.id connect SDK-generated telemetry with eBPF-generated data from the same workload.
Please let us know at hello@betterstack.com.
We're happy to help! 🙏
We use cookies to authenticate users, improve the product user experience, and for personalized ads. Learn more.