When configuring AppNeta Intelligent Alarms to send notifications via a webhook (e.g., to DX Operational Intelligence or other third-party integrations), users
may observe that alarms are successfully raised, but it is unclear if or how clearing events are generated. This can lead to alarms remaining in an open state
in the receiving system.
AppNeta Performance Manager
The AppNeta v4 API alarm connector is designed to notify on two distinct lifecycle states: RAISED and CLEARED.
There is no separate configuration toggle required to enable clearing events; the connector automatically sends a new webhook payload when the conditions of an active alarm are no longer met. To ensure these events are processed correctly, the receiving system must be configured to parse the state field within the JSON payload.
Below is an example of the JSON payload sent by the v4 connector when an alarm clears. Note the state field is set to CLEARED and a clearedTime timestamp is provided.
{
"orgId": "####",
"connectorName": "####",
"connectorType": "WEBHOOK",
"connectorId": "####",
"alarmId": "####",
"alarmType": "QUALITY_OF_SERVICE",
"state": "CLEARED",
"alarmSeverity": "MAJOR",
"rule": "Multiple Web errors (Default)",
"ruleId": "####",
"description": "Web Test Error Equals Any for 2 out of 3 samples",
"firstViolationTime": "2026-04-27T17:30:00.675+0000",
"raisedTime": "2026-04-27T17:35:02.512+0000",
"clearedTime": "2026-04-27T17:50:03.532+0000",
"providerLink": "https://####.pm.appneta.com/pvc/ngp/alarm/####?orgId=####",
"itemId": "####",
"itemName": "####",
"itemType": "WEB_PATH",
"target": "https://####",
"monitoringPointId": "####",
"monitoringPointName": "####",
"tags": [
{
"category": "APP",
"value": "NetOps"
}
],
"noisyConditions": []
}
CLEARED value to transition the alarm status to CLOSED or RESOLVED.AppNeta Alarm Map to O2
| State AppNeta Name | AppNeta Value | O2 Name | O2 Value |
| state | RAISED | status | NEW |
| state | CLEARED | status | CLOSED |