Skip to content

Conversation

git-thuerk-done
Copy link
Contributor

What does this PR do? What is the motivation?

Merge instructions

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

@git-thuerk-done git-thuerk-done requested a review from a team as a code owner October 10, 2025 17:47
@git-thuerk-done git-thuerk-done added the WORK IN PROGRESS No review needed, it's a wip ;) label Oct 10, 2025
@github-actions github-actions bot added the Architecture Everything related to the Doc backend label Oct 10, 2025
Copy link
Contributor

github-actions bot commented Oct 10, 2025

@git-thuerk-done git-thuerk-done requested a review from a team as a code owner October 10, 2025 18:15
@github-actions github-actions bot added the Images Images are added/removed with this PR label Oct 10, 2025
url: synthetics/browser_tests/app-that-requires-login
parent: synthetics_browser_tests
weight: 304
- name: Network Testing

Choose a reason for hiding this comment

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

Overall, we should favor using Network Path testing / Network Path test(s) instead of Network testing / Network test(s)

1. **Source service**: The label displayed for the source host in the Network Path visualization.
2. **Destination service**: The label displayed for the destination host in the Network Path visualization.
3. **Max TTL**: Maximum time-to-live (maximum number of hops) for outgoing probe packets. Defaults to 30 hops.
4. **E2E Queries**: Number of packets sent to the destination to measure packet loss, latency, and jitter.

Choose a reason for hiding this comment

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

Defaults to 50.

2. **Destination service**: The label displayed for the destination host in the Network Path visualization.
3. **Max TTL**: Maximum time-to-live (maximum number of hops) for outgoing probe packets. Defaults to 30 hops.
4. **E2E Queries**: Number of packets sent to the destination to measure packet loss, latency, and jitter.
5. **Traceroute Queries**: Number of traceroute path tracings to perform. Results are aggregated in each test run details panel.

Choose a reason for hiding this comment

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

Defaults to 3.

- Individual test runs
- Aggregated Network Path visualizations across all test runs

The Network Path visualization shows the routes packets take to complete queries during each test run. Use the health bar handles to control the time frame for displayed network paths. For more information about how Network Path visualizations are built, see the [Network Path documentation][2].

Choose a reason for hiding this comment

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

I anticipate there's going to be a bit of confusion between the handle bars and the date filter at the top of the page - we can talk about it live to see how best to phrase this!

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

Labels

Architecture Everything related to the Doc backend Images Images are added/removed with this PR WORK IN PROGRESS No review needed, it's a wip ;)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants