From atera
Resolves an Atera RMM alert by ID with optional resolution note and ticket creation. Returns confirmation including alert details and ticket ID if created.
npx claudepluginhub wyre-technology/msp-claude-plugins --plugin atera# Resolve Atera Alert Resolve an RMM alert and optionally create an associated ticket for documentation. ## Prerequisites - Valid Atera API key configured - Alert must exist and be in an open state - User must have alert management permissions ## Steps 1. **Get alert details** - Validate alert exists - Capture alert details for ticket creation if needed - Check if already resolved 2. **Create ticket if requested** If `--create_ticket true`: 3. **Resolve the alert** 4. **Return resolution confirmation** - Alert ID and original title - Resolution timestam...
/resolve-alertResolves a Syncro RMM alert by ID, adds optional resolution note, and creates a ticket if specified. Confirms action and returns details.
/resolve-alertResolves open alerts in Datto RMM by alert UID or device hostname. Optionally resolves all device alerts with notes. Outputs confirmation, details, and updated alert counts.
/resolve-alertResolves a SuperOps.ai RMM alert by ID, adds optional resolution note via GraphQL mutation, and creates a linked ticket if specified with custom subject.
Resolve an RMM alert and optionally create an associated ticket for documentation.
Get alert details
curl -s -X GET "https://app.atera.com/api/v3/alerts/{alert_id}" \
-H "X-API-KEY: $ATERA_API_KEY" \
-H "Accept: application/json"
Create ticket if requested
If --create_ticket true:
curl -s -X POST "https://app.atera.com/api/v3/tickets" \
-H "X-API-KEY: $ATERA_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"TicketTitle": "<ticket_title or alert title>",
"Description": "Alert resolved: <alert details>\n\nResolution: <resolution_note>",
"EndUserID": <customer_contact_id>,
"TicketPriority": "<based on alert severity>",
"TicketType": "Incident"
}'
Resolve the alert
curl -s -X POST "https://app.atera.com/api/v3/alerts/{alert_id}/resolve" \
-H "X-API-KEY: $ATERA_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"ResolutionNote": "<resolution_note>"
}'
Return resolution confirmation
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| alert_id | integer | Yes | - | The alert ID to resolve |
| resolution_note | string | No | - | Description of the resolution |
| create_ticket | boolean | No | false | Create a ticket from this alert |
| ticket_title | string | No | - | Custom title for the ticket |
/resolve-alert 9876
/resolve-alert 9876 --resolution_note "Disk space issue resolved by cleanup script"
/resolve-alert 9876 --create_ticket true --ticket_title "Critical disk alert - resolved"
/resolve-alert 9876 --resolution_note "Ran disk cleanup, removed 50GB of temp files" --create_ticket true
Alert Resolved Successfully
Alert ID: 9876
Title: Disk Space Critical (<5%)
Device: SERVER-DC01
Customer: Acme Corporation
Resolution Note: Disk space issue resolved by cleanup script
Resolved At: 2026-02-04 10:30:00
Resolved By: John Tech
Alert Resolved Successfully
Alert ID: 9876
Title: Disk Space Critical (<5%)
Device: SERVER-DC01
Customer: Acme Corporation
Resolution Note: Ran disk cleanup, removed 50GB of temp files
Resolved At: 2026-02-04 10:30:00
Ticket Created:
Ticket ID: 54321
Title: Critical disk alert - resolved
URL: https://app.atera.com/new/rmm/ticket/54321
Alert not found: 9876
Please verify the alert ID and try again.
Use /list-alerts to find valid alert IDs.
Alert 9876 is already resolved
Original Alert: Disk Space Critical (<5%)
Resolved At: 2026-02-04 09:00:00
Resolved By: Jane Smith
No action taken.
Alert resolved, but ticket creation failed
Alert ID: 9876
Status: Resolved
Ticket Error: Customer contact not found
Please create the ticket manually if needed.
Rate limit exceeded (700 req/min)
Waiting 30 seconds before retry...
Permission denied: Cannot resolve alert 9876
Contact your administrator to verify your permissions.
GET /api/v3/alerts/{alertId}
X-API-KEY: {api_key}
POST /api/v3/alerts/{alertId}/resolve
X-API-KEY: {api_key}
Content-Type: application/json
{
"ResolutionNote": "Issue resolved by running cleanup script"
}
POST /api/v3/tickets
X-API-KEY: {api_key}
Content-Type: application/json
{
"TicketTitle": "Critical disk alert - resolved",
"Description": "Alert: Disk Space Critical\nDevice: SERVER-DC01\n\nResolution: Disk space issue resolved by cleanup script",
"EndUserID": 12345,
"TicketPriority": "High",
"TicketType": "Incident"
}
| Alert Severity | Ticket Priority |
|---|---|
| Critical | High |
| Warning | Medium |
| Information | Low |
/list-alerts - List active alerts/create-ticket - Create a new ticket/search-agents - Search for RMM agents