Document HTTPS limitation for non-IIS Windows services in USM #32723
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
Add documentation explaining that Universal Service Monitoring (USM) only detects environment variables set at process start time, not those set programmatically within application code. This clarifies that while APM instrumentation libraries can read DD_SERVICE and similar variables set via System.setProperty() (Java) or Environment.SetEnvironmentVariable() (.NET), USM cannot detect these as it reads from /proc/PID/environ (Linux) or system APIs (Windows) which only contain the initial process environment. Includes examples for properly setting environment variables in Docker, Kubernetes, and shell environments to ensure USM detection. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Add documentation clarifying that Universal Service Monitoring on Windows only supports HTTPS monitoring for IIS-based services. Non-IIS services (custom .NET apps, Node.js, Java, etc.) can only be monitored via HTTP. This limitation exists because USM on Windows uses Event Tracing for Windows (ETW) via the Microsoft-Windows-HttpService provider, which is only available for IIS services. Non-IIS services running HTTPS will not have their encrypted traffic monitored by USM. Includes a clear breakdown of what is and isn't supported: - IIS services: HTTP + HTTPS ✅ - Non-IIS services: HTTP only ✅, HTTPS ❌ 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Contributor
Preview links (active after the
|
Contributor
|
Pushed style edits to make copy appear less LLM-generated. The hallmarks of LLM-generated text (frequent bolding, emojis, etc.) are associated with low trust. Will merge when checks complete. |
cswatt
approved these changes
Nov 10, 2025
1 task
brett0000FF
pushed a commit
that referenced
this pull request
Nov 10, 2025
* Clarify USM environment variable detection limitations Add documentation explaining that Universal Service Monitoring (USM) only detects environment variables set at process start time, not those set programmatically within application code. This clarifies that while APM instrumentation libraries can read DD_SERVICE and similar variables set via System.setProperty() (Java) or Environment.SetEnvironmentVariable() (.NET), USM cannot detect these as it reads from /proc/PID/environ (Linux) or system APIs (Windows) which only contain the initial process environment. Includes examples for properly setting environment variables in Docker, Kubernetes, and shell environments to ensure USM detection. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> * Document HTTPS limitation for non-IIS Windows services in USM Add documentation clarifying that Universal Service Monitoring on Windows only supports HTTPS monitoring for IIS-based services. Non-IIS services (custom .NET apps, Node.js, Java, etc.) can only be monitored via HTTP. This limitation exists because USM on Windows uses Event Tracing for Windows (ETW) via the Microsoft-Windows-HttpService provider, which is only available for IIS services. Non-IIS services running HTTPS will not have their encrypted traffic monitored by USM. Includes a clear breakdown of what is and isn't supported: - IIS services: HTTP + HTTPS ✅ - Non-IIS services: HTTP only ✅, HTTPS ❌ 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> * some reformatting * edits --------- Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: cecilia saixue watt <cecilia.watt@datadoghq.com>
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.
Documents that USM on Windows only supports HTTPS for IIS services, not for non-IIS services (Node.js, Java,
custom .NET apps, etc.)