Explain how to remove dependencies added by Orchestrion #32008
+13
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Orchestrion imports all available integrations by default so that users always get every integration we have without having to do more manual configuration. However, this adds lots of transitive dependencies. Some users are sensitive to this, e.g. if they have security scanner products which might flag dependencies their program doesn't actually use. Explain how to fine-tune which integrations Orchestrion imports.
Preview links (active after the
|
content/en/tracing/trace_collection/automatic_instrumentation/dd_libraries/go.md
Outdated
Show resolved
Hide resolved
content/en/tracing/trace_collection/automatic_instrumentation/dd_libraries/go.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Heston Hoffman <[email protected]>
kakkoyun
reviewed
Oct 7, 2025
|
|
||
| #### Remove integrations | ||
|
|
||
| You can remove integrations by modifying the imports in the `orchestrion.tool.go` file. |
There was a problem hiding this comment.
Or you can create your own orchestrion.tool.go before you run orchestrion.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
Orchestrion imports all available integrations by default so that users always get every integration we have without having to do more manual configuration. However, this adds lots of transitive dependencies. Some users are sensitive to this, e.g. if they have security scanner products which might flag dependencies their program doesn't actually use. Explain how to fine-tune which integrations Orchestrion imports.
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes