slug: betterstack
provider: Better Stack
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: 3
edges:
- tag: Incidents
  spec_file: betterstack-incidents-api-openapi.yml
  capability_id: BC-4220.30
  capability_id_l1: BC-4220
  capability_name: Incident Response Management
  confidence: 0.8
  evidence: '"acknowledgeIncident  Acknowledge incident", "escalateIncident  Escalate incident", "resolveIncident  Resolve
    incident"; vendor: "incident management with on-call paging and escalation policies"'
  reason: Acknowledge/resolve/reopen/escalate lifecycle over production incidents with on-call paging
    is incident response management. Slight residual ambiguity with generic ITSM incident management (BC-600.30),
    but the vendor framing is SRE/on-call for a running service.
- tag: Monitors
  spec_file: betterstack-monitors-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.8
  evidence: '"createMonitor  Create monitor", "getMonitorResponseTimes  Monitor response times", "getMonitorAvailability  Monitor
    availability"'
  reason: Lifecycle management of uptime/synthetic monitors plus response-time and availability telemetry
    — synthetic monitoring of the running service, which is observability management.
- tag: Heartbeats
  spec_file: betterstack-heartbeats-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.75
  evidence: '"createHeartbeat  Create heartbeat", "getHeartbeatAvailability  Heartbeat availability";
    vendor: "heartbeat monitoring for scheduled jobs"'
  reason: CRUD plus availability reporting over heartbeat checks that detect whether scheduled jobs are
    running — production monitoring that makes the running service understandable, i.e. observability.
    Some ambiguity between Observability Management and Service Reliability Engineering (availability
    metrics), hence 0.75.