diff --git a/README.md b/README.md index 9226c9da2..c29be2f99 100644 --- a/README.md +++ b/README.md @@ -366,23 +366,19 @@ This command should return the following output if everything is OK: {"metric":{"__name__":"system.load.1","environment":"test","host":"test.example.com"},"values":[0.5],"timestamps":[1632833641000]} ``` -DataDog agent sends the [configured tags](https://docs.datadoghq.com/getting_started/tagging/) to -undocumented endpoint - `/datadog/intake`. This endpoint isn't supported by VictoriaMetrics yet. This prevents from adding the configured tags to DataDog agent data sent into VictoriaMetrics. -The workaround is to run a sidecar [vmagent](https://docs.victoriametrics.com/vmagent.html) alongside every DataDog agent, which must run with `DD_DD_URL=http://localhost:8429/datadog` environment variable. -The sidecar `vmagent` must be configured with the needed tags via `-remoteWrite.label` command-line flag and must forward incoming data with the added tags to a centralized VictoriaMetrics: - -Tagging via vmagent - -The configuration details are the following: -1. Set the `dd_url` param for each DataDog agent to the corresponding vmagent proxy address: `dd_url: http://:8429/datadog` -2. Configure ever sidecar `vmagent` with `-remoteWrite.url` command-line flag, so it forwards the received data to a centralized storage: `-remoteWrite.url=http://victoria-metrics:8428/api/v1/write` -3. [Specify extra tags](https://docs.victoriametrics.com/vmagent.html#adding-labels-to-metrics) you want to add to the data received from DataDog agent via `-remoteWrite.label` command-line flag at `vmagent` sidecars. For example, the following config adds `team="dev"` and `env="prod"` tags to all the received metrics from DataDog agent: `-remoteWrite.label=team=dev,env=prod` - -See [these docs](https://docs.victoriametrics.com/vmagent.html#adding-labels-to-metrics) for details on how to add labels to metrics at `vmagent`. - Extra labels may be added to all the written time series by passing `extra_label=name=value` query args. For example, `/datadog/api/v1/series?extra_label=foo=bar` would add `{foo="bar"}` label to all the ingested metrics. +DataDog agent sends the [configured tags](https://docs.datadoghq.com/getting_started/tagging/) to +undocumented endpoint - `/datadog/intake`. This endpoint isn't supported by VictoriaMetrics yet. +This prevents from adding the configured tags to DataDog agent data sent into VictoriaMetrics. +The workaround is to run a sidecar [vmagent](https://docs.victoriametrics.com/vmagent.html) alongside every DataDog agent, +which must run with `DD_DD_URL=http://localhost:8429/datadog` environment variable. +The sidecar `vmagent` must be configured with the needed tags via `-remoteWrite.label` command-line flag and must forward +incoming data with the added tags to a centralized VictoriaMetrics specified via `-remoteWrite.url` command-line flag. + +See [these docs](https://docs.victoriametrics.com/vmagent.html#adding-labels-to-metrics) for details on how to add labels to metrics at `vmagent`. + ## How to send data from InfluxDB-compatible agents such as [Telegraf](https://www.influxdata.com/time-series-platform/telegraf/) Use `http://:8428` url instead of InfluxDB url in agents' configs. diff --git a/docs/README.md b/docs/README.md index 9226c9da2..c29be2f99 100644 --- a/docs/README.md +++ b/docs/README.md @@ -366,23 +366,19 @@ This command should return the following output if everything is OK: {"metric":{"__name__":"system.load.1","environment":"test","host":"test.example.com"},"values":[0.5],"timestamps":[1632833641000]} ``` -DataDog agent sends the [configured tags](https://docs.datadoghq.com/getting_started/tagging/) to -undocumented endpoint - `/datadog/intake`. This endpoint isn't supported by VictoriaMetrics yet. This prevents from adding the configured tags to DataDog agent data sent into VictoriaMetrics. -The workaround is to run a sidecar [vmagent](https://docs.victoriametrics.com/vmagent.html) alongside every DataDog agent, which must run with `DD_DD_URL=http://localhost:8429/datadog` environment variable. -The sidecar `vmagent` must be configured with the needed tags via `-remoteWrite.label` command-line flag and must forward incoming data with the added tags to a centralized VictoriaMetrics: - -Tagging via vmagent - -The configuration details are the following: -1. Set the `dd_url` param for each DataDog agent to the corresponding vmagent proxy address: `dd_url: http://:8429/datadog` -2. Configure ever sidecar `vmagent` with `-remoteWrite.url` command-line flag, so it forwards the received data to a centralized storage: `-remoteWrite.url=http://victoria-metrics:8428/api/v1/write` -3. [Specify extra tags](https://docs.victoriametrics.com/vmagent.html#adding-labels-to-metrics) you want to add to the data received from DataDog agent via `-remoteWrite.label` command-line flag at `vmagent` sidecars. For example, the following config adds `team="dev"` and `env="prod"` tags to all the received metrics from DataDog agent: `-remoteWrite.label=team=dev,env=prod` - -See [these docs](https://docs.victoriametrics.com/vmagent.html#adding-labels-to-metrics) for details on how to add labels to metrics at `vmagent`. - Extra labels may be added to all the written time series by passing `extra_label=name=value` query args. For example, `/datadog/api/v1/series?extra_label=foo=bar` would add `{foo="bar"}` label to all the ingested metrics. +DataDog agent sends the [configured tags](https://docs.datadoghq.com/getting_started/tagging/) to +undocumented endpoint - `/datadog/intake`. This endpoint isn't supported by VictoriaMetrics yet. +This prevents from adding the configured tags to DataDog agent data sent into VictoriaMetrics. +The workaround is to run a sidecar [vmagent](https://docs.victoriametrics.com/vmagent.html) alongside every DataDog agent, +which must run with `DD_DD_URL=http://localhost:8429/datadog` environment variable. +The sidecar `vmagent` must be configured with the needed tags via `-remoteWrite.label` command-line flag and must forward +incoming data with the added tags to a centralized VictoriaMetrics specified via `-remoteWrite.url` command-line flag. + +See [these docs](https://docs.victoriametrics.com/vmagent.html#adding-labels-to-metrics) for details on how to add labels to metrics at `vmagent`. + ## How to send data from InfluxDB-compatible agents such as [Telegraf](https://www.influxdata.com/time-series-platform/telegraf/) Use `http://:8428` url instead of InfluxDB url in agents' configs. diff --git a/docs/Single-server-VictoriaMetrics.md b/docs/Single-server-VictoriaMetrics.md index ca711bb24..01603a3a2 100644 --- a/docs/Single-server-VictoriaMetrics.md +++ b/docs/Single-server-VictoriaMetrics.md @@ -370,23 +370,19 @@ This command should return the following output if everything is OK: {"metric":{"__name__":"system.load.1","environment":"test","host":"test.example.com"},"values":[0.5],"timestamps":[1632833641000]} ``` -DataDog agent sends the [configured tags](https://docs.datadoghq.com/getting_started/tagging/) to -undocumented endpoint - `/datadog/intake`. This endpoint isn't supported by VictoriaMetrics yet. This prevents from adding the configured tags to DataDog agent data sent into VictoriaMetrics. -The workaround is to run a sidecar [vmagent](https://docs.victoriametrics.com/vmagent.html) alongside every DataDog agent, which must run with `DD_DD_URL=http://localhost:8429/datadog` environment variable. -The sidecar `vmagent` must be configured with the needed tags via `-remoteWrite.label` command-line flag and must forward incoming data with the added tags to a centralized VictoriaMetrics: - -Tagging via vmagent - -The configuration details are the following: -1. Set the `dd_url` param for each DataDog agent to the corresponding vmagent proxy address: `dd_url: http://:8429/datadog` -2. Configure ever sidecar `vmagent` with `-remoteWrite.url` command-line flag, so it forwards the received data to a centralized storage: `-remoteWrite.url=http://victoria-metrics:8428/api/v1/write` -3. [Specify extra tags](https://docs.victoriametrics.com/vmagent.html#adding-labels-to-metrics) you want to add to the data received from DataDog agent via `-remoteWrite.label` command-line flag at `vmagent` sidecars. For example, the following config adds `team="dev"` and `env="prod"` tags to all the received metrics from DataDog agent: `-remoteWrite.label=team=dev,env=prod` - -See [these docs](https://docs.victoriametrics.com/vmagent.html#adding-labels-to-metrics) for details on how to add labels to metrics at `vmagent`. - Extra labels may be added to all the written time series by passing `extra_label=name=value` query args. For example, `/datadog/api/v1/series?extra_label=foo=bar` would add `{foo="bar"}` label to all the ingested metrics. +DataDog agent sends the [configured tags](https://docs.datadoghq.com/getting_started/tagging/) to +undocumented endpoint - `/datadog/intake`. This endpoint isn't supported by VictoriaMetrics yet. +This prevents from adding the configured tags to DataDog agent data sent into VictoriaMetrics. +The workaround is to run a sidecar [vmagent](https://docs.victoriametrics.com/vmagent.html) alongside every DataDog agent, +which must run with `DD_DD_URL=http://localhost:8429/datadog` environment variable. +The sidecar `vmagent` must be configured with the needed tags via `-remoteWrite.label` command-line flag and must forward +incoming data with the added tags to a centralized VictoriaMetrics specified via `-remoteWrite.url` command-line flag. + +See [these docs](https://docs.victoriametrics.com/vmagent.html#adding-labels-to-metrics) for details on how to add labels to metrics at `vmagent`. + ## How to send data from InfluxDB-compatible agents such as [Telegraf](https://www.influxdata.com/time-series-platform/telegraf/) Use `http://:8428` url instead of InfluxDB url in agents' configs. diff --git a/docs/assets/images/datadog.png b/docs/assets/images/datadog.png deleted file mode 100644 index 041a0ff95..000000000 Binary files a/docs/assets/images/datadog.png and /dev/null differ