slug: airbrake
provider: Airbrake
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: 5
edges:
- tag: Notices
  spec_file: airbrake-notices-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.75
  evidence: POST /api/v3/projects/{project_id}/notices  Create notice (error occurrence)
  reason: Notices are individual error occurrences ingested from notifier libraries and queried per group
    — telemetry capture that makes the running service observable in production.
- tag: iOS Crash Reports
  spec_file: airbrake-ios-crash-reports-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.72
  evidence: POST /api/v3/projects/{project_id}/ios-reports  "Create iOS crash report"
  reason: Ingesting crash reports from a running mobile app into an error-monitoring platform is production
    telemetry capture that makes the running service understandable — observability management, not business
    incident handling.
- tag: Deploys
  spec_file: airbrake-deploys-api-openapi.yml
  capability_id: BC-4210
  capability_id_l1: BC-4210
  capability_name: Software Release & Deployment Management
  confidence: 0.7
  evidence: POST /api/v4/projects/{project_id}/deploys  Create deploy
  reason: Operations record and retrieve deployment events for a project — deploy tracking as described
    in the vendor blurb ('provides deploy tracking'). This sits in release and deployment management,
    but Airbrake only registers deploys rather than orchestrating or versioning them, so no L2 is asserted.
- tag: Groups
  spec_file: airbrake-groups-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.7
  evidence: Airbrake is an error monitoring and APM platform exposing endpoints for ... groups (errors);
    PUT /api/v4/projects/{project_id}/groups/{group_id}/muted  Mute group
  reason: Groups are aggregated production error signals that can be listed, muted and statistically summarised
    — production monitoring of the running service. A defect-management (quality engineering) reading
    is possible, which keeps confidence below 0.8.
- tag: Performance
  spec_file: airbrake-performance-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.7
  evidence: PUT /api/v5/projects/{project_id}/routes-stats  Submit route performance stats; PUT /api/v5/projects/{project_id}/queries-stats  Submit
    database query stats
  reason: Operations ingest APM metrics (route timings, DB query and queue statistics) for a monitored
    service, which is metrics-based observability. It is not capacity forecasting or performance testing,
    so the observability sub-capability is chosen, with some residual ambiguity.