Skip to content

Releases: kyma-project/telemetry-manager

1.57.2

06 Feb 15:57
bc3d1a3

Choose a tag to compare

Changelog

Bug fixes

1.57.1

04 Feb 16:42
6a5d3ed

Choose a tag to compare

Changelog

Bug fixes

  • 6a5d3ed: fix: drop-unknown-service-name processor nil warning and bump patch release 1.57.1 (#2956) (@hisarbalik)

1.57.0

03 Feb 13:39
5192e49

Choose a tag to compare

Release Notes

  • You can now enable a new method for service attribute enrichment that aligns more closely with OpenTelemetry semantic conventions. This new method is opt-in and is planned as the default in a future release. For details, see Automatic Data Enrichment: Service Attributes. (#2890)
  • Logs: To ensure LogPipeline resources are removed cleanly when you delete the Telemetry module, the Telemetry Manager no longer uses finalizers. (#1440)
  • The Telemetry Manager's reconciliation logic is optimized to reduce load on the Kubernetes API server. (#1097)
  • Update to OTel Collector 0.144.0 (#2909)

Changelog

Features

Bug fixes

Documentation

Test suites

1.56.1

20 Jan 18:28
a3ef319

Choose a tag to compare

Changelog

Bug fixes

1.56.0

20 Jan 11:01
daa1a44

Choose a tag to compare

Release Notes

This release promotes the Telemetry API to v1beta1, reflecting its production-ready stability (#767). The API conversion for running resources is automatic. However, if you store your Telemetry pipeline resources in a Git repository, you must manually update their API version to telemetry.kyma-project.io/v1beta1.
Required action: The upgrade includes a mandatory migration step for any Telemetry custom resources (CRs) that you store in a Git repository or manage through a CI/CD system. For detailed instructions, see the migration guide.

Other improvements:

  • The telemetry gateways now correctly enrich resource attributes, such as k8s.cluster.name, even if the incoming data already contains that attribute with an empty value (#1412).
  • You can now use IPv6 addresses in OTLP output endpoints (#2857).
  • Update to OTel Collector 0.143.0 (#2879).

Changelog

Features

Bug fixes

Documentation

1.55.0

08 Jan 15:12
552496d

Choose a tag to compare

Release Notes

Deprecation of Fluent Bit-based LogPipeline outputs
To align with the OpenTelemetry standard and provide enhanced features like log/trace correlation or advanced filter and transform expressions, we are deprecating the legacy Fluent Bit-based LogPipeline configuration. The use of http and custom outputs in LogPipeline resources is now deprecated. These legacy outputs, along with related fields like filters, files, and variables, are scheduled for removal in a future version of the Telemetry module.
Required Action:
If you are using LogPipeline resources with http or custom outputs, you must migrate them to use the otlp output (see Migrate Your LogPipeline From HTTP to OTLP).

Other Improvements

  • Update to Fluent Bit 4.2.2 (#2780)
    Resource attributes like k8s.cluster.name are getting enriched also if an empty value is already provided with the data (#1412)
  • In consequence of the deprecation announcements, all API elements relating to the Fluent Bit technology are marked as deprecated and a warning gets printed when used (#2232)
    New authentication method OAuth2 for otlp output (#2657)
  • The module deployment now supports to specify a imagePullSecret, custom labels, custom annotations and a trustCABundle (#2760)

Changelog

Features

Bug fixes

  • 851fee6: fix: gardener tests failed due to waiting for not existing resource (#2753) (@k15r)
  • 39f7154: fix: insert-cluster-attributes processor and add enrichment with predefined values E2E tests (#2763) (@TeodorSAP)
  • 859f037: fix: typo in workflow name and update branches-ignore (#2752) (@k15r)
  • ffb6b5d: fix: upgrade tests fail due to automatic resource cleanup (#2757) (@k15r)

Test suites

1.54.0

09 Dec 14:54
d4f689e

Choose a tag to compare

Changelog

Features

Bug fixes

Documentation

1.53.0

25 Nov 11:56
09ae2fc

Choose a tag to compare

Release Notes

  • Breaking Change: The LogParser API has been removed (#2205). As part of the legacy http/custom LogPipeline outputs feature, the LogParser API was deprecated for more than a year and finally got removed. Please use an OTLP based LogPipeline and use transform expressions instead.

  • Pipelines with invalid OTTL expressions will now get rejected, improving the developer experience: #2633

Changelog

Features

Bug fixes

Documentation

1.52.0

11 Nov 15:35
d32d12f

Choose a tag to compare

Release Notes

  • Now, you can use OTTL expressions to transform and filter telemetry data, before it's shipped to your observability backend. For details, see Transform and Filter with OTTL. (#1293)
  • We've removed the obsolete namespace "compass-system" from the list of system namespaces. (#2629)
  • You can now set a custom instrumentation scope for metrics ingested through the prometheus input. (#2638)
  • Update to OTel Collector 0.139.0 (#2661, #2662)

Changelog

Features

Bug fixes

Documentation

Test suites

1.51.0

28 Oct 14:45
4ea63b2

Choose a tag to compare

Changelog

Features

Bug fixes

Documentation