From 12c639b4eba10e95613095b7960d1d1f0b51703e Mon Sep 17 00:00:00 2001 From: Ryan Fitzpatrick Date: Thu, 15 Apr 2021 19:09:49 +0000 Subject: [PATCH] Use signalfx-forwarder in default agent trace pipeline --- .../templates/config/_otel-agent.tpl | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/helm-charts/splunk-otel-collector/templates/config/_otel-agent.tpl b/helm-charts/splunk-otel-collector/templates/config/_otel-agent.tpl index d78ac9801c..88efd629ed 100644 --- a/helm-charts/splunk-otel-collector/templates/config/_otel-agent.tpl +++ b/helm-charts/splunk-otel-collector/templates/config/_otel-agent.tpl @@ -57,6 +57,10 @@ receivers: extra_metadata_labels: - container.id + smartagent/signalfx-forwarder: + type: signalfx-forwarder + listenAddress: 0.0.0.0:9080 + # By default k8s_tagger and batch processors enabled. processors: # k8s_tagger enriches traces and metrics with k8s metadata @@ -188,7 +192,7 @@ service: # default traces pipeline traces: - receivers: [otlp, jaeger, zipkin] + receivers: [otlp, jaeger, smartagent/signalfx-forwarder, zipkin] processors: - memory_limiter - batch @@ -231,7 +235,7 @@ service: - resource/add_agent_k8s - resourcedetection exporters: - # Use signalfx instead of otlp even if collector is enabled + # Use signalfx instead of otlp even if collector is enabled # in order to sync host metadata. - signalfx {{- end }}