KubeWatch
Start free

Export Targets

Forward your own KubeWatch metrics out to Datadog, New Relic, Splunk, and other observability platforms.

Export Targets takes metrics KubeWatch already collects and pushes them out to a third-party observability platform on a schedule, for teams that want KubeWatch data sitting alongside everything else in a platform they already standardized on. It's the reverse of an Integration, which pulls data in. Creating, editing, deleting, or enabling/disabling a target requires the admin role, the same as integrations. Running a target on demand is available to any org member.

Adding a target

  1. Click Add export target and choose a platform.
  2. Fill in that platform's credential fields (see below, each platform needs different ones).
  3. Set Metric names, a comma-separated list of the exact KubeWatch metric names to forward (for example cpu_usage_percent, memory_usage_bytes). Only metrics you already see in KubeWatch's own dashboards can be forwarded; there's no wildcard.
  4. Set the export interval (minimum 30 seconds, defaults to 60).
  5. Click Save.

The platform can't be changed after creation. Delete and re-add it under the correct platform instead.

Per-platform setup

Datadog

You'll need an API key (Organization Settings → API Keys) and, optionally, a Site (defaults to datadoghq.com, use datadoghq.eu for the EU site). Metrics are submitted as gauges via the v2 Series API.

Dynatrace

You'll need an API token (Access Tokens, needs the metrics.ingest scope) and your Environment URL (your https://<environment-id>.live.dynatrace.com base).

Honeycomb

You'll need an Ingest key, a Dataset name, and optionally a Region (us or eu, defaults to us).

Honeycomb is built for events and traces, not periodic gauges, and bills per event submitted. Metrics support via OTLP is still beta on Honeycomb's side. Consider this the weakest fit of the nine platforms; a small export interval will generate a correspondingly large event volume and cost.

New Relic

You'll need a License key (Account Settings, use the License key, not a User key or Insights Insert key) and optionally a Region (us, eu, or jp, defaults to us).

AppDynamics

You'll need the Machine Agent URL, the local HTTP listener of an AppDynamics Machine Agent you already run (for example http://your-agent-host:8293), plus an optional Metric path prefix (defaults to Custom Metrics|KubeWatch).

AppDynamics has no direct SaaS metrics-ingest endpoint. This target only works if you already have a Machine Agent running somewhere reachable from KubeWatch; it submits to that agent's local API, which then forwards to your AppDynamics controller.

Splunk (metrics via HEC)

You'll need an HEC token (Settings → Data Inputs → HTTP Event Collector), your Collector URL (your HEC endpoint, for example https://splunk.example.com:8088), and an Index (a metrics-type index).

Splunk Infrastructure Monitoring

You'll need an Access token (Organization Settings → Access Tokens) and your Realm (for example us1, shown in your SignalFx/Splunk Observability URL). Realm is required; there's no default.

Sumo Logic

You'll need a Collector URL, a unique HTTP Logs & Metrics source URL you create yourself in Sumo (Configuration → Collection → add an HTTP source), and optionally a Token if you added one to that source.

Sumo Logic has no shared ingest host; you must provision the HTTP source in your own Sumo account first and paste its generated URL here.

Wavefront

You'll need an API token and your Instance URL (for example https://your-company.wavefront.com).

Wavefront's own documentation describes direct `/report` ingestion as suitable for test, trial, and proof-of-concept use, not production, where a separately-installed Wavefront proxy is the supported path. This target uses direct ingestion; treat it accordingly if your Wavefront usage is production-critical.

Reading a target's status

Each target shows a status dot, when it last exported, how many points it sent, and, if the last attempt failed, the error. Click Run now to export immediately rather than waiting for the next scheduled interval.

What's next

Export Targets today covers metric forwarding to nine platforms. Log and trace forwarding aren't included.