Repository files navigation

Telemetry Manager is a Kubernetes operator that fulfils theKyma 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 theusage of the module as well as generaldesign 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 allCRD attributes and someexamples.

For further information, seeDynamic Logging Backend Configuration.

The trace controller creates anOpenTelemetry Collector deployment and related Kubernetes objects from aTracePipeline custom resource. The collector is configured to receive traces using the OTLP and OpenCensus protocols, and forwards the received traces to a configurable OTLP backend.

For further information, seeDynamic Trace Backend Configuration.

The metric controller creates anOpenTelemetry Collector and related Kubernetes objects from aMetricPipeline custom resource. The collector is deployed as aGateway. The controller is configured to receive metrics in the OTLP protocol and forward them to a configurable OTLP backend.

For further information, seeDynamic Monitoring Backend Configuration.

See theuser documentation.

See theinstallation instruction.

For details, see:

• Available commands for building/linting/installation
• Testing strategy
• Troubleshooting and debugging
• Release process
• Governance checks like linting

This project is licensed under the Apache Software License, version 2.0 except as noted otherwise in theLICENSE file.

To contribute to this project, follow the generalKyma project contributing guidelines.