[DOCS-13682] Expand Understanding Injector Behavior with Windows, life cycle, and privilege details#36552
Open
[DOCS-13682] Expand Understanding Injector Behavior with Windows, life cycle, and privilege details#36552
Conversation
… to injector behavior guide Expands the Understanding Injector Behavior page with: - Windows loading mechanism (kernel driver + DLL) - Injector life cycle clarification (runs before main, exits before app starts) - Per-language injection mechanism table - Privileges and scope section covering injection scope, runtime privileges, and install-time privilege requirements per deployment mode Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
Contributor
Preview links (active after the
|
- Replace "Datadog DLL" with "injector DLL" to clarify what the file is and remove the redundant double "Datadog" reference - Drop the duplicate Java/.NET supported-runtimes statement, since this is already covered on the Windows install and SSI compatibility pages Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
- Lowercase "pod" in privileges section to match the rest of the page - Replace "Datadog DLL" with "injector DLL" for consistency with the Windows loading subsection - Name the injector explicitly at the start of the second life cycle paragraph for AI readability - Replace two semicolons with periods (Docker daemon, Windows profiler), per editorial reference - Match "tracer or profiler" wording across runtime privileges paragraph - Drop the awkward "only enable" placement in the Windows installation privileges item - Split the long "if injection fails" sentence into two Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
domalessi
added
WORK IN PROGRESS
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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?
Fixes DOCS-13682
Expands the Understanding Injector Behavior with Single Step Instrumentation guide with the following additions, requested by the APM SSI team and prompted by a customer security review:
mainand exits before the application starts, and is not a background process or thread.JAVA_TOOL_OPTIONS,PYTHONPATH,NODE_OPTIONS,RUBYOPT, CLR profiler vars,PHP_INI_SCAN_DIR, NGINX re-exec).Internal implementation details (weak symbol names, ELF/PE parsing, the Go processor, the policies engine, build details, and so on) were intentionally left out to keep the page customer-facing and stable.
Merge instructions
Merge readiness:
Additional notes