Telemetry Manager is a Kubernetes operator that fulfils the Kyma module interface. It provides APIs for a managed agent/gateway setup for log, trace, and metric ingestion and dispatching into 3rd-party backend systems, in order to reduce the pain of orchestrating such setup on your own. Read more on the usage of the module as well as general design and strategy behind the module.
The logging controllers generate a Fluent Bit DaemonSet and configuration from one or more LogPipeline and LogParser custom resources. The controllers ensure that all Fluent Bit Pods run the current configuration by restarting Pods after the configuration has changed. See all CRD attributes and some examples.
For more information, see Dynamic Logging Backend Configuration.
The trace controller creates an OpenTelemetry Collector deployment and related Kubernetes objects from a TracePipeline custom resource. The collector is configured to receive traces using the OpenTelemetry Protocol (OTLP), and forwards the received traces to a configurable OTLP backend.
For more information, see Dynamic Trace Backend Configuration.
The metric controller creates an OpenTelemetry Collector and related Kubernetes objects from a MetricPipeline custom resource. The collector is deployed as a Gateway. The controller is configured to receive metrics in the OTLP protocol and forward them to a configurable OTLP backend.
For more information, see Dynamic Monitoring Backend Configuration.
See the installation instruction.
See the user documentation.
For details, see:
- Available commands for building/linting/installation
- Testing strategy
- Troubleshooting and debugging
- Release process
- Governance checks like linting
See the CONTRIBUTING file.
See the LICENSE file.