Splunk Observability Cloud
Connect your client's Splunk Observability Cloud with a key they paste, and call its API through Operate As.
- Connects by
- Pasting a API access token
- Category
- Developer tools
- Services
- 1
- Tools
- Pass-through only
| Service | Key | Base URL |
|---|---|---|
| Splunk Observability Cloud | splunk-observability | https://api.{realm}.signalfx.com/v2 |
Your client also types their realm (In your profile, such as us1 or eu0).
Connecting
Your client makes a API access token in their Splunk Observability Cloud settings and pastes it on their link. Operate As tries it with Splunk Observability Cloud before saving it, and stores it encrypted. See Services connected with an API key.
curl https://api.operate.as/v1/me/clients \ -H "Authorization: Bearer $OPERATE_AS_API_KEY"[ { "id": "6f1c2a7e-...", "name": "Miller Dental", "services": [ "splunk-observability" ] }]Permissions
| What the client reads | Permission it asks for |
|---|---|
| Use the Splunk Observability Cloud key you paste, with only the access you gave that key | Chosen on the provider's screen |
Pass-through
Splunk Observability Cloud has no ready-made tools yet. Call any endpoint of its API through Operate As instead, with the client's access attached.
Add the client
In Clients, add your client and select Splunk Observability Cloud. Then send them their link.
Your client connects
They paste a API access token from their Splunk Observability Cloud settings.
Find the endpoint
Pick the call from Splunk Observability Cloud's own API docs. Your path is everything after https://api.{realm}.signalfx.com/v2, with the parts in braces filled in from your client's account.
Send it through Operate As
Use the client's ID, the service key splunk-observability and that path. Your Operate As key goes in Authorization; the client's access is added for you.
See Pass-through requests for the full request and response format.
curl "https://api.operate.as/v1/clients/6f1c2a7e-.../splunk-observability/dashboard" \ -H "Authorization: Bearer $OPERATE_AS_API_KEY"{ "status": 200, "data": { "…": "the service's own response" }, "encoding": "json"}When access ends
A key works until your client deletes it in Splunk Observability Cloud. They can paste a new one on the same link at any time, and your workflows carry on without changes.
See Keeping access alive and Removing access.
{ "status": 401, "data": { "…": "the service's own error" }, "encoding": "json"}