splunk-observability-cisco-intersight-integration

To send Cisco Intersight UCS metrics to Splunk Observability Cloud, you can render an isolated OTel deployment namespace, a credentials Secret stub, and OTLP pipeline manifests using this Skill. It generates the necessary ConfigMaps and deployments to wire Intersight metrics directly into your observability platform.

Rendering Intersight metrics into Splunk O11y produces an isolated intersight-otel namespace, a credentials Secret stub, deployment manifests, an OTLP ConfigMap pipeline overlay, dashboards, detectors, and handoff scripts. These artifacts enable secure and repeatable metric collection rollouts.

You validate and apply Splunk Observability manifests safely by using the provided scripts to run render, validate, preflight, and dry-run workflows before applying. The Skill enforces safety checks to ensure secret material is not embedded directly in the manifests during this process.

No, the Intersight OTel integration does not embed API keys directly in the Kubernetes manifests. It enforces strict secret handling by generating a credentials Secret stub, ensuring sensitive material remains isolated and secure throughout the render and apply workflows.

Yes, you can generate Splunk O11y dashboards and detectors for Cisco Intersight metrics. The Skill renders these observability components alongside handoff scripts, allowing you to visualize UCS metrics and set up automated alerts within Splunk Observability Cloud.