Splunk VMware TA Setup
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
- VMware, vCenter, ESXi logs, VMware metrics, VMware indexes, VMware extractions, or making VMware data ready for
Splunk ITSI, Enterprise Security, Monitoring Console, or infrastructure dashboards.
- Preview and review the splunk vmware ta setup 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-vmware-ta-setup/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-vmware-ta-setup/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 |
TA Completion Gate
For every TA/add-on or dashboard companion run, satisfy the shared
TA completion gate: configure and enable the
data ingest path owned by this skill or its required companion, validate events
or metrics in the target indexes/source types, and verify any
pre-built/package-shipped dashboards are visible, macro-aligned, and returning
data. If the package ships no dashboards, record that evidence explicitly and
hand off dashboard use to the consuming app, ES/ITSI/ARI content, or readiness
doctor.
Render-first workflow for VMware data onboarding through Splunk Supported
Add-ons. VMware coverage spans multiple glossary entries: VMware, vCenter Logs,
ESXi Logs, VMware Extractions, VMware Indexes, VMware Metrics, and VMware
Metrics Indexes. Treat them as one deployment plan so index placement,
collection ownership, search-time knowledge, and ITSI readiness stay aligned.
Safety Rules
- Never ask for or pass vCenter passwords, appliance credentials, or Splunk
secrets in chat, argv, or environment-variable prefixes.
- Use local secret files for credentials, then configure accounts through the
owning add-on UI or REST handler.
- Do not deploy credential-bearing VMware collection apps broadly through
Deployment Server. Run each vCenter/DCN collection path on an explicit owner
to avoid duplicate inventory, task, event, and performance collection.
- Splunk Cloud search-tier package install is separate from customer-managed
data collection nodes, heavy forwarders, Universal Forwarders, and syslog
collectors.
Workflow
- Render the VMware package:
bash skills/splunk-vmware-ta-setup/scripts/setup.sh --render \
--event-index vmware \
--metrics-index vmware_metrics \
--esxi-index vmware_esxi \
--vcenter-account vc_prod
Review vmware-plan.md, indexes.conf.template,
vcenter-account-runbook.md, esxi-syslog-runbook.md, and
itsi-readiness.md.
Install VMware packages through splunk-app-install or a customer-approved
package source. If package files are available locally:
bash skills/splunk-vmware-ta-setup/scripts/setup.sh --install-package /path/to/package.spl
- Configure vCenter/DCN collection on one owner, configure ESXi syslog to the
selected syslog path, then run validation:
bash skills/splunk-vmware-ta-setup/scripts/validate.sh --rendered-dir splunk-vmware-ta-rendered
Use splunk-supported-addons-setup for glossary resolution and package
handoff, splunk-data-source-readiness-doctor after data lands, and
splunk-itsi-config for service/entity/KPI modeling.
1---2name: splunk-vmware-ta-setup3description: "Use when the user asks about VMware, vCenter, ESXi logs, VMware metrics, VMware indexes, VMware4 extractions, or making VMware data ready for Splunk ITSI, Enterprise Security, Monitoring Console, or5 infrastructure dashboards. Install, render, configure, and validate Splunk Supported Add-on coverage for6 VMware, including the VMware app/add-on family, vCenter collection planning, ESXi syslog handoffs, event7 and metric index templates, deployment role placement, ITSI readiness, and post-ingest validation."8compatibility: "Splunk Cloud Platform 10.5.2605: conditional. Follow documented package, entitlement, topology, and customer-managed runtime guardrails; self-managed paths remain on the public 10.4 baseline."9metadata:10 source: https://skillmd.com/skills/chambear2809/splunk-vmware-ta-setup11 splunk_cloud_10_5: "conditional"12 compatibility_verified: "2026-08-20"13---1415# Splunk VMware TA Setup1617## Prerequisites1819| Tool or access | Purpose | Verify |20|---|---|---|21| Bash and Python 3 | Run bundled setup and validation helpers | `bash --version && python3 --version` |22| Required product/platform access | Inspect or configure the selected target | Complete the documented preflight |23| Credential files for live modes | Keep secrets out of chat | Verify paths only |2425## Workflow Overview2627```text28┌───────────┐ ┌───────────────┐ ┌───────────────┐ ┌─────────────────┐29│ Preflight │ → │ Render/review │ → │ Apply/handoff │ → │ Validate evidence │30└───────────┘ └───────────────┘ └───────────────┘ └─────────────────┘31```3233## When to Activate3435- VMware, vCenter, ESXi logs, VMware metrics, VMware indexes, VMware extractions, or making VMware data ready for36 Splunk ITSI, Enterprise Security, Monitoring Console, or infrastructure dashboards.37- Preview and review the splunk vmware ta setup workflow before any live apply phase.38- Diagnose failed prerequisites, generated assets, configuration, or validation evidence.3940## Scope4142Follow the documented read-only or render-first path whenever it is available.43This skill does not imply permission to mutate live systems. Require explicit44apply flags, protected credentials, and operator review for state changes.4546## Examples4748Inspect the supported setup modes before selecting one:4950```bash51bash skills/splunk-vmware-ta-setup/scripts/setup.sh --help52```5354Expected output: usage, supported modes, and required arguments are displayed55without changing the target environment.5657Inspect validation modes before running completion checks:5859```bash60bash skills/splunk-vmware-ta-setup/scripts/validate.sh --help61```6263Expected output: offline, live, and completion options are displayed when the64skill supports them; help exits without mutation.6566## Troubleshooting6768| Issue | Cause | Resolution |69|---|---|---|70| Preflight fails | A required tool or access path is missing | Resolve it before rendering or applying |71| Rendered assets are incomplete | Required non-secret inputs are absent | Complete intake and render again |72| Apply is blocked | Review, credentials, or explicit acceptance is missing | Use the documented handoff |73| Validation is incomplete | Live evidence is unavailable | Record the gap and keep completion open |7475## TA Completion Gate7677For every TA/add-on or dashboard companion run, satisfy the shared78[TA completion gate](../shared/ta_completion_gate.md): configure and enable the79data ingest path owned by this skill or its required companion, validate events80or metrics in the target indexes/source types, and verify any81pre-built/package-shipped dashboards are visible, macro-aligned, and returning82data. If the package ships no dashboards, record that evidence explicitly and83hand off dashboard use to the consuming app, ES/ITSI/ARI content, or readiness84doctor.8586Render-first workflow for VMware data onboarding through Splunk Supported87Add-ons. VMware coverage spans multiple glossary entries: VMware, vCenter Logs,88ESXi Logs, VMware Extractions, VMware Indexes, VMware Metrics, and VMware89Metrics Indexes. Treat them as one deployment plan so index placement,90collection ownership, search-time knowledge, and ITSI readiness stay aligned.9192## Safety Rules9394- Never ask for or pass vCenter passwords, appliance credentials, or Splunk95 secrets in chat, argv, or environment-variable prefixes.96- Use local secret files for credentials, then configure accounts through the97 owning add-on UI or REST handler.98- Do not deploy credential-bearing VMware collection apps broadly through99 Deployment Server. Run each vCenter/DCN collection path on an explicit owner100 to avoid duplicate inventory, task, event, and performance collection.101- Splunk Cloud search-tier package install is separate from customer-managed102 data collection nodes, heavy forwarders, Universal Forwarders, and syslog103 collectors.104105## Workflow1061071. Render the VMware package:108109```bash110bash skills/splunk-vmware-ta-setup/scripts/setup.sh --render \111 --event-index vmware \112 --metrics-index vmware_metrics \113 --esxi-index vmware_esxi \114 --vcenter-account vc_prod115```1161172. Review `vmware-plan.md`, `indexes.conf.template`,118 `vcenter-account-runbook.md`, `esxi-syslog-runbook.md`, and119 `itsi-readiness.md`.1201213. Install VMware packages through `splunk-app-install` or a customer-approved122 package source. If package files are available locally:123124```bash125bash skills/splunk-vmware-ta-setup/scripts/setup.sh --install-package /path/to/package.spl126```1271284. Configure vCenter/DCN collection on one owner, configure ESXi syslog to the129 selected syslog path, then run validation:130131```bash132bash skills/splunk-vmware-ta-setup/scripts/validate.sh --rendered-dir splunk-vmware-ta-rendered133```134135Use `splunk-supported-addons-setup` for glossary resolution and package136handoff, `splunk-data-source-readiness-doctor` after data lands, and137`splunk-itsi-config` for service/entity/KPI modeling.