Splunk AppDynamics Machine Agent OTel Collector 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 Machine Agent bundled OTel Collector, combined agent for infrastructure visibility, AppDynamics
collector YAML, local OTLP 4317/4318 listeners, or Splunk Observability plus AppDynamics OTel export from Linux,
Docker, or.
- Preview and review the splunk appdynamics machine agent otel collector 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-machine-agent-otel-collector-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-machine-agent-otel-collector-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 the AppDynamics Machine Agent bundled OTel Collector configuration. The
default is loopback-only OTLP reception, traces to Splunk Observability Cloud
and AppDynamics OTel, metrics to Splunk Observability Cloud, and logs disabled
unless a log destination is explicitly declared.
bash skills/splunk-appdynamics-machine-agent-otel-collector-setup/scripts/setup.sh --render
bash skills/splunk-appdynamics-machine-agent-otel-collector-setup/scripts/setup.sh --apply preflight --spec collector.yaml
bash skills/splunk-appdynamics-machine-agent-otel-collector-setup/scripts/setup.sh --apply collector --spec collector.yaml --accept-host-mutation
bash skills/splunk-appdynamics-machine-agent-otel-collector-setup/scripts/validate.sh --output-dir splunk-appdynamics-machine-agent-otel-collector-setup-rendered
What This Skill Covers
- Machine Agent combined mode for Linux RPM, Linux ZIP, Docker, and Windows ZIP
layouts.
- Bundled collector config rendering with OTLP gRPC on
127.0.0.1:4317 and
OTLP HTTP on 127.0.0.1:4318 by default.
- Splunk Observability token-file and AppDynamics API key-file placeholders.
- A chmod-600 runtime environment file generated on the target from those
secret files, plus a systemd drop-in for Linux service installs.
- Collector service/container restart, OTLP port checks, exporter health probes,
backup manifests, and rollback.
Guardrails
--accept-host-mutation is required before writing files or restarting the
collector.
--accept-remote-execution is required for SSH targets.
- Direct token, access-token, and API key flags are refused; use file-backed
fields in the spec.
- Referenced secret files must be non-empty and mode 600. Docker and Windows
targets require an explicit
collector_credentials_ready_command; a plain
container/service restart cannot attach new credentials.
- Mutation is refused when the expected bundled collector path or service or
container name cannot be confirmed from the spec and preflight.
1---2name: splunk-appdynamics-machine-agent-otel-collector-setup3description: "Use when the user asks for Machine Agent bundled OTel Collector, combined agent for infrastructure4 visibility, AppDynamics collector YAML, local OTLP 4317/4318 listeners, or Splunk Observability plus5 AppDynamics OTel export from Linux, Docker, or Windows Machine Agent installs. Render, validate,6 preflight, apply, and rollback the bundled OpenTelemetry Collector that runs with AppDynamics Machine7 Agent combined mode."8compatibility: "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."9metadata:10 source: https://skillmd.com/skills/chambear2809/splunk-appdynamics-machine-agent-otel-collector-setup11 splunk_cloud_10_5: "not-applicable"12 compatibility_verified: "2026-08-20"13---1415# Splunk AppDynamics Machine Agent OTel Collector 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- The user asks for Machine Agent bundled OTel Collector, combined agent for infrastructure visibility, AppDynamics36 collector YAML, local OTLP 4317/4318 listeners, or Splunk Observability plus AppDynamics OTel export from Linux,37 Docker, or.38- Preview and review the splunk appdynamics machine agent otel collector setup workflow before any live apply phase.39- Diagnose failed prerequisites, generated assets, configuration, or validation evidence.4041## Scope4243Follow the documented read-only or render-first path whenever it is available.44This skill does not imply permission to mutate live systems. Require explicit45apply flags, protected credentials, and operator review for state changes.4647## Examples4849Inspect the supported setup modes before selecting one:5051```bash52bash skills/splunk-appdynamics-machine-agent-otel-collector-setup/scripts/setup.sh --help53```5455Expected output: usage, supported modes, and required arguments are displayed56without changing the target environment.5758Inspect validation modes before running completion checks:5960```bash61bash skills/splunk-appdynamics-machine-agent-otel-collector-setup/scripts/validate.sh --help62```6364Expected output: offline, live, and completion options are displayed when the65skill supports them; help exits without mutation.6667## Troubleshooting6869| Issue | Cause | Resolution |70|---|---|---|71| Preflight fails | A required tool or access path is missing | Resolve it before rendering or applying |72| Rendered assets are incomplete | Required non-secret inputs are absent | Complete intake and render again |73| Apply is blocked | Review, credentials, or explicit acceptance is missing | Use the documented handoff |74| Validation is incomplete | Live evidence is unavailable | Record the gap and keep completion open |7576Owns the AppDynamics Machine Agent bundled OTel Collector configuration. The77default is loopback-only OTLP reception, traces to Splunk Observability Cloud78and AppDynamics OTel, metrics to Splunk Observability Cloud, and logs disabled79unless a log destination is explicitly declared.8081```bash82bash skills/splunk-appdynamics-machine-agent-otel-collector-setup/scripts/setup.sh --render83bash skills/splunk-appdynamics-machine-agent-otel-collector-setup/scripts/setup.sh --apply preflight --spec collector.yaml84bash skills/splunk-appdynamics-machine-agent-otel-collector-setup/scripts/setup.sh --apply collector --spec collector.yaml --accept-host-mutation85bash skills/splunk-appdynamics-machine-agent-otel-collector-setup/scripts/validate.sh --output-dir splunk-appdynamics-machine-agent-otel-collector-setup-rendered86```8788## What This Skill Covers8990- Machine Agent combined mode for Linux RPM, Linux ZIP, Docker, and Windows ZIP91 layouts.92- Bundled collector config rendering with OTLP gRPC on `127.0.0.1:4317` and93 OTLP HTTP on `127.0.0.1:4318` by default.94- Splunk Observability token-file and AppDynamics API key-file placeholders.95- A chmod-600 runtime environment file generated on the target from those96 secret files, plus a systemd drop-in for Linux service installs.97- Collector service/container restart, OTLP port checks, exporter health probes,98 backup manifests, and rollback.99100## Guardrails101102- `--accept-host-mutation` is required before writing files or restarting the103 collector.104- `--accept-remote-execution` is required for SSH targets.105- Direct token, access-token, and API key flags are refused; use file-backed106 fields in the spec.107- Referenced secret files must be non-empty and mode 600. Docker and Windows108 targets require an explicit `collector_credentials_ready_command`; a plain109 container/service restart cannot attach new credentials.110- Mutation is refused when the expected bundled collector path or service or111 container name cannot be confirmed from the spec and preflight.