Splunk AppDynamics 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
- The user asks for AppDynamics setup, AppDynamics coverage, AppDynamics product routing, or a full AppDynamics
doctor/gap report.
- Preview and review the splunk appdynamics 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-appdynamics-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-appdynamics-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 |
This is the parent router for the AppDynamics suite. It does not mutate a
Controller, Kubernetes cluster, host, SAP system, or Splunk deployment directly.
It reads the taxonomy in references/appdynamics-taxonomy.yaml, routes each
feature family to its owner, and renders a coverage report with explicit source
URLs, validation methods, and apply boundaries.
cisco-appdynamics-setup remains the owner for Splunk_TA_AppDynamics on
Splunk Platform. This parent delegates that path instead of duplicating TA
automation.
Safe Workflow
bash skills/splunk-appdynamics-setup/scripts/setup.sh --render
bash skills/splunk-appdynamics-setup/scripts/validate.sh
python3 skills/splunk-appdynamics-setup/scripts/check_coverage.py
Render output defaults to splunk-appdynamics-setup-rendered/ and includes:
coverage-report.json
child-orchestration-plan.md
doctor-summary.md
apply-plan.sh
redacted-spec.json
Modes
--render: render coverage, child routing, and runbooks.
--apply: rejected at the parent. Invoke the routed child skill so its real
mutation gate, spec schema, and validation contract are enforced.
--validate: validate rendered coverage and artifact contracts. --live
executes only implemented read-only child probes (currently platform,
Controller licensing, and Kubernetes/O11y) and fails closed for workflows
whose only probe would mutate state or is not implemented.
--doctor: check taxonomy fields, ownership, wrapper files, and consistency
between actionable coverage claims and executable apply paths.
--quickstart: render and print the validation command.
--rollback: rejected at the parent; rollback belongs to the child that
created the mutation and evidence.
--json: emit machine-readable result.
Coverage Contract
A feature is covered only when taxonomy rows include:
- owner skill
- official source URL
- allowed coverage status
- validation method
- explicit apply boundary
Allowed statuses are api_apply, cli_apply, k8s_apply, delegated_apply,
render_runbook, validate_only, and not_applicable.
Secret Handling
Never ask for, paste, or render AppDynamics passwords, OAuth client secrets,
Events API keys, Database Visibility credentials, SAP passwords, or Splunk
tokens. Use chmod-600 files and the *-file flags exposed by child workflows.
1---2name: splunk-appdynamics-setup3description: "Use when the user asks for AppDynamics setup, AppDynamics coverage, AppDynamics product routing, or a4 full AppDynamics doctor/gap report. Coverage-first parent router for the Splunk AppDynamics skill suite.5 Resolves AppDynamics SaaS, On-Premises, Virtual Appliance, SAP Agent, APM, agents, Smart Agent, Cluster6 Agent, Infrastructure Visibility, Database Visibility, Analytics, EUM, Synthetic Monitoring, Log7 Observer Connect, Controller/admin, alerting, dashboards/reports, ThousandEyes integration, tags,8 extensions, Sensitive Data Collection and Security, release notes and references, product announcements,9 AIML, GPU Monitoring, Splunk AppDynamics for OpenTelemetry, Secure Application, Observability for AI,10 and Splunk Platform integration requests to the owning child skill, then emits a machine-readable11 coverage report from the checked-in taxonomy."12compatibility: "Splunk Cloud Platform 10.5.2605: delegated. Compatibility is determined by the canonical replacement or selected child skill; this compatibility alias or router does not own a runtime or package."13metadata:14 source: https://skillmd.com/skills/chambear2809/splunk-appdynamics-setup15 splunk_cloud_10_5: "delegated"16 compatibility_verified: "2026-08-20"17---1819# Splunk AppDynamics Setup2021## Prerequisites2223| Tool or access | Purpose | Verify |24|---|---|---|25| Bash and Python 3 | Run bundled setup and validation helpers | `bash --version && python3 --version` |26| Required product/platform access | Inspect or configure the selected target | Complete the documented preflight |27| Credential files for live modes | Keep secrets out of chat | Verify paths only |2829## Workflow Overview3031```text32┌───────────┐ ┌───────────────┐ ┌───────────────┐ ┌─────────────────┐33│ Preflight │ → │ Render/review │ → │ Apply/handoff │ → │ Validate evidence │34└───────────┘ └───────────────┘ └───────────────┘ └─────────────────┘35```3637## When to Activate3839- The user asks for AppDynamics setup, AppDynamics coverage, AppDynamics product routing, or a full AppDynamics40 doctor/gap report.41- Preview and review the splunk appdynamics setup workflow before any live apply phase.42- Diagnose failed prerequisites, generated assets, configuration, or validation evidence.4344## Scope4546Follow the documented read-only or render-first path whenever it is available.47This skill does not imply permission to mutate live systems. Require explicit48apply flags, protected credentials, and operator review for state changes.4950## Examples5152Inspect the supported setup modes before selecting one:5354```bash55bash skills/splunk-appdynamics-setup/scripts/setup.sh --help56```5758Expected output: usage, supported modes, and required arguments are displayed59without changing the target environment.6061Inspect validation modes before running completion checks:6263```bash64bash skills/splunk-appdynamics-setup/scripts/validate.sh --help65```6667Expected output: offline, live, and completion options are displayed when the68skill supports them; help exits without mutation.6970## Troubleshooting7172| Issue | Cause | Resolution |73|---|---|---|74| Preflight fails | A required tool or access path is missing | Resolve it before rendering or applying |75| Rendered assets are incomplete | Required non-secret inputs are absent | Complete intake and render again |76| Apply is blocked | Review, credentials, or explicit acceptance is missing | Use the documented handoff |77| Validation is incomplete | Live evidence is unavailable | Record the gap and keep completion open |7879This is the parent router for the AppDynamics suite. It does not mutate a80Controller, Kubernetes cluster, host, SAP system, or Splunk deployment directly.81It reads the taxonomy in `references/appdynamics-taxonomy.yaml`, routes each82feature family to its owner, and renders a coverage report with explicit source83URLs, validation methods, and apply boundaries.8485`cisco-appdynamics-setup` remains the owner for `Splunk_TA_AppDynamics` on86Splunk Platform. This parent delegates that path instead of duplicating TA87automation.8889## Safe Workflow9091```bash92bash skills/splunk-appdynamics-setup/scripts/setup.sh --render93bash skills/splunk-appdynamics-setup/scripts/validate.sh94python3 skills/splunk-appdynamics-setup/scripts/check_coverage.py95```9697Render output defaults to `splunk-appdynamics-setup-rendered/` and includes:9899- `coverage-report.json`100- `child-orchestration-plan.md`101- `doctor-summary.md`102- `apply-plan.sh`103- `redacted-spec.json`104105## Modes106107- `--render`: render coverage, child routing, and runbooks.108- `--apply`: rejected at the parent. Invoke the routed child skill so its real109 mutation gate, spec schema, and validation contract are enforced.110- `--validate`: validate rendered coverage and artifact contracts. `--live`111 executes only implemented read-only child probes (currently platform,112 Controller licensing, and Kubernetes/O11y) and fails closed for workflows113 whose only probe would mutate state or is not implemented.114- `--doctor`: check taxonomy fields, ownership, wrapper files, and consistency115 between actionable coverage claims and executable apply paths.116- `--quickstart`: render and print the validation command.117- `--rollback`: rejected at the parent; rollback belongs to the child that118 created the mutation and evidence.119- `--json`: emit machine-readable result.120121## Coverage Contract122123A feature is covered only when taxonomy rows include:124125- owner skill126- official source URL127- allowed coverage status128- validation method129- explicit apply boundary130131Allowed statuses are `api_apply`, `cli_apply`, `k8s_apply`, `delegated_apply`,132`render_runbook`, `validate_only`, and `not_applicable`.133134## Secret Handling135136Never ask for, paste, or render AppDynamics passwords, OAuth client secrets,137Events API keys, Database Visibility credentials, SAP passwords, or Splunk138tokens. Use chmod-600 files and the `*-file` flags exposed by child workflows.