From 8b8ac096267dec9ce04bc57f1d3dc5de1a81de02 Mon Sep 17 00:00:00 2001
From: Dave Evans <dave.evans@thedatalab.org>
Date: Thu, 7 May 2026 17:57:33 +0100
Subject: [PATCH] Remove `logging` from configured otel exporters

This had the effect that every otel metric/trace ended up in the systemd
journal, which significantly bloated our logs and reduced our effective
retention period.

Having this data logged would have made sense when we were first
configuring and testing the collector, but is not helpful now.

See Slack discussion at:
https://bennettoxford.slack.com/archives/C069YDR4NCA/p1778171836696039
---
 services/collector/collector.yaml | 2 --
 1 file changed, 2 deletions(-)

diff --git a/services/collector/collector.yaml b/services/collector/collector.yaml
index 43fb84c..c9db17e 100644
--- a/services/collector/collector.yaml
+++ b/services/collector/collector.yaml
@@ -731,7 +731,6 @@ service:
         - resourcedetection
         - batch
       exporters:
-        - logging
         - otlphttp/metrics
     traces:
       receivers:
@@ -741,5 +740,4 @@ service:
         - resourcedetection
         - batch
       exporters:
-        - logging
         - otlphttp/traces