Release 1.25.0 · kyma-project/telemetry-manager

Release Notes

Now you can list all resources across the pipeline types LogPipeline/TracePipeline/metricPipeline using kubectl get kyma-telemetry-pipelines (#1487)
Metrics: You can now monitor the health of the Telemetry module via exposed metrics: By default, every MetricPipeline reports status metrics about the active pipeline and its conditions, which you can use for alerting and troubleshooting, see also the related Documentation. (#1294)
Metrics: Now, you can collect metrics (memory, CPU, and filesystem usage) about the Kubernetes Nodes of your cluster: In the runtime input of MetricPipeline, enable the new selector for Node metrics. See also the related Documentation. (#1300)
Traces/Metrics: Traces and Metrics: Improved validation for HTTP-based OTLP endpoints using path and port.(#1492)
Traces/Metrics: Update to OTel Collector 0.111.0 (#1497)

1ada9f6: feat: Add Node metrics selector to the UI (#1477) (@shorim)
bb16816: feat: Add a selector for runtime node metrics (#1450) (@shorim)
ab08df3: feat: Add conversion webhook config to dev CRD variant (#1463) (@skhalash)
08dacbb: feat: Add proper categories for telemetry CRDs (#1487) (@a-thaler)
8d56177: feat: Bump OTel image version to 0.111.0 (#1497) (@hisarbalik)
cdb1f9a: feat: Enable all memory metrics for nodes (#1500) (@rakesh-garimella)
e3cd057: feat: Enable resource status for telemetry resources (#1453) (@rakesh-garimella)
f1fac4c: feat: Make v1alpha1 LogPipeline input disableable (#1469) (@skhalash)

88c1bbb: fix: Adjust Self Monitor storage size (#1482) (@hisarbalik)
bfc92ee: fix: Endpoint validation with path and port scenario (#1492) (@TeodorSAP)
aea637e: fix: Revert removal of drop kyma resource attributes (#1471) (@rakesh-garimella)