Metrics

groundcover is able to ingest metrics generated by DataDog clients using the DogStatsD protocol. Once ingested the metrics will appear as custom metrics in the Dashboards section.

There are two ways to ingest DogStatsD data into groundcover:

1. Dual Shipping from the DataDog agent - to DataDog + groundcover's endpoint

2. Redirecting the DataDog SDK to send metrics to groundcover's endpoint

Dual Shipping from the DataDog agent

Finding the groundcover Custom Metrics Service Endpoint

Use the instructions here to locate the endpoint for the Custom Metrics service, referenced below as {GROUNDCOVER_CUSTOM_METRICS_ENDPOINT}.

Configuring the DataDog agent

DataDog agents can be configured to send data to groundcover's VictoriaMetrics instance. This can be set up in two methods:

1. Fully Redirect metrics to groundcover - metrics will not be sent to DataDog

2. Send metrics both to groundcover & DataDog - Dual Shipping

The following is based on VictoriaMetrics' docs here.

Dual Shipping

Add the following configuration value to your DataDog deployment:

DD_ADDITIONAL_ENDPOINTS='{\"http://{GROUNDCOVER_CUSTOM_METRICS_ENDPOINT}:8428/datadog\": [\"apikey\"]}'

Full Redirection

Add the following configuration value to your DataDog deployment:

DD_DD_URL=http://{GROUNDCOVER_CUSTOM_METRICS_ENDPOINT}:8428/datadog

Redirecting the DataDog SDK

Finding the groundcover Vector Service Endpoint

Use the instructions here to locate the endpoint for the Vector's service, referenced below as GROUNDCOVER_VECTOR_ENDPOINT.

Configuring the SDK endpoint

Apply the following environment variables to your deployment to redirect the traffic to groundcover's endpoint for ingestion:

env:
  - name: DD_DOGSTATSD_URL
    value: "udp://{GROUNDCOVER_VECTOR_ENDPOINT}:8125"

Keep in mind - using this method will stop sending metrics to the DataDog agent, meaning they will not appear in DataDog's platform