About Splunk Observability Cloud
Splunk Observability Cloud (formerly SignalFx) is Splunk’s observability platform covering infrastructure monitoring, APM, synthetics, and detector-based alerting. Serval connects to a Splunk Observability Cloud organization using its realm (the regional instance identifier, e.g. us0, us1, eu0, jp0, au0) and an org access token, stored as a secret and attached to every request Serval makes on your behalf. An Instance Name distinguishes multiple connections in the same Serval workspace. Authentication: Org access token with the API authorization scope (custom header authentication). The token is stored as a secret and injected on every request as the X-SF-TOKEN header. There is no OAuth flow and no token refresh - the token is used as-is until you rotate it by editing the connection. Data sync: On-demand only. Serval calls the Splunk Observability Cloud API when a workflow step runs - there is no background sync.What the Splunk Observability Cloud integration enables
Get your credentials
Serval needs two pieces of information from Splunk Observability Cloud: your realm and an org access token with the API authorization scope. See Splunk: Create and manage authentication tokens for the official guide.Find your realm
Create an org access token
Check the token's permissions
Connect in Serval
All three fields are required.Enter the Realm
Enter the Access Token
Enter an Instance Name
Submit the form
Verifying the connection
When the connection is created, Serval runs a health check that confirms your token is valid and your realm is reachable. The integration also includes four named health-check workflows you can run at any time:- Validate Splunk Observability Cloud API Connection - lists detectors to confirm the realm and token work together.
- Check Splunk Observability Incidents Access - verifies Serval can read incidents (triggered alerts).
- Check Splunk Observability Dashboards Access - verifies Serval can read dashboards.
- Check Splunk Observability Teams Access - verifies Serval can read teams.
Gotchas and troubleshooting
Realm mismatch is the most common connect failure
Realm mismatch is the most common connect failure
Org access token, not a User API access token
Org access token, not a User API access token
Token roles bound what workflows can do
Token roles bound what workflows can do
Missing objects can return HTTP 200 with an empty body
Missing objects can return HTTP 200 with an empty body
List endpoints cap results at 10,000 objects
List endpoints cap results at 10,000 objects
Incidents list returns a bare array
Incidents list returns a bare array
Need help? Contact support@serval.com for assistance with your Splunk Observability Cloud integration.

