This is the repository for recommended Helm charts for running an OpenTelemetry Collector using the OpenTelemetry Operator for Kubernetes. We recommend following the quick start documenation here for using these charts.
- otel-cloud-stack - Recommended chart for sending Kubernetes metrics to ServiceNow Cloud Observability using OpenTelemetry-native metric collection and the OpenTelemetry Operator.
- kube-otel-stack - Drop in replacement for kube-prometheus-stack, which uses the same configuration for scraping Prometheus exporters and forwarding metrics to Lightstep using the OpenTelemetry Operator. Use this chart if you are looking to compare Kubernetes monitoring in Prometheus with Kubernetes monitoring using ServiceNow Cloud Observability.
Note
Arrow usage is in beta, please use at your own risk. Reach out if you have any issues.
In order to use an arrow trace collector, you can use (1) the prebuilt image available via the Github Container Registry (GHCR) or you may (2) build your own custom image.
- We have built a Docker image using the recommended build config
- This Docker image can be pulled by running:
docker pull ghcr.io/lightstep/otel-collector-charts/otelarrowcol-experimental:latest
- You can use the collector config (
/arrow/config/gateway-collector.yaml
) by running:docker run -it -v $(PWD)/config/:/config --entrypoint /otelarrowcol ghcr.io/lightstep/otel-collector-charts/otelarrowcol-experimental:latest --config=/config/gateway-collector.yaml
- We have supplied a collector builder config below.
- Once an image is a available, simply apply your desired helm chart with the values.yaml AND the arrow.yaml in the respective chart.
- Make sure to replace the image in arrow.yaml with your custom built image.
Some of the features available in these charts are optional because they rely on components that have not been released in the OpenTelemetry Contrib Collector. Specifically, to make use of the new OpenTelemetry Protocol With Apache Arrow support requires using either the prebuilt image or a customer collector build at this time.
See the recommended custom collector build configuration as a starting point.