Skip to content
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

add option to disable smart agent bundle use #5

Merged
merged 1 commit into from
Dec 14, 2022
Merged

Conversation

atoulme
Copy link
Contributor

@atoulme atoulme commented Dec 9, 2022

Fixes #4

This pull request allows a user to explicitly disable the Smart agent bundle download, to save on disk space.

  1. Remove the existing buildpack if you have installed it in the past:
    heroku buildpacks:remove https://github.com/signalfx/splunk-otel-collector-heroku.git\#v0.0.1
  2. Add a new configuration entry to explicitly disable the smart agent download:
    heroku config:set SFX_AGENT_DISABLED=true
  3. Add the new buildpack:
    heroku buildpacks:add https://github.com/atoulme/splunk-otel-collector-heroku.git\#disable_sfx_agent
  4. Push a release like usual. Check the output of the push, looking for this line:
    remote: -----> Skipping installing the SignalFx Agent Bundle

That's it! You should be set.
Note disabling the smart agent has side effects. We will no longer collect heroku metadata about your application. I have opened open-telemetry/opentelemetry-collector-contrib#16833 to create a native receiver to replace this monitor going forward.

@atoulme atoulme requested review from a team as code owners December 9, 2022 07:45
@atoulme atoulme force-pushed the disable_sfx_agent branch 2 times, most recently from fe18aa0 to ac2b8cb Compare December 14, 2022 19:22
@atoulme atoulme merged commit d051e85 into main Dec 14, 2022
@atoulme atoulme deleted the disable_sfx_agent branch December 14, 2022 19:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Heroku Slug created with this project approaches disk limits
2 participants