slug: overops
provider: Overops
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: 4
edges:
- tag: View Metrics
  spec_file: overops-view-metrics-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.8
  evidence: '''Fetch event metrics split by view'', ''Fetch event metrics split by entry point'', schemas
    EventStats, EntryPointStats'
  reason: Time-series metrics over production application events from a reliability-monitoring agent are
    observability data, making the running service understandable in production.
- tag: Events
  spec_file: overops-events-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.75
  evidence: GET /services/{env_id}/events/{event_id}/snapshot — "Fetch event snapshot"; schemas Event,
    CodeLocation, EventStats
  reason: Retrieval of captured error events, code-location snapshots and statistics from instrumented
    production applications is production observability data, not business event processing.
- tag: System Metrics
  spec_file: overops-system-metrics-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.75
  evidence: GET /services/{env_id}/metrics/system/{metric_name}/graph — "Fetch metric graph/data"; schema
    SystemMetrics
  reason: Retrieval of system metric metadata and time-series graphs for the monitored runtime is classic
    metrics-based observability of the running service.
- tag: Views
  spec_file: overops-views-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.75
  evidence: '''Fetch events details'', ''Fetch stats for all events in the specified view'', ''Fetch entry
    points details'', schemas Event, CodeLocation, Filter'
  reason: 'Views are saved filters over captured production error/event telemetry with stats and metrics
    graphs — observability of the running service. Not product usage analytics: the events are code-level
    errors with CodeLocation, not product usage events.'