Splunk AppDynamics Controller Admin 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 Controller administration, API clients, OAuth, RBAC, SAML, LDAP, user/group/role
management, account permissions, licensing, license rules, sensitive data controls, SQL/log masking, environment
variable.
- Preview and review the splunk appdynamics controller admin 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-controller-admin-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-controller-admin-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 |
Controller administration renders documented API/UI runbooks and read-only
probes. This wrapper does not mutate users, groups, roles, API clients, license
rules, identity providers, or privacy controls; --apply fails closed. The
license-usage reporter is the concrete read-only action path.
bash skills/splunk-appdynamics-controller-admin-setup/scripts/setup.sh --render
bash skills/splunk-appdynamics-controller-admin-setup/scripts/validate.sh
bash skills/splunk-appdynamics-controller-admin-setup/scripts/license_usage_report.sh \
--controller-url "$APPD_CONTROLLER_URL" \
--account-name "$APPD_ACCOUNT_NAME" \
--account-id "$APPD_ACCOUNT_ID" \
--api-client-name "$APPD_API_CLIENT_NAME" \
--client-secret-file "$APPD_OAUTH_CLIENT_SECRET_FILE" \
--deep \
--output-dir ./appd-license-report
Secrets such as OAuth client secrets and passwords must be referenced by
chmod-600 files.
The license usage reporter is read-only. It polls documented Controller License
API endpoints and writes a customer-facing Markdown consumption report plus
complete JSON and CSV exports for timestamp-level analysis.
Live validation notes:
APPD_ACCOUNT_ID is the numeric License API account ID, not the account name,
tenant key, or GUID-like acctId/tntId claim in an OAuth token.
APPD_OAUTH_CLIENT_SECRET_FILE and APPD_OAUTH_TOKEN_FILE must be paths to
chmod-600 local files, not inline secret values.
- API Client role assignments are separate from user role assignments. If
license endpoints return 403 for
ACCOUNT_LICENSE, LICENSE_USAGE, or
LICENSE_RULE, assign and save a role on Administration > API Clients.
- OAuth JWT role or account-permission claim counts are diagnostic only; some
SaaS tokens omit effective API Client permissions even when License API
readbacks succeed.
- AppDynamics SaaS controllers can require the vendor JSON
Accept media type;
the reporter sends that header for OAuth and License API requests.
- Deep mode falls back to application inventory when grouped application usage
returns an empty
items object, and host usage degrades cleanly when no host
IDs are available.
1---2name: splunk-appdynamics-controller-admin-setup3description: "Use when the user asks for AppDynamics Controller administration, API clients, OAuth, RBAC, SAML, LDAP,4 user/group/role management, account permissions, licensing, license rules, sensitive data controls,5 SQL/log masking, environment variable filtering, or privacy validation. Render and validate Splunk6 AppDynamics Controller administration workflows, including SaaS and on-prem account checks, API clients,7 OAuth token-file flow, users, groups, roles, SAML, LDAP, account permissions, licensing, license rules,8 sensitive data collection controls, privacy settings, audit readiness, and data collection dashboards."9compatibility: "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."10metadata:11 source: https://skillmd.com/skills/chambear2809/splunk-appdynamics-controller-admin-setup12 splunk_cloud_10_5: "not-applicable"13 compatibility_verified: "2026-08-20"14---1516# Splunk AppDynamics Controller Admin Setup1718## Prerequisites1920| Tool or access | Purpose | Verify |21|---|---|---|22| Bash and Python 3 | Run bundled setup and validation helpers | `bash --version && python3 --version` |23| Required product/platform access | Inspect or configure the selected target | Complete the documented preflight |24| Credential files for live modes | Keep secrets out of chat | Verify paths only |2526## Workflow Overview2728```text29┌───────────┐ ┌───────────────┐ ┌───────────────┐ ┌─────────────────┐30│ Preflight │ → │ Render/review │ → │ Apply/handoff │ → │ Validate evidence │31└───────────┘ └───────────────┘ └───────────────┘ └─────────────────┘32```3334## When to Activate3536- The user asks for AppDynamics Controller administration, API clients, OAuth, RBAC, SAML, LDAP, user/group/role37 management, account permissions, licensing, license rules, sensitive data controls, SQL/log masking, environment38 variable.39- Preview and review the splunk appdynamics controller admin setup workflow before any live apply phase.40- Diagnose failed prerequisites, generated assets, configuration, or validation evidence.4142## Scope4344Follow the documented read-only or render-first path whenever it is available.45This skill does not imply permission to mutate live systems. Require explicit46apply flags, protected credentials, and operator review for state changes.4748## Examples4950Inspect the supported setup modes before selecting one:5152```bash53bash skills/splunk-appdynamics-controller-admin-setup/scripts/setup.sh --help54```5556Expected output: usage, supported modes, and required arguments are displayed57without changing the target environment.5859Inspect validation modes before running completion checks:6061```bash62bash skills/splunk-appdynamics-controller-admin-setup/scripts/validate.sh --help63```6465Expected output: offline, live, and completion options are displayed when the66skill supports them; help exits without mutation.6768## Troubleshooting6970| Issue | Cause | Resolution |71|---|---|---|72| Preflight fails | A required tool or access path is missing | Resolve it before rendering or applying |73| Rendered assets are incomplete | Required non-secret inputs are absent | Complete intake and render again |74| Apply is blocked | Review, credentials, or explicit acceptance is missing | Use the documented handoff |75| Validation is incomplete | Live evidence is unavailable | Record the gap and keep completion open |7677Controller administration renders documented API/UI runbooks and read-only78probes. This wrapper does not mutate users, groups, roles, API clients, license79rules, identity providers, or privacy controls; `--apply` fails closed. The80license-usage reporter is the concrete read-only action path.8182```bash83bash skills/splunk-appdynamics-controller-admin-setup/scripts/setup.sh --render84bash skills/splunk-appdynamics-controller-admin-setup/scripts/validate.sh85bash skills/splunk-appdynamics-controller-admin-setup/scripts/license_usage_report.sh \86 --controller-url "$APPD_CONTROLLER_URL" \87 --account-name "$APPD_ACCOUNT_NAME" \88 --account-id "$APPD_ACCOUNT_ID" \89 --api-client-name "$APPD_API_CLIENT_NAME" \90 --client-secret-file "$APPD_OAUTH_CLIENT_SECRET_FILE" \91 --deep \92 --output-dir ./appd-license-report93```9495Secrets such as OAuth client secrets and passwords must be referenced by96chmod-600 files.9798The license usage reporter is read-only. It polls documented Controller License99API endpoints and writes a customer-facing Markdown consumption report plus100complete JSON and CSV exports for timestamp-level analysis.101102Live validation notes:103104- `APPD_ACCOUNT_ID` is the numeric License API account ID, not the account name,105 tenant key, or GUID-like `acctId`/`tntId` claim in an OAuth token.106- `APPD_OAUTH_CLIENT_SECRET_FILE` and `APPD_OAUTH_TOKEN_FILE` must be paths to107 chmod-600 local files, not inline secret values.108- API Client role assignments are separate from user role assignments. If109 license endpoints return 403 for `ACCOUNT_LICENSE`, `LICENSE_USAGE`, or110 `LICENSE_RULE`, assign and save a role on Administration > API Clients.111- OAuth JWT role or account-permission claim counts are diagnostic only; some112 SaaS tokens omit effective API Client permissions even when License API113 readbacks succeed.114- AppDynamics SaaS controllers can require the vendor JSON `Accept` media type;115 the reporter sends that header for OAuth and License API requests.116- Deep mode falls back to application inventory when grouped application usage117 returns an empty `items` object, and host usage degrades cleanly when no host118 IDs are available.