Skip to content

Remove smartagent/signalfx-forwarder from the agent default config #1759

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 9, 2025

Conversation

dmitryax
Copy link
Contributor

@dmitryax dmitryax commented Apr 9, 2025

The old SignalFx instrumentation libraries are not supported anymore. So we don't need to keep the forwarder in the default config. Use Splunk OpenTelemetry instrumentation libraries to send traces in OTLP format instead.

If you need to keep the receiver for longer, add the following section to your values.yaml file:

agent:
  ports:
    sfx-forwarder:
      containerPort: 9080
      hostPort: 9080
      protocol: TCP
      enabled_for: [traces]
  config:
    receivers:
      smartagent/signalfx-forwarder:
        listenAddress: 0.0.0.0:9080
        type: signalfx-forwarder
    service:
      pipelines:
        traces:
          receivers:
            - otlp
            - jaeger
            - smartagent/signalfx-forwarder
            - zipkin

All signalfx instrumentation libraries are not supported anymore. So we don't need to keep the forwarder in the default config. Use Splunk OpenTelemetry instrumentation libraries which send metrics and traces in OTLP format.
@dmitryax dmitryax requested review from a team as code owners April 9, 2025 01:49
Copy link
Contributor

@dloucasfx dloucasfx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR looks good!
My only question is communicating this change and making the user aware of it.
Do we have customers pointing their instrumented apps to 9080?

@dmitryax
Copy link
Contributor Author

dmitryax commented Apr 9, 2025

Do we have customers pointing their instrumented apps to 9080?

Only if they use the old SignalFx instrumentation libraries which are not supported anymore

@dmitryax dmitryax merged commit 8164149 into main Apr 9, 2025
82 checks passed
@dmitryax dmitryax deleted the remove-smartagent-signalfx-forwarder branch April 9, 2025 18:04
@github-actions github-actions bot locked and limited conversation to collaborators Apr 9, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants