1.13.0

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

• 0c1b1be: feat: Add LogPipeline TLS Certificate Validation (#914) (@hisarbalik)
• bf93b9c: feat: Add self-monitor Fluent Bit alert rules (#948) (@skhalash)
• f24cea3: feat: Trigger immediate reconciliation when self-monitor alert state changes (#912) (@skhalash)
• 987b479: feat: Update to otel-collector 0.97. with updated resty lib (#923) (@a-thaler)

Bug fixes

• 999330a: fix: Certificater/key should be sanitized always (#953) (@rakesh-garimella)
• 39dd83a: fix: Set content-security-policy header in webhook handler (#949) (@chrkl)

Documentation

• 0e7c063: docs: Add ADR for LogPipeline health status (#934) (@chrkl)
• 757bfe4: docs: Fix unordered lists (#933) (@Disper)

Test suites

• c9b5db0: test: Add Gitleaks workflow (#941) (@chrkl)
• 02ee5cc: test: Allow self-monitor to be deployed in dev mode (#915) (@rakesh-garimella)
• b45a9d8: test: Migrate noisy span filters test to telemetrygen (#945) (@skhalash)
• c52d012: test: Migrate to telmetry gen for metrics (#940) (@rakesh-garimella)
• 3c64d30: test: Self-monitor webhook E2E test (#932) (@skhalash)
• e6dfed3: test: Telemetry OTLP-based components error/warning logs (#931) (@TeodorSAP)