Skip to main content

Telemetry & Observability

Environment variables for the deploy microservice's telemetry stack: agent logs and metrics ingestion/query, plus automatic provisioning of Kibana and Grafana dashboards on startup. Metrics are read from VictoriaMetrics when configured, otherwise Elasticsearch is used as a fallback.

Elasticsearch & Kibana​

NameDescriptionRequiredType
ELASTICSEARCH_NODE
URL of the Elasticsearch node used to store agent logs and to serve as a metrics fallback when VictoriaMetrics is not configured.
false
string
Default:http://elasticsearch:9200
KIBANA_URL
URL of the Kibana instance used to auto-provision saved objects (data views and dashboards) on startup.
false
string
Default:http://kibana:5601
KIBANA_DASHBOARDS_PATH
Filesystem path to the Kibana saved-objects NDJSON file imported on startup.
Example: /app/telemetry/kibana-dashboards.ndjson
false
string
Default:<service-dir>/telemetry/kibana-dashboards.ndjson

VictoriaMetrics & Grafana​

NameDescriptionRequiredType
VICTORIA_METRICS_URL
URL of the VictoriaMetrics server used to store and query agent metrics.
Notes:
  • If not set, the deploy service falls back to Elasticsearch for metrics and skips Grafana dashboard setup.
false
string
Default:http://victoriametrics:8428
GRAFANA_URL
URL of the Grafana instance used to auto-provision the VictoriaMetrics data source and dashboards on startup.
false
string
Default:http://grafana:3000
GRAFANA_DASHBOARDS_PATH
Filesystem path to the Grafana dashboards JSON file imported on startup.
Example: /app/telemetry/grafana-dashboards.json
false
string
Default:<service-dir>/telemetry/grafana-dashboards.json