chambear2809 Database Supported Add-ons 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
- Onboard SQL Server, MySQL, Oracle Database, database logs, or supported database TA readiness in Splunk.
- Preview and review the splunk database 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-database-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-database-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 verified database add-ons:
Splunk_TA_microsoft-sqlserver3.1.0, Splunkbase2648Splunk_TA_mysql3.2.0, Splunkbase2848Splunk_TA_oracle4.2.0, Splunkbase1910
Workflow
bash skills/splunk-database-ta-setup/scripts/setup.sh --phase render \
--products mssql,mysql,oracle --index database
Review the rendered DB Connect handoff, SQL Server host input overlay, install commands, and validation SPL.
bash skills/splunk-database-ta-setup/scripts/setup.sh --install \
--products mssql,mysql,oracle --no-restart
bash skills/splunk-database-ta-setup/scripts/validate.sh --index database
Readiness handoff:
bash skills/splunk-data-source-readiness-doctor/scripts/setup.sh \
--phase collect --source-pack mssql_database,mysql_database,oracle_database
Secrets stay in DB Connect identities, add-on account storage, or protected local secret files. This skill never accepts database credentials as flags.