-
Notifications
You must be signed in to change notification settings - Fork 1.2k
[DOCS-12270] Synthetic Monitoring Network Tests #32138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Preview links (active after the
|
url: synthetics/browser_tests/app-that-requires-login | ||
parent: synthetics_browser_tests | ||
weight: 304 | ||
- name: Network Testing |
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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]. |
There was a problem hiding this comment.
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!
What does this PR do? What is the motivation?
Merge instructions
Merge readiness:
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