Splunk Observability Cisco Nexus Integration
Prerequisites
| Tool or access |
Purpose |
Verify |
| Bash and Python 3 |
Run bundled setup and validation helpers |
bash --version && python3 --version |
| Required product/platform access |
Inspect or configure the selected target |
Complete the documented preflight |
| Credential files for live modes |
Keep secrets out of chat |
Verify paths only |
Workflow Overview
┌───────────┐ ┌───────────────┐ ┌───────────────┐ ┌─────────────────┐
│ Preflight │ → │ Render/review │ → │ Apply/handoff │ → │ Validate evidence │
└───────────┘ └───────────────┘ └───────────────┘ └─────────────────┘
When to Activate
- Send Cisco Nexus, NX-OS, IOS-XE, or IOS-XR device metrics to Splunk Observability Cloud, configure the cisco_os
receiver, set up multi-device Nexus telemetry, or render dashboards/detectors for Cisco data center fabric.
- Preview and review the splunk observability cisco nexus integration workflow before any live apply phase.
- Diagnose failed prerequisites, generated assets, configuration, or validation evidence.
Scope
Follow the documented read-only or render-first path whenever it is available.
This skill does not imply permission to mutate live systems. Require explicit
apply flags, protected credentials, and operator review for state changes.
Examples
Inspect the supported setup modes before selecting one:
bash skills/splunk-observability-cisco-nexus-integration/scripts/setup.sh --help
Expected output: usage, supported modes, and required arguments are displayed
without changing the target environment.
Inspect validation modes before running completion checks:
bash skills/splunk-observability-cisco-nexus-integration/scripts/validate.sh --help
Expected output: offline, live, and completion options are displayed when the
skill supports them; help exits without mutation.
Troubleshooting
| Issue |
Cause |
Resolution |
| Preflight fails |
A required tool or access path is missing |
Resolve it before rendering or applying |
| Rendered assets are incomplete |
Required non-secret inputs are absent |
Complete intake and render again |
| Apply is blocked |
Review, credentials, or explicit acceptance is missing |
Use the documented handoff |
| Validation is incomplete |
Live evidence is unavailable |
Record the gap and keep completion open |
This is a standalone reusable skill for Cisco Nexus 9000 (and any cisco_os-receiver-supported device) metrics in Splunk Observability Cloud. It is independent of the AI Pod umbrella — useful for any data center with Nexus fabric. The AI Pod skill composes this skill via subprocess + yq deep-merge.
The Splunk Platform TA path for Nexus / ACI / Nexus Dashboard lives in cisco-dc-networking-setup. That's a different layer (Splunk Platform side); this skill is the O11y side.
What it renders
splunk-otel-overlay/values.overlay.yaml — clusterReceiver.config.receivers.cisco_os block in the new multi-device + global-scrapers format (cisco_os receiver in upstream contrib v0.149.0+). Devices reference K8s Secret-mounted creds; supports password or key_file per device. Scrapers: system (cisco.device.up, system.cpu.utilization, system.memory.utilization) and interfaces (system.network.io, system.network.errors, system.network.packet.dropped|count, system.network.interface.status).
splunk-otel-overlay/cisco-os-pipeline.yaml — metrics/cisco-os-metrics pipeline with signalfx exporter and memory_limiter|batch|resourcedetection|resource processors.
secrets/cisco-nexus-ssh-secret.yaml — K8s Secret manifest stub (rendered with placeholders; user creates with kubectl create secret generic --from-file=...). Renderer never reads SSH passwords.
dashboards/<name>.signalflow.yaml — Nexus port utilization, packet errors, drop rates, system CPU/memory, interface status.
detectors/<name>.yaml — interface down, packet drop rate threshold, memory pressure.
scripts/setup.sh, render_assets.py, validate.sh, handoff-base-collector.sh, handoff-dashboards.sh, handoff-detectors.sh.
metadata.json.
Safety Rules
- Never ask for Cisco Nexus SSH passwords or SSH keys in conversation.
- The renderer writes a K8s Secret manifest stub with placeholder values; the operator creates the actual Secret out-of-band with
kubectl create secret generic --from-file=....
--o11y-token-file flag is for the Splunk Observability Org access token (passed through to base collector). Reject --o11y-token, --access-token, --token, --bearer-token, --api-token, --sf-token.
- Token files must be
chmod 600; --allow-loose-token-perms overrides with WARN.
Primary Workflow
Identify your Nexus devices (hostnames or management IPs) and gather per-device SSH credentials (out-of-band).
Render:
bash skills/splunk-observability-cisco-nexus-integration/scripts/setup.sh \
--render --validate \
--realm us0 \
--cluster-name lab-cluster \
--nexus-device "core-switch-01:192.168.1.10" \
--nexus-device "core-switch-02:192.168.1.11" \
--output-dir splunk-observability-cisco-nexus-rendered
Review splunk-observability-cisco-nexus-rendered/ and create the SSH credentials Secret:
kubectl create secret generic cisco-nexus-ssh \
--from-literal=username=splunk-otel \
--from-file=password=/tmp/nexus_password \
-n splunk-otel
Apply directly via the skill (recommended). This merges the rendered
overlay onto the existing Splunk OTel collector helm release values and
runs helm upgrade --atomic. Refuses without --accept-k8s-apply,
refuses if the cisco-nexus-ssh Secret from step 3 is missing, and
prints the active kube-context first:
bash skills/splunk-observability-cisco-nexus-integration/scripts/setup.sh \
--apply --accept-k8s-apply \
--realm us0 --cluster-name lab-cluster \
--nexus-device "core-switch-01:192.168.1.10" \
--nexus-device "core-switch-02:192.168.1.11"
--apply --accept-k8s-apply --dry-run runs helm upgrade --dry-run
without mutating the cluster.
For dashboards / detectors, the rendered handoff scripts call into the
owning skills:
bash splunk-observability-cisco-nexus-rendered/scripts/handoff-dashboards.sh
bash splunk-observability-cisco-nexus-rendered/scripts/handoff-detectors.sh
Hand-offs
Out of scope (companion skills)
Validation
bash skills/splunk-observability-cisco-nexus-integration/scripts/validate.sh
Static checks: overlay shape, Secret manifest placeholder validity, no inline credentials. With --live: helm status, OTel collector pod logs grep for cisco_os scrape errors.
See reference.md and the references/ annexes for the cisco_os receiver schema, multi-device config, SSH secrets, dashboards catalog, and troubleshooting.
1---2name: splunk-observability-cisco-nexus-integration3description: "Use when the user asks to send Cisco Nexus, NX-OS, IOS-XE, or IOS-XR device metrics to Splunk4 Observability Cloud, configure the cisco_os receiver, set up multi-device Nexus telemetry, or render5 dashboards/detectors for Cisco data center fabric. Standalone reusable skill for sending Cisco Nexus6 9000 metrics to Splunk Observability Cloud via the OTel cisco_os receiver (multi-device + global7 scrapers format, PR #45562, currently at v0.149.0+ in upstream contrib). Renders the clusterReceiver8 overlay, K8s Secret manifest stub for SSH credentials, dashboards and starter detectors. Hands off base9 collector to splunk-observability-otel-collector-setup, dashboards to splunk-observability-dashboard-10 builder, detectors to splunk-observability-native-ops. Independent of Cisco AI Pod -- useful for any11 data center with Nexus fabric. Companion to cisco-dc-networking-setup (Splunk Platform TA for Nexus /12 ACI / Nexus Dashboard)."13compatibility: "No direct Splunk Platform runtime dependency. This workflow can be used alongside Splunk Cloud Platform 10.5.2605 through its documented external APIs or handoffs."14metadata:15 source: https://skillmd.com/skills/chambear2809/splunk-observability-cisco-nexus-integration16 splunk_cloud_10_5: "not-applicable"17 compatibility_verified: "2026-08-20"18---1920# Splunk Observability Cisco Nexus Integration2122## Prerequisites2324| Tool or access | Purpose | Verify |25|---|---|---|26| Bash and Python 3 | Run bundled setup and validation helpers | `bash --version && python3 --version` |27| Required product/platform access | Inspect or configure the selected target | Complete the documented preflight |28| Credential files for live modes | Keep secrets out of chat | Verify paths only |2930## Workflow Overview3132```text33┌───────────┐ ┌───────────────┐ ┌───────────────┐ ┌─────────────────┐34│ Preflight │ → │ Render/review │ → │ Apply/handoff │ → │ Validate evidence │35└───────────┘ └───────────────┘ └───────────────┘ └─────────────────┘36```3738## When to Activate3940- Send Cisco Nexus, NX-OS, IOS-XE, or IOS-XR device metrics to Splunk Observability Cloud, configure the cisco_os41 receiver, set up multi-device Nexus telemetry, or render dashboards/detectors for Cisco data center fabric.42- Preview and review the splunk observability cisco nexus integration workflow before any live apply phase.43- Diagnose failed prerequisites, generated assets, configuration, or validation evidence.4445## Scope4647Follow the documented read-only or render-first path whenever it is available.48This skill does not imply permission to mutate live systems. Require explicit49apply flags, protected credentials, and operator review for state changes.5051## Examples5253Inspect the supported setup modes before selecting one:5455```bash56bash skills/splunk-observability-cisco-nexus-integration/scripts/setup.sh --help57```5859Expected output: usage, supported modes, and required arguments are displayed60without changing the target environment.6162Inspect validation modes before running completion checks:6364```bash65bash skills/splunk-observability-cisco-nexus-integration/scripts/validate.sh --help66```6768Expected output: offline, live, and completion options are displayed when the69skill supports them; help exits without mutation.7071## Troubleshooting7273| Issue | Cause | Resolution |74|---|---|---|75| Preflight fails | A required tool or access path is missing | Resolve it before rendering or applying |76| Rendered assets are incomplete | Required non-secret inputs are absent | Complete intake and render again |77| Apply is blocked | Review, credentials, or explicit acceptance is missing | Use the documented handoff |78| Validation is incomplete | Live evidence is unavailable | Record the gap and keep completion open |7980This is a **standalone reusable skill** for Cisco Nexus 9000 (and any cisco_os-receiver-supported device) metrics in Splunk Observability Cloud. It is **independent of the AI Pod** umbrella — useful for any data center with Nexus fabric. The AI Pod skill composes this skill via subprocess + yq deep-merge.8182The Splunk Platform TA path for Nexus / ACI / Nexus Dashboard lives in [cisco-dc-networking-setup](../cisco-dc-networking-setup/SKILL.md). That's a different layer (Splunk Platform side); this skill is the O11y side.8384## What it renders8586- `splunk-otel-overlay/values.overlay.yaml` — `clusterReceiver.config.receivers.cisco_os` block in the new multi-device + global-scrapers format (cisco_os receiver in upstream contrib v0.149.0+). Devices reference K8s Secret-mounted creds; supports `password` or `key_file` per device. Scrapers: `system` (`cisco.device.up`, `system.cpu.utilization`, `system.memory.utilization`) and `interfaces` (`system.network.io`, `system.network.errors`, `system.network.packet.dropped|count`, `system.network.interface.status`).87- `splunk-otel-overlay/cisco-os-pipeline.yaml` — `metrics/cisco-os-metrics` pipeline with `signalfx` exporter and `memory_limiter|batch|resourcedetection|resource` processors.88- `secrets/cisco-nexus-ssh-secret.yaml` — K8s Secret manifest stub (rendered with placeholders; user creates with `kubectl create secret generic --from-file=...`). Renderer never reads SSH passwords.89- `dashboards/<name>.signalflow.yaml` — Nexus port utilization, packet errors, drop rates, system CPU/memory, interface status.90- `detectors/<name>.yaml` — interface down, packet drop rate threshold, memory pressure.91- `scripts/setup.sh`, `render_assets.py`, `validate.sh`, `handoff-base-collector.sh`, `handoff-dashboards.sh`, `handoff-detectors.sh`.92- `metadata.json`.9394## Safety Rules9596- Never ask for Cisco Nexus SSH passwords or SSH keys in conversation.97- The renderer writes a K8s Secret manifest stub with placeholder values; the operator creates the actual Secret out-of-band with `kubectl create secret generic --from-file=...`.98- `--o11y-token-file` flag is for the Splunk Observability Org access token (passed through to base collector). Reject `--o11y-token`, `--access-token`, `--token`, `--bearer-token`, `--api-token`, `--sf-token`.99- Token files must be `chmod 600`; `--allow-loose-token-perms` overrides with WARN.100101## Primary Workflow1021031. Identify your Nexus devices (hostnames or management IPs) and gather per-device SSH credentials (out-of-band).1041052. Render:106107 ```bash108 bash skills/splunk-observability-cisco-nexus-integration/scripts/setup.sh \109 --render --validate \110 --realm us0 \111 --cluster-name lab-cluster \112 --nexus-device "core-switch-01:192.168.1.10" \113 --nexus-device "core-switch-02:192.168.1.11" \114 --output-dir splunk-observability-cisco-nexus-rendered115 ```1161173. Review `splunk-observability-cisco-nexus-rendered/` and create the SSH credentials Secret:118119 ```bash120 kubectl create secret generic cisco-nexus-ssh \121 --from-literal=username=splunk-otel \122 --from-file=password=/tmp/nexus_password \123 -n splunk-otel124 ```1251264. Apply directly via the skill (recommended). This merges the rendered127 overlay onto the existing Splunk OTel collector helm release values and128 runs `helm upgrade --atomic`. Refuses without `--accept-k8s-apply`,129 refuses if the `cisco-nexus-ssh` Secret from step 3 is missing, and130 prints the active kube-context first:131132 ```bash133 bash skills/splunk-observability-cisco-nexus-integration/scripts/setup.sh \134 --apply --accept-k8s-apply \135 --realm us0 --cluster-name lab-cluster \136 --nexus-device "core-switch-01:192.168.1.10" \137 --nexus-device "core-switch-02:192.168.1.11"138 ```139140 `--apply --accept-k8s-apply --dry-run` runs `helm upgrade --dry-run`141 without mutating the cluster.142143 For dashboards / detectors, the rendered handoff scripts call into the144 owning skills:145146 ```bash147 bash splunk-observability-cisco-nexus-rendered/scripts/handoff-dashboards.sh148 bash splunk-observability-cisco-nexus-rendered/scripts/handoff-detectors.sh149 ```150151## Hand-offs152153- Splunk OTel Collector base install: [splunk-observability-otel-collector-setup](../splunk-observability-otel-collector-setup/SKILL.md).154- Dashboards: [splunk-observability-dashboard-builder](../splunk-observability-dashboard-builder/SKILL.md).155- Detectors: [splunk-observability-native-ops](../splunk-observability-native-ops/SKILL.md).156157## Out of scope (companion skills)158159- Splunk Platform TA path for Nexus / ACI / Nexus Dashboard: [cisco-dc-networking-setup](../cisco-dc-networking-setup/SKILL.md).160- Cisco Catalyst Center / ISE / SD-WAN / Cyber Vision: [cisco-catalyst-ta-setup](../cisco-catalyst-ta-setup/SKILL.md).161162## Validation163164```bash165bash skills/splunk-observability-cisco-nexus-integration/scripts/validate.sh166```167168Static checks: overlay shape, Secret manifest placeholder validity, no inline credentials. With `--live`: `helm status`, OTel collector pod logs grep for `cisco_os` scrape errors.169170See `reference.md` and the `references/` annexes for the cisco_os receiver schema, multi-device config, SSH secrets, dashboards catalog, and troubleshooting.