Send data to VictoriaMetrics from Edge Delta

Prepare to send metrics to VictoriaMetrics.

  2 minute read  

Overview

You can use the Prometheus Remote Write Destination to send metrics to your VictoriaMetrics instance. In this scenario VictoriaMetrics functions only as a data destination without the VictoriaMetrics vmagent. The Edge Delta agent will push metrics using VictoriaMetrics’s Prometheus remote write API .../api/v1/write.

Determine the Endpoint

In an enterprise setup, the VictoriaMetrics endpoint and authentication settings depend on your deployment model and how you expose the service to external systems like Edge Delta.

Option 1. Kubernetes-Based Deployment (with Ingress)

Ingress URL: If you’re exposing VictoriaMetrics via an Ingress controller:

  https://victoria.yourcompany.com

Setup:

  1. Create an Ingress object for the VM service.
  2. Attach TLS (via cert-manager, Let’s Encrypt, etc.).
  3. Ensure DNS resolves to your ingress controller’s IP.

Option 2. Kubernetes with LoadBalancer Service (Cloud-native)

External IP: Get the external IP provisioned by your cloud provider:

  kubectl get svc vm-victoria-metrics-single-server -n <namespace>

Replace with the namespace used by VictoriaMetrics.

Example Output:

NAME                               TYPE           CLUSTER-IP     EXTERNAL-IP      PORT(S)
vm-victoria-metrics-single-server  LoadBalancer   10.96.0.100    35.233.74.200    8428:32563/TCP

In this example, the endpoint is as follows:

http://35.233.74.200:8428

Note: Replace with HTTPS and certs in production.

Option 3. Standalone VM (VM/Bare Metal/Container)

Direct IP or DNS: If deployed on a VM or server with a public IP or behind a reverse proxy:

Endpoint example:

https://vm-metrics.company.com:8428

If you use this method, ensure:

  • VM port 8428 is open to ED nodes
  • TLS termination is configured
  • DNS points to the server/reverse proxy

Option 4. Behind a Reverse Proxy

Reverse proxy terminates TLS and forwards to VictoriaMetrics on port 8428

Endpoint:

https://metrics.company.com

Your NGINX (for example) config would proxy /api/v1/write to localhost:8428

Configure the Prometheus Remote Write Destination Node

Add a Prometheus Remote Write Destination node to your pipeline, configure it with the endpoint and any required TLS settings, and route metrics to it.

In this example, the endpoint is an in-cluster service and TLS is not required:

Note: The Prometheus remote write API is specified as the destination endpoint: .../api/v1/write

Check VictoriaMetrics for Edge Delta Metrics

You can check VictoriaMetrics for metrics from Edge Delta by searching for metrics with an Edge Delta type attribute. For example, the resource_ed_conf_id label reflects the resource["ed.conf.id"] field used by Edge Delta: