slug: logicmonitor
provider: LogicMonitor
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: 10
edges:
- tag: Roles
  spec_file: logicmonitor-roles-api-openapi.yml
  capability_id: BC-620.20
  capability_id_l1: BC-620
  capability_name: Identity & Access Management
  confidence: 0.85
  evidence: POST /setting/roles addRole 'add role'; schemas Role, Privilege, RolePaginationResponse
  reason: CRUD over roles and their privileges in the portal — this is access-control administration,
    i.e. identity and access management, not a monitoring function.
- tag: Users
  spec_file: logicmonitor-users-api-openapi.yml
  capability_id: BC-620.20
  capability_id_l1: BC-620
  capability_name: Identity & Access Management
  confidence: 0.85
  evidence: POST /setting/admins addAdmin 'add user'; schemas Admin, Role, Privilege, APIToken
  reason: Lifecycle of portal user accounts with roles, privileges and API tokens — administrative identity
    and access management, not HR employee records.
- tag: Cost Optimization Recommendations
  spec_file: logicmonitor-cost-optimization-recommendations-api-openapi.yml
  capability_id: BC-600.80
  capability_id_l1: BC-600
  capability_name: IT Financial Management
  confidence: 0.78
  evidence: GET /cost-optimization/recommendations  'Get recommendation list'; schema RestCloudRecommendationV3
  reason: Cloud cost-optimization recommendations and categories map to IT Financial Management, which
    explicitly covers IT spend and IT cost optimisation. Read-only recommendation retrieval supports the
    edge.
- tag: Data
  spec_file: logicmonitor-data-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.75
  evidence: GET /device/devices/{deviceId}/devicedatasources/{hdsId}/instances/{id}/data  'get device
    instance data'; 'get website graph data'
  reason: Operations retrieve collected metric/graph/checkpoint time-series and device config data from
    monitored resources — the core retrieval of monitoring telemetry, i.e. observability management.
- tag: Websites
  spec_file: logicmonitor-websites-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.75
  evidence: GET /website/websites/{id}/alerts 'get alerts for a website'; GET /website/smcheckpoints 'get
    website checkpoint list'; schemas SiteMonitorCheckpoint, WebCheckStep, GraphPlot
  reason: Configures synthetic website checks from monitoring checkpoints and retrieves their alerts and
    performance graphs — synthetic monitoring, explicitly within observability management; not digital
    marketing or web content.
- tag: Devices
  spec_file: logicmonitor-devices-api-openapi.yml
  capability_id: BC-600.40
  capability_id_l1: BC-600
  capability_name: IT Operations Management
  confidence: 0.72
  evidence: POST /device/devices  addDevice  add a new device; GET /device/devices/{id}/alerts  get alerts;
    'get a list of alert settings for a device'; 'schedule active discovery for a device'
  reason: CRUD over monitored devices plus their alerts, alert settings, netflow and discovery — the core
    of infrastructure monitoring operations. Cross-industry IT Operations Management (monitoring, automation)
    is the accurate reading for this observability devtool; no industry-specific business capability applies.
- tag: Alerts
  spec_file: logicmonitor-alerts-api-openapi.yml
  capability_id: BC-600.40
  capability_id_l1: BC-600
  capability_name: IT Operations Management
  confidence: 0.7
  evidence: POST /alert/alerts/{id}/ack "ack alert by id"; POST /alert/alerts/{id}/escalate "Escalate
    alert by ID"
  reason: 'Alerts here are infrastructure monitoring alerts that operators acknowledge, annotate and escalate
    — IT operations monitoring. Homograph check: nothing suggests business or compliance alerting.'
- tag: LogPartitions
  spec_file: logicmonitor-logpartitions-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.7
  evidence: POST /log/partitions  createLogPartition  Create a new log partition; GET /log/partitions/retentions  Retrieve
    the list of log retentions
  reason: Management of log storage partitions and retention within an observability platform — directly
    the 'logs' element of Observability Management.
- tag: LogQueryGroups
  spec_file: logicmonitor-logquerygroups-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.7
  evidence: GET /log/logquerygroups/{id}/logqueries  getLogQueriesByGroupId  Get log queries by group
    ID
  reason: Saved log query and query-group management for log analysis — log observability tooling, not
    business querying.
- tag: Thresholds
  spec_file: logicmonitor-thresholds-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.7
  evidence: GET /device/devices/{deviceId}/devicedatasources/{hdsId}/instances/{instanceId}/alertsettings
    'get a list of alert settings for a device datasource instance'; schema DeviceGroupAlertThresholdInfo
  reason: Configuration of alert thresholds on monitored device datasources — monitoring instrumentation
    configuration, i.e. observability management; not business alerting of any kind.