Integrations · Splunk
A Guild agent reads and resolves Splunk Observability Cloud incidents, queries detectors, manages dashboards and SLOs, and updates teams, without your access token ever leaving Guild’s servers. Guild stores the credential server-side and injects it per request, so agent code never sees it. Credential policies let you restrict which operations each agent may call, and every request is auditable through Guild’s credential proxy.
Book a demo
See how teams govern agents that use Splunk.
Talk to sales
Get access to Guild, then connect Splunk to your first agent.
What the Splunk integration exposes
The tools cover Splunk Observability Cloud detectors, incidents, dashboards and charts, metric metadata and time series, SLOs, muting rules, teams, org tokens, integrations, SignalFlow computations, visibility filters, data links, navigators, and organization members. Tools follow the splunk_ prefix convention and are imported from guildai~splunk. Use pick() to give an agent only the tools it needs.How it works
1
Find your realm
In Splunk Observability Cloud, your realm, such as us1 or eu0, appears in your organization settings and profile.
2
Create an access token
Create an access token with the API scope in Splunk Observability Cloud.
3
Connect in Guild
Go to Access & setup > Credentials, click Connect, select splunk, enter the realm in Realm and the token in API Key. See Credentials for workspace, member, and agent-scoped options.
Why Splunk access needs governing in Guild
Guild’s credential proxy holds the token server-side and never exposes it to agent code, prompts, or containers. Credential policies let you write ALLOW and DENY rules that the proxy enforces before any request reaches Splunk, filtering by operation name, HTTP method, agent identity, or workspace. You can scope the credential itself to the whole account, a single workspace, a specific member, or one installed agent, as described in Credentials. A scoped DENY rule blocks destructive operations such as splunk_delete_single_detector across every agent on a shared credential, while a narrower ALLOW rule limits a specialist agent to read-only incident tools. Without these controls, every agent that can reach the credential can reach every operation it covers.About the Splunk integration
The Splunk integration connects agents to the Splunk Observability Cloud API: detectors, incidents, dashboards and charts, metric metadata, SLOs, and teams. It doesn’t search Splunk Enterprise or Splunk Cloud Platform logs. The integration isguildai~splunk.
Authentication
- Type: Access token
- Header: Guild sends the token in the
X-SF-Tokenrequest header - Realm: Requests go to
https://api.<realm>.observability.splunkcloud.com, using the realm you enter when you connect
Setup
1
Find your realm
In Splunk Observability Cloud, your realm, such as
us1 or eu0, is shown in your organization settings and profile.2
Create an access token
Create an access token with the API scope in Splunk Observability Cloud.
3
Connect Splunk
In Guild, go to Access & setup > Credentials, click Connect, select splunk, and enter the realm in Realm and the token in API Key.
Usage
Selecting specific tools
Tools are named with thesplunk_ prefix. Use pick() to include only what your agent needs.
Tools
Tools in the latest published version ofguildai~splunk:
All 122 tools
All 122 tools
Frequently asked questions
Can a Guild agent search Splunk Enterprise or Splunk Cloud Platform logs?
Can a Guild agent search Splunk Enterprise or Splunk Cloud Platform logs?
No. The integration connects to the Splunk Observability Cloud API only. It does not search Splunk Enterprise or Splunk Cloud Platform logs.
How does Guild authenticate requests to Splunk?
How does Guild authenticate requests to Splunk?
Guild sends the access token in the X-SF-Token request header. The token is stored server-side and agent code never sees it.
Can I limit which Splunk operations an agent is allowed to call?
Can I limit which Splunk operations an agent is allowed to call?
Yes. Credential policies let you write ALLOW and DENY rules matched against operation names, HTTP methods, agents, and workspaces. Guild’s credential proxy enforces the rules before any request leaves Guild.
Does the Splunk integration receive webhook events from Splunk?
Does the Splunk integration receive webhook events from Splunk?
Not yet. The catalog entry lists no webhook events for this integration, so agents cannot be triggered by inbound Splunk alerts through Guild’s event system.
Put a governed agent on Splunk Observability Cloud this week
Book a demo
See how teams govern agents that use Splunk.
Talk to sales
Get access to Guild, then connect Splunk to your first agent.