LogicMonitor - ResolveAI

Connect from ResolveAI to LogicMonitor to give the agent read-only access to your alerts, devices and datasource data for investigations. ResolveAI calls the LogicMonitor REST API v3.

Prerequisite: in LogicMonitor, permission to add users and roles, and Allow Creation of API Tokens.

In LogicMonitor

1. Create a read-only API user

Open Settings → User Access → Users and Roles. Add a role with View access to Resources and Alerts (the built-in readonly role also works), then add an API-only user with that role.

2. Create an API token

Open Settings → User Access → API Tokens and add a token for that user. ResolveAI accepts either kind:

LMv1: copy the Access ID and Access Key. The key is shown only once.
Bearer: copy the generated token.

LogicMonitor rejects API calls from tokens of users with the built-in Administrator role. Use the read-only user from step 1.

In ResolveAI

Resolve UI
Resolve Satellite

3. Add a LogicMonitor connection

Open Integrations, click LogicMonitor, then Add Connection. Give it a name (ex. LogicMonitor Prod) and list its environments.

4. Add the portal and the token

Company: the <company> in https://<company>.logicmonitor.com
Auth mode: lmv1 or bearer, matching the token from step 2
Access ID and Access key, or API token

5. Behind an API gateway (optional)

Base URL: the gateway URL that replaces https://<company>.logicmonitor.com/santaba/rest
Request headers overrides: headers the gateway requires, as JSON (ex. {"X-Api-Key": "<key>"})
Auth mode gateway: when the gateway authenticates to LogicMonitor itself and ResolveAI should send only those headers

6. Save and verify

Click Save, then Check Health.

The Resolve Satellite connects from inside your network, so the token never leaves your environment.

Prerequisites: the Resolve Satellite is installed. LMv1 tokens need Satellite v1.1.59 or later; Bearer tokens work on any version.

3. Create a Kubernetes secret

logicmonitor-credentials.yml

apiVersion: v1
kind: Secret
type: Opaque
metadata:
  name: logicmonitor-credentials
stringData:
  accessId: "<Access ID>"
  accessKey: "<Access Key>"
  # For a Bearer token instead:
  # apiToken: "<Bearer token>"
  # Headers an API gateway requires:
  # requestHeadersOverrides: |
  #   X-Api-Key: "<key>"

kubectl apply -f logicmonitor-credentials.yml

4. Update your values file

resolve-values.yaml

integrations:
  logicmonitor-main:
    type: logicMonitor
    create: true
    secretName: logicmonitor-credentials
    connection:
      company: "<portal name>"
      authMode: lmv1 # lmv1, bearer, or gateway
      # baseUrl: "https://gateway.example.com/logicmonitor/santaba/rest"

5. Apply and verify

helm upgrade --install resolve-satellite \
  oci://registry-1.docker.io/resolveaihq/satellite-chart \
  --values resolve-values.yaml

Verify with Check Health on the LogicMonitor integration page.

​In LogicMonitor

​1. Create a read-only API user

​2. Create an API token

​In ResolveAI

​3. Add a LogicMonitor connection

​4. Add the portal and the token

​5. Behind an API gateway (optional)

​6. Save and verify

​3. Create a Kubernetes secret

​4. Update your values file

​5. Apply and verify

In LogicMonitor

1. Create a read-only API user

2. Create an API token

In ResolveAI

3. Add a LogicMonitor connection

4. Add the portal and the token

5. Behind an API gateway (optional)

6. Save and verify

3. Create a Kubernetes secret

4. Update your values file

5. Apply and verify