slug: mezmo
provider: Mezmo
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: Logs
  spec_file: mezmo-logs-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.8
  evidence: POST /logs/ingest ingestLogs "Ingest log lines into the Mezmo log analysis platform"
  reason: Log ingestion is the core of observability telemetry collection; maps to Observability Management.
- tag: Export
  spec_file: mezmo-export-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.75
  evidence: '"Query and export logs from the Mezmo log analysis platform"; GET /v2/export exportLogsV2'
  reason: Log query/export on an observability platform realises Observability Management (logs/metrics/traces
    made understandable), not any business-domain capability.
- tag: PresetAlerts
  spec_file: mezmo-presetalerts-api-openapi.yml
  capability_id: BC-4220
  capability_id_l1: BC-4220
  capability_name: SaaS Platform Operations Management
  confidence: 0.75
  evidence: '"Preset alerts encapsulate presence or absence triggers, frequency, count thresholds, and
    notification channels (PagerDuty, Slack, webhook, email)"'
  reason: Monitoring alert rules with PagerDuty/Slack routing sit in SaaS platform operations (observability/incident
    detection). Not financial-crime or business alerting; L2 left null as evidence straddles observability
    and incident response.
- tag: Destinations
  spec_file: mezmo-destinations-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.7
  evidence: POST /pipelines/{pipelineId}/destinations createDestination Create Destination; "Manage pipelines,
    sources, processors, destinations"
  reason: CRUD over the destinations to which a telemetry pipeline routes logs and metrics. This configures
    where observability data lands, squarely within Observability Management (logs, metrics, traces).
    Not a business 'destination' concept.
- tag: Pipelines
  spec_file: mezmo-pipelines-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.7
  evidence: '"Programmatic CRUD over Mezmo Telemetry Pipelines. Manage pipelines, sources, processors,
    destinations"; GET /pipelines/{pipelineId}/health'
  reason: Telemetry pipeline configuration is the plumbing that delivers logs/metrics/traces, i.e. observability
    tooling management, not a business-domain capability.