Splunk Observability Endpoint Target
A Splunk Observability Endpoint target connects Cisco Workflows to Splunk Observability Cloud management APIs. The target stores endpoint details referenced by Generic Splunk Observability API Request and generated Splunk Observability workflows.
Before You Begin
Make sure you have:
-
Access to a Splunk Observability Cloud organization with permission to use the required management APIs.
-
The realm-specific API host name, such as
api.us1.observability.splunkcloud.com. -
A saved Splunk Observability Access Token account key.
Creating Splunk Observability Targets
-
In Workflows, go to Automation > Targets.
-
Select New Target.
-
Select Splunk Observability Endpoint.
-
Enter a display name and description.
-
Select a saved Splunk Observability Access Token account key.
-
In Connection, enter:
-
Protocol: HTTPS
-
Host: The realm-specific API host; do not include protocol or port.
-
Port: The API port; the default is
443.
-
-
Configure proxy settings only when your environment requires an outbound proxy.
-
Select Save.
After saving the target, use it with Generic Splunk Observability API Request. Provide a relative API path that includes the API version, for example /v2/organization. Workflows verifies the connection with GET /v2/organization.
Target Fields
| Field | Required | Description |
|
Protocol |
Yes |
HTTPS only. |
|
Host |
Yes |
Realm-specific API host, such as |
|
Port |
No |
HTTPS port for the management API. Default: |