Skip to content
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

[DOCS-9753] adding Windows support for Network Path #26914

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
51 changes: 46 additions & 5 deletions content/en/network_monitoring/network_path/setup.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,15 +23,19 @@ Setting up Network Path involves configuring your Linux environment to monitor a

## Prerequisites

- Agent version `7.59` or higher is required.
- [CNM][1] must be enabled.
[CNM][1] must be enabled.

**Note**: If your network configuration restricts outbound traffic, follow the setup instructions on the [Agent proxy configuration][2] documentation.

## Setup

### Monitor individual paths

{{< tabs >}}
{{% tab "Linux" %}}

Agent `v7.59+` is required.

Manually configure individual paths by specifying the exact endpoint you want to test. This allows you to target specific network routes for monitoring.

1. Enable the `system-probe` traceroute module in `/etc/datadog-agent/system-probe.yaml` by adding the following:
Expand Down Expand Up @@ -126,8 +130,35 @@ Manually configure individual paths by specifying the exact endpoint you want to

3. Restart the Agent after making these configuration changes to start seeing network paths.

[4]: https://github.com/DataDog/datadog-agent/blob/main/cmd/agent/dist/conf.d/network_path.d/conf.yaml.example

{{% /tab %}}
{{% tab "Windows" %}}

Agent `v7.61+` is required.

**Note**: Windows only supports TCP traceroutes.

In Windows environments, the Agent uses UDP by default to monitor individual paths. If the protocol is not specified in the configuration, the Agent attempts a UDP traceroute, and any errors are logged. To work around this, ensure the protocol is set to TCP in the following example:

```yaml
init_config:
min_collection_interval: 60 # in seconds, default 60 seconds
instances:
- hostname: api.datadoghq.eu # endpoint hostname or IP
protocol: TCP
port: 443 # optional port number, default is 80
```
{{% /tab %}}
{{< /tabs >}}

### Network traffic paths (experimental)

{{< tabs >}}
{{% tab "Linux" %}}

Agent `v7.59+` is required.

**Note**: Network traffic paths is experimental and is not yet stable. Do not deploy network traffic paths widely in a production environment.

Configure network traffic paths to allow the Agent to automatically discover and monitor network paths based on actual network traffic, without requiring you to specify endpoints manually.
Expand Down Expand Up @@ -170,13 +201,23 @@ Configure network traffic paths to allow the Agent to automatically discover and

3. Restart the Agent after making these configuration changes to start seeing network paths.

**Note**: Network path is only supported for Linux environments.
[3]: https://github.com/DataDog/datadog-agent/blob/main/pkg/config/config_template.yaml#L1697

{{% /tab %}}
{{% tab "Windows" %}}

Agent `v7.61+` is required.

For network traffic paths on Windows environments, only detected TCP connections are shown.

{{% /tab %}}
{{< /tabs >}}

## Further Reading

{{< partial name="whats-next/whats-next.html" >}}

[1]: /network_monitoring/cloud_network_monitoring/setup/
[2]: https://docs.datadoghq.com/agent/configuration/proxy/?tab=linux
[3]: https://github.com/DataDog/datadog-agent/blob/main/pkg/config/config_template.yaml#L1645
[4]: https://github.com/DataDog/datadog-agent/blob/main/cmd/agent/dist/conf.d/network_path.d/conf.yaml.example


Loading