Document OTel metrics lifecycle methods - #39515
Draft
bm1549 wants to merge 1 commit into
Draft
Conversation
Contributor
Preview links (active after the
|
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?
Documents how short-lived Python, Java, and Node.js processes can flush OTel custom metrics before exiting. It adds the Java and Node.js release requirements, shows ForceFlush and Shutdown examples, and documents the relevant timeout controls.
Merge readiness
This stays unchecked while the matching Java, Node.js, and system-tests PRs are under review.
For Datadog employees:
<name>/<description>convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR./reviewto run an automated check that catches common issues before a Documentation team member reviews your PR.AI assistance
Used Codex to research the SDK behavior, draft the examples, and run local documentation checks. The examples were also exercised through short-lived test apps against a Datadog backend.
Additional notes
Vale reports no errors. Its remaining warnings and suggestions are on unchanged lines.
Companion PRs: system-tests #7606, Java #12317, and Node.js #10023.