> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Connecting LogicMonitor to Neo

> Create a LogicMonitor Bearer token for an API-only user and save it in Neo with your portal name

You connect LogicMonitor once at the MSP level. One Bearer token covers every client in your portal.

## 1. Create the user and its role

A LogicMonitor Bearer token belongs to one user and has that user's role. Create an API-only user for Neo, so its changes show apart in LogicMonitor's audit log, and give its role what your agents do:

| Agents that | Role permission |
| - | - |
| Read alerts, resources and their data | **View** on Resources |
| Acknowledge alerts and schedule downtime | **Manage** on Resources |
| Change thresholds, alert rules or escalation chains | **Manage** on the matching Settings areas |
| Restart collectors | **Manage** on Settings > Collectors |

You can limit the role to the resource groups of the clients Neo should reach.

## 2. Create the Bearer token

**1. Open the user**

In LogicMonitor, open **Settings > Users and Roles**, then the user Neo acts as.

**2. Add a Bearer token**

Under **API Tokens**, add a token of type **Bearer** and copy it. LogicMonitor shows the whole token once.

> [!WARNING]
>
> If the user is suspended or the token is deleted, Neo loses access until you save a new token here.

## 3. Add the token in Neo

**1. Open Integrations**

In the Neo Dashboard, open **Integrations** and find the LogicMonitor card, under Networking.

**2. Save the portal and the token**

Enter your portal, the address you sign in at, such as `https://acme.logicmonitor.com` (or `.lmgov.us` for GovCloud), or the account name alone (`acme`). Paste the Bearer token and click **Save settings**. Neo reads one resource group with the token before saving, so a wrong portal or token, or a role that cannot see resources, is rejected straight away.

## 4. Turn LogicMonitor on per agent

Open the agent, go to its **Tools & Settings** tab, click **Networking**, and expand the **LogicMonitor** block. Pick one of its **Presets**, or set each area yourself:

| Area | Access levels you can pick | Notes |
| - | - | - |
| **Alerts** | Disabled, Read Only, Read / Write | Alerts, acknowledging them, notes and escalating. |
| **Scheduled Downtime and Ops Notes** | Disabled, Read Only, Read / Write | Downtime on resources, groups, DataSources, websites and collectors, and ops notes. |
| **Alert Settings, Rules and Escalation** | Disabled, Read Only, Read / Write | Thresholds, turning a DataSource's alerting off for a group, alert rules, escalation chains, recipient groups. |
| **Resources and Resource Groups** | Disabled, Read Only, Read / Write | Resources, groups, properties, DataSources, instances and their data. |
| **Websites** | Disabled, Read Only, Read / Write | Website and ping checks and their data. |
| **Collectors and NetScans** | Disabled, Read Only, Read / Write | Collectors, their logs and restarts, NetScans. |
| **LogicModules** | Disabled, Read Only, Read / Write | DataSources and the other modules. A change reaches every client the module applies to. |
| **Diagnostics, Remediation and Debug** | Disabled, Read Only, Read / Write | Collector debug commands, diagnostics and remediation, and their results. |
| **Dashboards and Reports** | Disabled, Read Only, Read / Write | Dashboards, widgets and reports. |
| **Logs** | Disabled, Read Only, Read / Write | LM Logs partitions, pipelines and saved queries. |
| **Users, Roles and Audit Logs** | Disabled, Read Only, Read / Write | Users and their API tokens, roles, access groups and the audit log. |
| **Usage and Account** | Disabled, Read Only | Resource and metric counts, contract and API usage. |

| Preset | 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 most writes | LogicModules, diagnostics and debug commands, users and roles |
| **Full Automation** | Every read and write | Only the writes that always ask |

A few writes always ask a technician, whatever the preset: storing a credential, changing 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. A `PUT` that would replace a whole record is refused: agents update with `PATCH`. Neo refuses downtime on the root group, and turning alerting off there, because the root group holds every client.

## Use it on alert tickets

Most MSPs send LogicMonitor alerts to their PSA through an integration or an on-call tool such as Opsgenie. The ticket titles name the severity, the resource and the datapoint, for example `[LogicMonitor] [error] - web01 CPU CPUBusyPercent > 90 95`. An agent that triggers on those tickets finds the alert, reads the data and the collector, notes what it found, and acknowledges the alert when your instructions say to.

See [LogicMonitor API](https://docs.neoagent.io/agents/tools/networking/logicmonitor-api.md) for what the agent can read and change.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.