What's changed
- Fix the Service Integrations feature silently rendering no integration modules when
integrations.collectorwas left at its default empty string. The feature now relies on the same collector resolution as every other feature, so simply enabling integrations (e.g.integrations.alloy,integrations.cert-manager,integrations.istio) generates the expected Alloy modules without also having to setintegrations.collectorexplicitly (#2625) (@petewall) - Add
timeoutsetting on the OTLP destination (@petewall) - Fail rendering with a clear error when
profiling.enabled: trueis set but none ofprofiling.ebpf.enabled,profiling.java.enabled, orprofiling.pprof.enabledare enabled, instead of silently producing a profiling feature that collects no data (#2620) (@petewall) - Update Alloy Operator to 0.5.8, OpenCost to 2.5.21 and Windows Exporter to 0.12.7 (@petewall)* Fix Alloy collector instances cross-contaminating each other's
mounts.extra(and other nested values fromcollectorCommon.alloyor per-instancecollectors.<name>) due to SprigmergeOverwritealiasing nested map/slice references. The user-supplied merge inputs ($userCommonValuesand$userValues) are nowdeepCopy-ed before merging (#2623) (@petewall)
Full changelog: CHANGELOG.md