Skip to content

Releases: kyma-project/telemetry-manager

1.14.0

23 Apr 10:29
4b490c0
Compare
Choose a tag to compare

Release Notes

General

  • To use the memory limits more efficiently, the resource setup has been improved for all components. (#804)
  • Support for Kubernetes 1.29 (#967)

Logs

  • Improved status message for LogPipeline if the used certificate is invalid (#996)

Metrics/Traces

  • You can now easily detect whether there is an invalid or expired client certificate, because the TracePipeline and MetricPipeline status shows what's wrong (#930).

Experimental

  • Data flow problems in a LogPipeline are now reflected in the status for LogPipelines as well (#963)

Changelog

Features

Bug fixes

Documentation

Test suites

1.13.1

18 Apr 14:17
9ce82ec
Compare
Choose a tag to compare

Changelog

Features

1.13.0

09 Apr 15:01
66193df
Compare
Choose a tag to compare

Release Notes

Logs

  • You can now easily detect whether there is an invalid or expired client certificate, because the LogPipeline status shows what's wrong (#653).

Metrics/Traces

  • Update to Otel Collector 0.97.0 (#923)

Experimental

The first version of the advanced pipeline status is available in the development release (#425), covering the following features:

  • Collection of agent metrics with a new self-monitor component
  • Calculation of alert situations in the self-monitor regarding data flow problems like backpressure
  • Enrichment of pipeline status with alert situations

Changelog

Features

Bug fixes

Documentation

Test suites

1.12.0

26 Mar 12:35
df77ce1
Compare
Choose a tag to compare

Release Notes

  • Update Otel Collector to 0.96.0 (#882)

Changelog

Features

Bug fixes

Documentation

Test suites

1.11.1

14 Mar 12:43
451310b
Compare
Choose a tag to compare

Release Notes

A bug got fixed which was introduced with 1.11.0 and which was breaking the compatibility of the TracePipeline status attribute (#891)

Changelog

Bug fixes

1.11.0

12 Mar 16:14
902f369
Compare
Choose a tag to compare

Release Notes

Deprecation of condition types

With Telemetry version 1.11.0, we are deprecating condition types Running and Pending. They will be removed in future versions of the Telemetry module.

Please adjust your automation to rely on the new condition types instead.

Logs and Traces:

For LogPipeline and TracePipeline, we are introducing new status condition types, following the Kubernetes conventions ([#805])(#805).

Metrics:

For the MetricPipeline input type runtime, we are introducing the metrics *.cpu.usage, which replaces *.cpu.utilization.
This also fixes the calculation of the emitted metrics which are now calculated based on percentage instead of nanoseconds ([#838])((#838)).

Changelog

Features

Bug fixes

Documentation

1.10.1

05 Mar 10:55
fb9b126
Compare
Choose a tag to compare

Changelog

Bug fixes

1.10.0

27 Feb 13:16
Compare
Choose a tag to compare

Release Notes

Manager

  • Renamed the deployment "telemetry-operator" to "telemetry-manager" in the kyma-system namespace (#651)

Traces/Metrics

  • Update to OTel Collector 0.95.0 (#815)

Traces/Logs

  • Enriched resource status conditions for TracePipeline and LogPipeline with "status" and "reason" attribute to be aligned with kubernetes conventions (#772)

Logs

  • Update to FluentBit 2.2.2 (#794)

Changelog

Features

Bug fixes

Documentation

Test suites

1.9.0

13 Feb 13:25
93fff11
Compare
Choose a tag to compare

Release Notes

Traces/Metrics

  • Update of Otel-Collector to 0.93.0 (#771)

Logs

  • LogPipelines allow to include/exclude system namespaces for log collection explicitly (#778)

Changelog

Bug fixes

Documentation

1.8.0

30 Jan 12:02
Compare
Choose a tag to compare

Release Notes

Manager

  • Improved resource utilisation (#704)
  • Support for running in a denyAll NetworkPolicy environment (#536)

Traces/Metrics

  • Update to Otel-Collector 0.92.0 (#723)

Changelog

Features

Bug fixes

Documentation

Test suites