Customize the pipeline
You can customize the Gloo OTel pipeline and set up additional receivers, processors, and exporters in your pipeline.
To see the receivers, processors, and exporters that are set up by default for you, run kubectl get configmap gloo-telemetry-gateway-config -n gloo-mesh -o yaml and kubectl get configmap gloo-telemetry-collector-config -n gloo-mesh -o yaml.
- Receivers: Receivers listen on a network port to receive telemetry data. For example, you can set up receivers to scrape extra Prometheus targets. To see an example, check out Scrape Gloo management server metrics.
- Processors: Processors can transform the data before it is forwarded to another processor and an exporter. For example, you can use processors to drop and generate new data. To see an example, see Enable Cilium metrics
- Exporters: Exporters forward the data they get to a destination on the local or remote network. For example, you can use an exporter to forward your data to a remote Thanos cluster, Mimir cluster, or a third-party provider, such as Datadog, Honeycomb, and others. To see an example, check out Forward data to Datadog.
For more information about receivers, processors, and exporters, see the pipeline architecture information in the OpenTelemetry documentation.