Splunk AppDynamics Dual Agent 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 Java dual-agent, Java Dual Signal mode, AGENT_DEPLOYMENT_MODE=dual,
-Dagent.deployment.mode=dual, Java OTLP export to a local collector, or coordinated collector-first then Java
restart rollout on local or SSH.
- Preview and review the splunk appdynamics dual agent 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-dual-agent-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-dual-agent-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 |
Owns production Java Dual Signal host configuration. The supported apply order
is collector first, Java second: configure and validate the local collector, then
write persistent Java startup settings and restart only approved app services.
bash skills/splunk-appdynamics-dual-agent-setup/scripts/setup.sh --render
bash skills/splunk-appdynamics-dual-agent-setup/scripts/setup.sh --apply preflight --spec dual-agent.yaml
bash skills/splunk-appdynamics-dual-agent-setup/scripts/setup.sh --apply all --spec dual-agent.yaml --accept-host-mutation --accept-app-restart
bash skills/splunk-appdynamics-dual-agent-setup/scripts/validate.sh --output-dir splunk-appdynamics-dual-agent-setup-rendered
What This Skill Covers
- Java Dual Signal startup configuration using
AGENT_DEPLOYMENT_MODE=dual
or equivalent system properties.
- OTLP trace export to a local collector, defaulting to
http://127.0.0.1:4318 and http/protobuf.
- Resource attributes for application, tier, node, and deployment environment.
- Linux systemd drop-ins, process env files or wrappers, Docker env files, and
Windows service environment guidance.
- Gated apply and rollback for local or SSH targets with backup manifests,
checksum verification, redacted reports, and generated rollback plans.
Guardrails
--accept-host-mutation is required before writing files or restarting
services.
--accept-remote-execution is required for SSH targets.
--accept-app-restart is required for Java service or container restarts.
--accept-full-restart is required when restart_strategy: full.
- Direct token, access-token, and API key flags are refused; use file-backed
fields in the spec.
- Referenced collector secret files must be non-empty and mode 600. Collector
apply writes a target-side mode-600 environment file; Docker and Windows
targets need an explicit
collector_credentials_ready_command.
1---2name: splunk-appdynamics-dual-agent-setup3description: "Use when the user asks for AppDynamics Java dual-agent, Java Dual Signal mode,4 AGENT_DEPLOYMENT_MODE=dual, -Dagent.deployment.mode=dual, Java OTLP export to a local collector, or5 coordinated collector-first then Java restart rollout on local or SSH hosts. Render, validate,6 preflight, apply, and rollback production Java Dual Signal AppDynamics agent configuration."7compatibility: "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."8metadata:9 source: https://skillmd.com/skills/chambear2809/splunk-appdynamics-dual-agent-setup10 splunk_cloud_10_5: "not-applicable"11 compatibility_verified: "2026-08-20"12---1314# Splunk AppDynamics Dual Agent Setup1516## Prerequisites1718| Tool or access | Purpose | Verify |19|---|---|---|20| Bash and Python 3 | Run bundled setup and validation helpers | `bash --version && python3 --version` |21| Required product/platform access | Inspect or configure the selected target | Complete the documented preflight |22| Credential files for live modes | Keep secrets out of chat | Verify paths only |2324## Workflow Overview2526```text27┌───────────┐ ┌───────────────┐ ┌───────────────┐ ┌─────────────────┐28│ Preflight │ → │ Render/review │ → │ Apply/handoff │ → │ Validate evidence │29└───────────┘ └───────────────┘ └───────────────┘ └─────────────────┘30```3132## When to Activate3334- The user asks for AppDynamics Java dual-agent, Java Dual Signal mode, AGENT_DEPLOYMENT_MODE=dual,35 -Dagent.deployment.mode=dual, Java OTLP export to a local collector, or coordinated collector-first then Java36 restart rollout on local or SSH.37- Preview and review the splunk appdynamics dual agent 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-appdynamics-dual-agent-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-appdynamics-dual-agent-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 |7475Owns production Java Dual Signal host configuration. The supported apply order76is collector first, Java second: configure and validate the local collector, then77write persistent Java startup settings and restart only approved app services.7879```bash80bash skills/splunk-appdynamics-dual-agent-setup/scripts/setup.sh --render81bash skills/splunk-appdynamics-dual-agent-setup/scripts/setup.sh --apply preflight --spec dual-agent.yaml82bash skills/splunk-appdynamics-dual-agent-setup/scripts/setup.sh --apply all --spec dual-agent.yaml --accept-host-mutation --accept-app-restart83bash skills/splunk-appdynamics-dual-agent-setup/scripts/validate.sh --output-dir splunk-appdynamics-dual-agent-setup-rendered84```8586## What This Skill Covers8788- Java Dual Signal startup configuration using `AGENT_DEPLOYMENT_MODE=dual`89 or equivalent system properties.90- OTLP trace export to a local collector, defaulting to91 `http://127.0.0.1:4318` and `http/protobuf`.92- Resource attributes for application, tier, node, and deployment environment.93- Linux systemd drop-ins, process env files or wrappers, Docker env files, and94 Windows service environment guidance.95- Gated apply and rollback for local or SSH targets with backup manifests,96 checksum verification, redacted reports, and generated rollback plans.9798## Guardrails99100- `--accept-host-mutation` is required before writing files or restarting101 services.102- `--accept-remote-execution` is required for SSH targets.103- `--accept-app-restart` is required for Java service or container restarts.104- `--accept-full-restart` is required when `restart_strategy: full`.105- Direct token, access-token, and API key flags are refused; use file-backed106 fields in the spec.107- Referenced collector secret files must be non-empty and mode 600. Collector108 apply writes a target-side mode-600 environment file; Docker and Windows109 targets need an explicit `collector_credentials_ready_command`.