Skip to content

Explain how to remove dependencies added by Orchestrion #32008

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.

Sign up for GitHub

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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
+13 −0
Open

Explain how to remove dependencies added by Orchestrion #32008

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7c2fac4
Explain how to remove dependencies added by Orchestrion
nsrip-dd Oct 6, 2025
00f49e4
Apply suggestions from code review
nsrip-dd Oct 6, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions content/en/tracing/trace_collection/automatic_instrumentation/dd_libraries/go.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -235,6 +235,17 @@
Your Orchestrion-built application includes [continuous profiler][12] instrumentation.
To enable the profiler, set the environment variable `DD_PROFILING_ENABLED=true` at runtime.

#### Remove integrations

You can remove integrations by modifying the imports in the `orchestrion.tool.go` file.
Copy link
Member

Choose a reason for hiding this comment

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

Or you can create your own orchestrion.tool.go before you run orchestrion.

You might do this if you don't want an integration,

Check notice on line 241 in content/en/tracing/trace_collection/automatic_instrumentation/dd_libraries/go.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.sentencelength 

Suggestion: Try to keep your sentence length to 25 words or fewer.
or if you want to reduce the number of transitive dependencies for integrations your program doesn't use.
By default, Orchestrion imports `github.com/DataDog/dd-trace-go/orchestrion/all/v2`,
which will import every library for which there is an Orchestrion integration.

Check warning on line 244 in content/en/tracing/trace_collection/automatic_instrumentation/dd_libraries/go.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.tense 

Avoid temporal words like 'will'.
You can replace this import with imports of only the integrations you want to use.
See [the tracer source code][17] for the list of supported integrations.
Note that if you do this, you will need to manually update `orchestrion.tool.go` in order to enable new integrations.

Check warning on line 247 in content/en/tracing/trace_collection/automatic_instrumentation/dd_libraries/go.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.words 

Use 'to' instead of 'in order to'.

Check warning on line 247 in content/en/tracing/trace_collection/automatic_instrumentation/dd_libraries/go.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.tense 

Avoid temporal words like 'will'.

Check warning on line 247 in content/en/tracing/trace_collection/automatic_instrumentation/dd_libraries/go.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.words 

Use '**Note**:' instead of 'Note that'.

### Troubleshooting

To troubleshoot builds that `orchestrion` manages, see [Troubleshooting Go Compile-Time Instrumentation][13].
Expand All @@ -250,6 +261,7 @@
[14]: /getting_started/tagging/unified_service_tagging/
[15]: /security/application_security/exploit-prevention/
[16]: /tracing/trace_collection/library_config/go/#traces
[17]: https://github.com/DataDog/dd-trace-go/blob/main/orchestrion/all/orchestrion.tool.go


{{% /tab %}}
Expand Down
Loading