monitoring connectors¶
Monitoring + observability platform integrations. After the 2026-06-19
SDK migration, the three highest-traffic connectors (datadog,
newrelic, prometheus) all run on official Go SDKs. splunk
and jaeger stay on REST because neither ships a maintained Go SDK
upstream (jaeger-client-go is officially deprecated for OpenTelemetry).
Connectors in this category¶
| Connector | URI / type | Native SDK | One-line description |
|---|---|---|---|
datadog |
connector://<name>/send |
✅ DataDog/datadog-api-client-go/v2 v2.61 |
Metrics / logs / events / monitors / NRQL-like queries. |
elastic_apm |
connector://<name>/send |
REST | Elastic APM transactions + errors. |
fluentd |
connector://<name>/send |
REST | Fluentd forward protocol push. |
jaeger |
connector://<name>/send |
Jaeger REST (no Go SDK; jaeger-client-go deprecated for OTel) |
spans + traces + services + operations. |
logstash |
connector://<name>/send |
REST | Logstash HTTP input push. |
micrometer |
connector://<name>/send |
REST | Micrometer registry compatibility shim. |
newrelic |
connector://<name>/send |
✅ newrelic/newrelic-client-go/v2 v2.89 |
NRQL / alerts / channels / incidents / events / logs. |
prometheus |
connector://<name>/send |
✅ prometheus/client_golang/api v1.23 |
PromQL query + range + labels + targets + alerts + rules. |
resilience |
connector://<name>/send |
Helix-native | Resilience4j-style circuit-breaker stats. |
splunk |
connector://<name>/send |
Splunk REST (no Go SDK upstream) | search / submit-event / indexes / saved-searches. |
Deep notes — SDK-backed connectors¶
datadog://¶
Source: pkg/connector/connectors/monitoring/datadog.go · SDK: DataDog/datadog-api-client-go/v2 v2.61.0
Ops (7): submit-metrics, submit-log, submit-event,
query-metrics, list-monitors, create-monitor, list-events.
connectors:
dd:
type: datadog
config:
api_key: ${DATADOG_API_KEY} # required
app_key: ${DATADOG_APP_KEY} # required for reads
site: datadoghq.com # or datadoghq.eu, us3.datadoghq.com, etc.
newrelic://¶
Source: pkg/connector/connectors/monitoring/newrelic.go · SDK: newrelic/newrelic-client-go/v2 v2.89.0
Ops (7): query-nrql (NerdGraph), list-alerts, list-channels,
list-incidents, send-event (Insights), send-log.
connectors:
nr:
type: newrelic
config:
api_key: ${NEWRELIC_API_KEY} # NRAK-... user/personal key
account_id: 1234567
region: US # or EU
insights_insert_key: ${NEWRELIC_INSIGHTS_KEY} # for send-event / send-log
prometheus://¶
Source: pkg/connector/connectors/monitoring/prometheus.go · SDK: prometheus/client_golang/api v1.23.2
Ops (8): query, query-range, list-series, list-labels,
list-label-values, get-targets, get-alerts, get-rules.
connectors:
prom:
type: prometheus
config:
url: http://prometheus.monitoring.svc.cluster.local:9090
# Optional basic-auth:
# username: prom
# password: ${PROM_PASS}
splunk://¶
Source: pkg/connector/connectors/monitoring/splunk.go · Protocol: Splunk REST API (Splunk ships no Go SDK upstream)
Ops (7): search, submit-event, list-indexes, get-index,
create-index, get-results, list-saved-searches.
connectors:
splunk:
type: splunk
config:
base_url: https://splunk.example.com:8089
token: ${SPLUNK_TOKEN}
index: main
source_type: helix:audit
jaeger://¶
Source: pkg/connector/connectors/monitoring/jaeger.go · Protocol: Jaeger collector + query REST APIs
Ops (5): send-spans, get-trace, find-traces, get-services,
get-operations.
connectors:
jaeger:
type: jaeger
config:
collector_url: http://jaeger-collector:14268
query_url: http://jaeger-query:16686
Runnable bundle¶
A complete, validatable bundle that exercises every connector lives at
examples/esb/monitoring.yaml:
bin/helix validate examples/esb/monitoring.yaml
# Validation passed: 0 workflow(s), 5 connector(s), 0 starlang block(s)
See also¶
pkg/tracing/— Helix's internal OpenTelemetry tracing (the recommended path for new code; export to Jaeger / DataDog / NewRelic via OTel exporters).pkg/metrics/— Helix's internal Prometheus-compatible metrics registry.