splunk-observability-native-ops

You render native-ops specs to generate payloads and deeplinks for Splunk Observability detectors and alert routing. The workflow validates rules and creates handoffs before any live changes are applied to your environment.

A render-first workflow generates Splunk Observability payloads, deeplinks, and handoffs for review before execution. It enforces validation rules and requires explicit safety gates to apply any live changes to your environment.

Yes, you can apply muting rules and SLOs across Splunk Observability detectors, synthetics, APM, RUM, and logs. The skill restricts API surfaces to documented endpoints and blocks unsupported services during configuration.

To apply live changes to Splunk Observability native ops, you need a rendered plan, realm context, and an authentication token. The skill enforces these requirements to ensure safe and auditable updates.

Yes, Splunk Observability automation supports On-Call handoffs by generating them as part of the rendered native-ops spec. This ensures deterministic updates are properly routed and validated before execution.

Unsupported services are blocked during Splunk Observability configuration to enforce validation rules and restrict API surfaces to documented endpoints. This prevents unauthorized or unsafe changes to detectors and alert routing.