slug: appdynamics
provider: AppDynamics
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Software & Technology
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 8
edges:
- tag: Custom Metrics
  spec_file: appdynamics-custom-metrics-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.9
  evidence: POST /api/v1/metrics publishCustomMetrics "Publish custom metrics"; "uploading custom metrics
    to the AppDynamics Controller"
  reason: Direct metric ingestion into a monitoring platform — plainly logs/metrics observability of the
    running service.
- tag: Database Collectors
  spec_file: appdynamics-database-collectors-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.85
  evidence: '"managing Database Monitoring database Collectors ... monitor the performance and availability
    of database instances"; createDatabaseCollector'
  reason: Provisioning of monitoring collectors that observe database performance and availability — infrastructure
    observability, not data management.
- tag: Metrics
  spec_file: appdynamics-metrics-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.85
  evidence: GET /rest/applications/{applicationId}/metric-data getMetricData — "retrieve metric data and
    transaction snapshots from monitored applications"; schemas MetricData, MetricValue
  reason: Operations retrieve performance metric hierarchies and time-series data from monitored applications
    — metrics-based observability of running services, not a business-domain metric.
- tag: Applications
  spec_file: appdynamics-applications-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.8
  evidence: GET /rest/applications listApplications "List all business applications"; "query application
    metrics, retrieve transaction snapshots ... access topology information for monitored applications"
  reason: The 'Applications' here are monitored application entities in an APM controller, i.e. the inventory
    of monitored services for production observability — not a business application portfolio.
- tag: Backends
  spec_file: appdynamics-backends-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.8
  evidence: GET /rest/applications/{applicationId}/backends listBackends "List backends for an application";
    schema Backend
  reason: Lists discovered backend dependencies (databases, queues) of a monitored application — topology/observability
    data about the running service.
- tag: Business Transactions
  spec_file: appdynamics-business-transactions-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.8
  evidence: GET /rest/applications/{applicationId}/business-transactions listBusinessTransactions; "manage
    business transactions, and access topology information for monitored applications"
  reason: 'Homograph: ''Business Transactions'' is an APM construct (traced request flows), not financial
    transactions. Serves production observability of the monitored application.'
- tag: Snapshots
  spec_file: appdynamics-snapshots-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.8
  evidence: GET /rest/applications/{applicationId}/request-snapshots listRequestSnapshots; "retrieve request
    snapshots for detailed transaction analysis"
  reason: Retrieval of distributed transaction snapshots (trace-level detail) for diagnosing production
    behaviour — observability of the running service.
- tag: Health Rules
  spec_file: appdynamics-health-rules-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.7
  evidence: POST /alerting/rest/v1/applications/{applicationId}/health-rules createHealthRule "Create
    a health rule"; schemas HealthRule, CloudHealthRule
  reason: 'Defines monitoring thresholds/conditions that trigger alerts on monitored applications — observability
    configuration. Note: ''Health'' here is service health, not customer or occupational health; some
    overlap with reliability-objective management keeps confidence moderate.'