This directory contains a number of sample configurations that can be used with the OTEL kubernetes operator that is installed as part of the MARA project.
Each configuration currently uses the simplest deployment, which uses an
in-memory store for data being processed. This is obviously not suited to a
production deployment, but it is intended to illustrate the steps required to
work with the OTEL deployment.
Each of the sample files is configured to listen on the OTLP protocol . The listen ports configured are:
- grpc on port 9978
- http on port 9979
All the examples log to the container's stdout. However, the basic configuration
is configured to only show the condensed version of the traces being received.
In order to see the full traces, you need to set the logging level to
DEBUG. The basic-debug object is configured to do this automatically.
This is the default collector that only listens and logs summary spans to the container's stdout.
This is a more complex variant that contains multiple receivers, processors, and exporters. Please see the file for details.
This configuration file deploys lightstep as an ingester. Please note you will need to have a lightstep account to use this option, and you will need to add your lightstep access token to the file in the field noted.
By default, the otel-collector.yaml.basic configuration is copied into the
live otel-collector.yaml. The logic for this project runs all files ending in
.yaml as part of the configuration, so you simply need to either rename your
chosen file to otel-collector.yaml or add ensuring only the files you want to
use have the .yaml extension.