Skip to content

Releases: kyma-project/telemetry-manager

1.31.0

07 Jan 16:33
b734cf0
Compare
Choose a tag to compare

Changelog

Features

Bug fixes

  • fe1f89c: fix: MetricPipeline should not apply input default when the input not enabled explicitly (#1712) (@hisarbalik)

Documentation

Test suites

1.30.0

17 Dec 13:36
c12b7ea
Compare
Choose a tag to compare

Release Notes

  • Traces/Metrics: Update to Otel Collector 0.115.0 (#1666)
  • Metrics: Improved memory footprint of the metric agent when running with MetricPipeline input prometheus.(#1663)

Changelog

Features

Bug fixes

1.29.1

11 Dec 11:53
838c4e3
Compare
Choose a tag to compare

Changelog

Bug fixes

  • 838c4e3: fix: Optimize Prometheus scrape target discovery and prepare images for 1.29.1 release (#1669) (@hisarbalik)

1.29.0

03 Dec 16:45
375f649
Compare
Choose a tag to compare

Release Notes

  • Traces/Metrics: Update to Otel Collector 0.114.0 (#1632)

  • Logs: Update to Fluent Bit 3.2.2 (#1646)

  • Experimental: New LogPipeline output "OTLP" which will spin up a log gateway with an OTLP ingestion endpoint, instead of a fluentbit agent (#1415)

Changelog

Features

Bug fixes

Documentation

1.28.0

19 Nov 10:29
f68d177
Compare
Choose a tag to compare

Release Notes

  • Traces: You can now filter out Istio traces properly thanks to the noise filter of the trace gateway that was adjusted to trace changes in Istio (#1612).
  • Metrics: New MetricPipelines now have the subselectors of the “runtime” input enabled out of the box which means that when you enable the “runtime” input, all metrics are collected by default (#972).
  • Metrics: As the annotation-based scraping of Pods running with an Istio sidecar cannot work by desing, it is now explicitly not supported. The recommended way to do the scraping is by using annotations on a related service (#1468).
  • Logs: Improved resource configuration of the log agent no longer triggers CPU throttling alerts in third-party observability solutions (#1601).
  • New labels to use for telemetry workload in NetworkPolicies when you enable the communication of your workload with telemetry module components (#1516).

Changelog

Features

Bug fixes

Documentation

1.27.0

05 Nov 14:31
d1f13a7
Compare
Choose a tag to compare

Release Notes

  • Logs: Increased memory limit to prevent unnecessary restarts of Fluent Bit Pods (#1586)
  • General: Improved printColumns for Telemetry CRD (#1560)
  • Metrics: Cluster-level metrics (without namespace attribute) are no longer dropped if the runtime input defines a namespace selector (#1549)
  • Logs: Improved health reporting for the AgentHealthy status of a LogPipeline. (#1545)
  • Metrics: You can export lifecycle statistics for your Deployment, StatefulSet, DaemonSet, and Jobs resources with selectors in the runtime input of a MetricPipeline (#1521)

Changelog

Features

Bug fixes

Documentation

Test suites

1.26.2

31 Oct 13:08
c4fbced
Compare
Choose a tag to compare

Release Notes

1.26.1

23 Oct 09:54
937ed00
Compare
Choose a tag to compare

Release Notes

  • A missing RBAC role caused noisy error logs in the manager logs (#1548)

Changelog

Bug fixes

1.26.0

22 Oct 11:49
ff9819e
Compare
Choose a tag to compare

Release Notes

  • Logs: Update of Fluent Bit to version 3.1.9 (#1503)
  • Metrics: ou can now collect metrics about the Kubernetes Persistent Volumes that are bound to your workloads: Just enable the new selector for Volume metrics in the runtime input of your MetricPipeline resources. See also https://kyma-project.io/#/telemetry-manager/user/04-metrics?id=_6-activate-runtime-metrics. (#1301)
  • Traces: The deployment name of the trace gateway is now consistently named telemetry-trace-gateway. This change does not affect users. (#652)
  • Improved resource request settings for several components of the module (#1532)

Changelog

Features

Documentation

1.25.0

08 Oct 11:37
c96dcf9
Compare
Choose a tag to compare

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)

Changelog

Features

Bug fixes

Documentation