Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Splunk Observability Metrics (BYOK) — connector documentation

  • MCP endpoint: https://byok-splunk-observability-metrics.connectorbay.com/mcp
  • REST API: POST https://byok-splunk-observability-metrics.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-splunk-observability-metrics.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Splunk Observability Metrics Splunk Observability Cloud user API access token, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-splunk-observability-metrics.connectorbay.com/health · Tool schemas: https://byok-splunk-observability-metrics.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-splunk-observability-metrics · agent@connectorbay.com

What Splunk Observability Metrics (BYOK) is for

Splunk Observability Metrics (BYOK) lets an AI assistant read your own Splunk Observability Metrics data through the Splunk Observability Metrics API with a key you supply (Splunk Observability Cloud user API access token). Read-only: 8 tools (list_metrics, get_metric, list_dimensions, get_dimension, list_metric_timeseries, get_metric_timeseries, list_tags, get_tag). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.us0.signalfx.com, api.us1.signalfx.com, api.eu0.signalfx.com, api.eu1.signalfx.com, api.eu2.signalfx.com, api.au0.signalfx.com, api.jp0.signalfx.com, api.sg0.signalfx.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Splunk Observability Metrics. Splunk Observability Metrics and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which Splunk Observability metrics start with cpu.?"
  • "What type of metric is cpu.utilization in Splunk Observability?"
  • "Which hosts are known as dimension values in Splunk Observability?"
  • "Show the metadata Splunk Observability has for host web-1"
  • "Which time series exist for cpu.utilization on host web-1 in Splunk Observability?"
  • "Describe Splunk Observability time series AAAAAAAAAAA"

What it does

  • list_metrics: Search metric names and metadata (type, description, tags, custom properties). Query syntax: name: with * wildcards, for example name:cpu.*.
  • get_metric: Get the metadata of one metric by exact name: type, description, tags and custom properties.
  • list_dimensions: Search dimensions and their metadata. Query syntax: key: for names, : for values, * wildcard, exists:, AND/OR/NOT.
  • get_dimension: Get the metadata of one dimension value: description, tags and custom properties.
  • list_metric_timeseries: Search metric time series (MTS) metadata: metric name, type, dimensions, tags and custom properties. Query syntax: metric:, :, * wildcard, AND/OR/NOT.
  • get_metric_timeseries: Get the metadata of one metric time series by its id: metric name, type, dimensions, tags and custom properties.
  • list_tags: Search tags and their metadata (description and custom properties). Use * as a wildcard, for example prod*.
  • get_tag: Get the metadata of one tag by exact name: description and custom properties.

BYOK key

You bring your own Splunk Observability Metrics Splunk Observability Cloud user API access token (https://help.splunk.com/en/splunk-observability-cloud/administer/authentication-and-security/authentication-tokens/user-api-access-tokens). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.us0.signalfx.com, api.us1.signalfx.com, api.eu0.signalfx.com, api.eu1.signalfx.com, api.eu2.signalfx.com, api.au0.signalfx.com, api.jp0.signalfx.com, api.sg0.signalfx.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Splunk Observability Metrics API (api.us0.signalfx.com, api.us1.signalfx.com, api.eu0.signalfx.com, api.eu1.signalfx.com, api.eu2.signalfx.com, api.au0.signalfx.com, api.jp0.signalfx.com, api.sg0.signalfx.com) with a BYOK key; documentation: https://dev.splunk.com/observability/reference/api/metrics_metadata/latest. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Splunk Observability Metrics. Splunk Observability Metrics and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Splunk Observability Metrics account.

Built for: Worldwide. Languages: English.