Skip to content

Conversation

@fernandorodriguezcdatadog
Copy link
Contributor

Example says "Traces for which the end-to-end execution time is more than 5 seconds" but code says "trace_duration:>2s", so changing the second number to make both match at 5 seconds.

What does this PR do? What is the motivation?

Example says "Traces for which the end-to-end execution time is more than 5 seconds" but code says "trace_duration:>2s", so changing the second number to make both match at 5 seconds.

Merge readiness:

  • Ready for merge

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

Example says "Traces for which the end-to-end execution time is more than 5 seconds" but code says "trace_duration:>2s", so changing the second number to make both match at 5 seconds.
@fernandorodriguezcdatadog fernandorodriguezcdatadog requested a review from a team as a code owner December 26, 2025 20:10
@rtrieu
Copy link
Contributor

rtrieu commented Dec 26, 2025

Hi @fernandorodriguezcdatadog can you rename your branch to follow our naming conventions (see PR description notes) so that the required checks will pass? Thanks!

@fernandorodriguezcdatadog fernandorodriguezcdatadog deleted the fernandorodriguezcdatadog-patch-1 branch December 26, 2025 22:26
@fernandorodriguezcdatadog
Copy link
Contributor Author

Hi @rtrieu thanks for pointing that out!
I renamed the branch, but that seems to have caused the PR to be automatically closed. Should I create a new PR for the name branch name?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants