Splunk Appdynamics Setup

Splunk AppDynamics Setup

Prerequisites

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

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.