This example deploys a central OpenTelemetry Collector to receive OTLP trace and metrics data. From the OpenTelemetry Collector, data can be exported to remote backends, removing the need to run an expensive monitoring stack on MicroShift.
For a sample application with a sidecar opentelemetry collector, refer to the kepler & opentelemetry example
Edit the OpenTelemetry Collector config file to configure the correct receivers, exporters, and pipelines.
In this example, the collector is configured to receive OTLP and Prometheus data. Logging and Jaeger exporters are also configured.
An opentelemetry collector deployment will be created in namespace otelcol. The Jaeger deployment in this example is running external to the VM
on the host machine. Refer to the Jaeger deployment document.
Deploy the OpenTelemetry Collector in MicroShift:
oc create ns otelcol
oc apply -n otelcol -k manifests/otel-collector/An opentelemetry-collector pod should now be running in -n otelcol. View the logs of the opentelemetry collector pod
to ensure data is being received and exported as expected.
For this Jaeger is running on the local system external to the virtual machine. For this example, refer to the Jaeger deployment document.