| name | splunk-appdynamics-thousandeyes-integration-setup |
| description | Render, validate, and safely gate the AppDynamics-ThousandEyes integration across AppDynamics SaaS, On-Premises, and Virtual Appliance. Use when Codex needs to configure AppDynamics ThousandEyes token readiness, Dash Studio ThousandEyes widgets, Browser/Mobile RUM ThousandEyes network metrics, ThousandEyes native AppDynamics integration runbooks for test recommendations and alert notifications, ThousandEyes API-backed tests/labels/tags/alert rules/dashboards/templates, or a custom webhook fallback that posts ThousandEyes alerts into AppDynamics custom events. |
| compatibility | 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. |
| metadata | {"splunk_cloud_10_5":"not-applicable","compatibility_verified":"2026-07-02"} |
Splunk AppDynamics ThousandEyes Integration Setup
Own the AppDynamics-ThousandEyes integration end to end. The skill renders
reviewable artifacts first and keeps live product mutation behind explicit gates.
Safe Workflow
bash skills/splunk-appdynamics-thousandeyes-integration-setup/scripts/setup.sh --render
bash skills/splunk-appdynamics-thousandeyes-integration-setup/scripts/validate.sh
bash skills/splunk-appdynamics-thousandeyes-integration-setup/scripts/setup.sh \
--apply assets,webhook --accept-appd-te-mutation --spec path/to/appd-te.yaml
Use a local spec derived from template.example for customer work. Never put
ThousandEyes tokens, AppDynamics passwords, OAuth client secrets, or API keys in
the spec, shell history, rendered files, or chat. Use chmod-600 secret files.
What This Skill Covers
- AppDynamics
Administration > Integrations > ThousandEyes token enablement,
rotation, disablement, and Dash Studio query readiness.
- Dash Studio ThousandEyes widget constraints: Time Series, Metric Number, and
Gauge only; one TE query per widget; group-by only for Time Series; disabled
tests excluded; max time range 90 days; no time range comparison.
- Browser/Mobile RUM ThousandEyes network metrics. Treat this as SaaS-supported
unless an on-premises or Virtual Appliance Controller exposes the documented
UI.
- ThousandEyes native AppDynamics integration runbook. Test recommendations are
cSaaS-only; alert notifications need a reachable Controller URL and Create
Events permission.
- ThousandEyes API-backed assets through the existing
splunk-observability-thousandeyes-integration skill: tests, alert rules,
labels, tags, dashboards, and templates.
- ThousandEyes Integrations API custom webhook fallback: generic connector,
webhook operation, connector assignment, alert-rule notification fragments,
and AppDynamics custom event probe.
Boundaries
- Do not claim a public ThousandEyes API can create the native AppDynamics
integration unless Cisco documents that endpoint. Render the UI runbook and
accept an existing native integration ID for alert rules.
- Do not use ThousandEyes Webhook Operations APIs for ThousandEyes for
Government instances.
- Do not mutate ThousandEyes assets without
--accept-appd-te-mutation and the
downstream --i-accept-te-mutations gate.
--apply executes only explicit assets, webhook, or event sections
(all means all three). It requires a customer-specific spec, a numeric
account-group ID, non-example targets, and chmod-600 secret files.
Rendered Outputs
Primary outputs include:
appd-te-readiness.yamlthousandeyes-token-runbook.mddash-studio-query-runbook.mdeum-network-metrics-runbook.mdte-assets-spec.yamlhandoff-thousandeyes-assets.shte-native-appd-integration-runbook.mdte-appd-webhook-payloads/connector.jsonte-appd-webhook-payloads/operation.jsonte-alert-notification-fragments.jsonte-api-apply-plan.shappd-events-api-probe.shte-appd-admin-checklist.md
Read reference.md before applying or adapting the rendered API payloads.
