LogicMonitor
The LogicMonitor action of an automation rule sends an alert to your LogicMonitor portal when the rule fires, so your operations center sees ANTS Platform alerts next to the rest of its monitoring. When the problem recovers, or someone resolves the alert in ANTS Platform, the same alert is cleared.
There is no LogicMonitor page under Integrations: the connection is set in each action.
Set up
Create a Webhook LogSource in LogicMonitor
In your LogicMonitor portal, add a Webhook LogSource with a source name (for example ants) and bearer token authentication. Copy the token.
Map the resource from the resource field, keep alertId, status and severity as fields, and add a LogAlert condition on status active, with the severity from severity, and a clear condition on status clear, matched by alertId. See What ANTS Platform sends.
Add the action to a rule
In Project Settings → Automations, open or create a rule, select Add action, then LogicMonitor, and fill in the settings below.
Save and test
Save the rule, then select Send test on the action to send the event's sample to your portal.
Action settings
| Setting | Meaning |
|---|---|
| Portal | The account name in your portal address: example for example.logicmonitor.com. Letters, numbers and -. |
| Source name | The source name of the Webhook LogSource that receives ANTS alerts. Letters, numbers, - and _. Default ants. |
| Bearer token | The LogSource's token. Stored encrypted and never shown again. Leave it empty when editing to keep the saved token. Changing Portal or Source name needs the token again. |
| Severity | From event severity maps Critical to critical, High to error, and Medium, Low and Info to warn. Or pick Critical, Error or Warning for every alert. |
| Clear when resolved | Sends a clear for the same alert when the source event recovers or the alert is resolved. On by default. |
| Title, Message | The alert text. Use {{variable}} message templates, or leave them empty for the event's default message. |
The severity used for From event severity is the rule's severity when the rule sets one.
Adding a LogicMonitor action, or changing its portal, source name or token, asks for step-up verification when it is turned on.
What ANTS Platform sends
ANTS Platform posts JSON to https://<portal>.logicmonitor.com/rest/api/v1/webhook/ingest/<source name> with Authorization: Bearer <token>:
| Field | Meaning |
|---|---|
alertId | The same for the alert and its clear, so LogicMonitor can match them. One incident, such as one silent agent or one failing export, keeps one alertId. |
status | active for an alert, clear when it is cleared. |
severity | critical, error or warn. |
title, message | The action's title and message. |
resource | What the event is about: the agent, key, deployment or other subject. |
eventType | The event key. |
project, rule | The project ID and the rule name. |
link | Opens the subject in ANTS Platform. |
occurredAt | When the event happened. |
A clear is sent when:
- the event's recovery event arrives for the same incident, for example Agent error rate back to normal;
- someone with automations edit access resolves the alert on the Alerts page, or the alert expires.
LogicMonitor has no acknowledge, so Acknowledge in ANTS Platform sends nothing.
Delivery follows the automation rules: a 2xx answer within 10 seconds is a success, network errors, timeouts and 5xx answers are retried, and repeated failures turn the action off. See Delivery and failures.
Without a Webhook LogSource
If your portal cannot use a Webhook LogSource, use a Webhook action instead:
- Add a Webhook action with the URL of your LogicMonitor ingest endpoint or your own relay, and an
Authorizationheader marked Secret. - ANTS Platform sends the event envelope with
type,severity,subject,data,linksandcorrelationId. MapcorrelationIdto the alert ID andseverityto the LogicMonitor level in the relay or LogSource. - Add a second rule on the recovery event, for example Agent resumed sending traces, with the same Webhook action to send the clear.