LogicMonitor API

The common use is a ticket a LogicMonitor alert opened in your PSA: the agent finds the alert by the resource and datapoint in the ticket, reads the value against the threshold, whether it cleared, the resource’s recent data and its collector, and notes what it found. It can acknowledge the alert with the ticket number. Other agents schedule downtime for a maintenance window, or raise a threshold on a noisy resource.

Automatically enabled when you configure LogicMonitor permissions in your agent workflow.

What It Does

Read alerts on resources, websites and collectors, with their value, threshold, start and end; acknowledge them, add notes and escalate
Schedule, change and end downtime (SDT), and read downtime history and ops notes
Read resources and resource groups, their properties, DataSources, instances, metric data, graphs and NetFlow; add, change and delete them, and turn alerting off
Read and change thresholds per instance, resource and group, cluster alerts, alert rules, escalation chains and recipient groups
Read and change website checks, collectors, NetScans and LogicModules, and import LogicModules
Run collector debug commands, diagnostics and remediation, and read their results
Read and change dashboards, reports, LM Logs pipelines and queries, users, roles and API tokens, and read the audit log and usage

Permission Groups

Group	Covers
Alerts	Alerts, acknowledging, notes and escalating
Scheduled Downtime and Ops Notes	Downtime on any target, its history, and ops notes
Alert Settings, Rules and Escalation	Thresholds, cluster alerts, turning a DataSource’s alerting off for a group, alert rules, escalation chains, recipient groups, integration delivery logs
Resources and Resource Groups	Resources, groups, properties, DataSources, instances, metric data, graphs, NetFlow, cloud account checks
Websites	Website checks, groups, checkpoints and their data
Collectors and NetScans	Collectors and collector groups, their logs, events, restarts and status checks; NetScans; DNS mappings
LogicModules	DataSources, ConfigSources, EventSources, PropertySources, TopologySources, LogSources, AppliesTo functions, OIDs, JobMonitors
Diagnostics, Remediation and Debug	Collector debug commands, DiagnosticSources, RemediationSources, their results, and the action rules and chains that run them
Dashboards and Reports	Dashboards, widgets, reports and running a report
Logs	LM Logs partitions, pipelines, log alert processors, saved and tracked queries
Users, Roles and Audit Logs	Users and their API tokens, roles, access groups, the audit log
Usage and Account	Resource and metric counts, contract, API usage, cost recommendations (read only)

Access Profiles

Profile	What runs on its own	What asks a technician
Read Only	Every read	No write is allowed
Helpdesk	Reads, acknowledging and noting alerts	Scheduled downtime. Everything else stays read only
IT Admin	Every read and every write but the next column	LogicModules, which reach every client; diagnostics, remediation and collector debug commands, which run code at the client; and users and roles, which grant access
Full Automation	Every read and write	Only the writes that always ask (below)

Safety Controls

Control	Behavior
Always ask	Storing a credential (a password, a token, or a credential property such as `ssh.pass` or `snmp.community`), a change to a list whose items hold a password (a website check’s steps, a user’s API tokens, a NetScan’s credentials), deleting a resource group, and downtime that repeats always need a technician’s approval, whatever the profile
Whole-record updates	A `PUT` that would replace a whole record is refused, because it would erase the credentials Neo hides; agents update with `PATCH`
Every client at once	Downtime on the root resource group or root website group, and turning alerting or monitoring off there, are refused: the root group holds every client
Property updates	An update that carries properties must set `opType` to `replace` or `add`, so LogicMonitor keeps the properties the update leaves out
Hidden credentials	Passwords, tokens, keys and credential properties read `[hidden by Neo]` in every answer. Neo refuses a write that sends that value, or LogicMonitor’s own `********`, back, and a filter or sort that names a credential or compares a property’s value. The output of a debug command, a diagnostic or a remediation is free text the script wrote, and Neo does not redact it
Not sent	The collector installer and its download token, creating an API token, and a device’s collected configuration files, which hold the device’s own passwords

Getting started

Core

Triggered & Scheduled Agents

Chat Agents

Integrations

Product

Workflows

Customizing Neo

What It Does

Permission Groups

Access Profiles

Safety Controls

​What It Does

​Permission Groups

​Access Profiles

​Safety Controls

What It Does

Permission Groups

Access Profiles

Safety Controls