Details
| ID | iLert |
|---|---|
| Provider | Ilert GmbH |
| Category | Messaging and Conferencing |
| From Version | 5.0.0 |
| Docker Image | demisto/python3:3.12.13.10116658 |
| Supported Modules | Agentix XSIAM |
README
iLert is a modern uptime platform with advanced on-call and alerting features.
Alert and notify users using iLert.
This integration was integrated and tested with API version 1 of iLert.
Configure iLert on Cortex XSOAR
- Navigate to Settings > Integrations > Servers & Services.
- Search for iLert.
-
Click Add instance to create and configure a new integration instance.
Parameter Required Server URL True The API key of the alert source (for triggering events only) True Trust any certificate (not secure) False Use system proxy settings False - Click Test to validate the URLs, token, and connection.
Commands
You can execute these commands from the Cortex XSOAR CLI, as part of an automation, or in a playbook.
After you successfully execute a command, a DBot message appears in the War Room with the command details.
iLert-submit-event
Creates a new event/incident in iLert (in order to use this command you have to enter the Integration Key in the integration settings)
Base Command
ilert-submit-event
Input
| Argument Name | Description | Required |
|---|---|---|
| incident_key | For ALERT events, the incident key can be used to deduplicate or group events. If an open incident with the key already exists, the event will be appended to the incident’s event log. Otherwise a new incident will be created. For ACCEPT and RESOLVE events, the incident key is used to reference the open incident which is to be accepted or resolved by this event. | Optional |
| event_type | Must be either ALERT, ACCEPT, or RESOLVE. Default is ALERT. | Optional |
| summary | The event summary. Will be used as the incident summary if a new incident is created. | Optional |
| details | The event details. Will be used as the incident details if a new incident is created. | Optional |
| priority | Must be either HIGH or LOW. Will overwrite the evaluated priority of the alert source. | Optional |
Context Output
There is no context output for this command.
Command Example
!ilert-submit-event summary="Test incident"
Human Readable Output
Incident has been created.
ilert-acknowledge-event
Acknowledges an existing event in iLert
Base Command
iLert-acknowledge-event
Input
| Argument Name | Description | Required |
|---|---|---|
| incident_key | The incident key is used to reference the open incident which is to be accepted or resolved by this event. | Optional |
| summary | The event summary. Will be used as the event description in the incident timeline. | Optional |
Context Output
There is no context output for this command.
Command Example
!ilert-acknowledge-event incident_key="ctx312"
Human Readable Output
Incident has been acknowledged.
ilert-resolve-event
Resolves an existing event in iLert
Base Command
ilert-resolve-event
Input
| Argument Name | Description | Required |
|---|---|---|
| incident_key | The incident key is used to reference the open incident which is to be accepted or resolved by this event. | Optional |
| summary | The event summary. Will be used as the event description in the incident timeline. | Optional |
Context Output
There is no context output for this command.
Command Example
!iLert-resolve-event incident_key="ctx312"
Human Readable Output
Incident has been resolved.
Configuration parameters
url— Server URL (required)integrationKey— The API key of the alert source (for triggering events only) (required)insecure— Trust any certificate (not secure)proxy— Use system proxy settings
Commands (3)
-
ilert-acknowledge-eventAcknowledges an existing event in iLert
-
ilert-resolve-eventResolves an existing event in iLert
-
ilert-submit-eventCreates a new event/incident in iLert (in order to use this command you have to enter the Integration Key in the integration settings)
category: Messaging and Conferencing provider: Ilert GmbH commonfields: id: iLert version: -1 sectionorder: - Connect - Collect configuration: - display: Server URL name: url defaultvalue: https://api.ilert.com/api/v1/ required: true type: 0 section: Connect - display: The API key of the alert source (for triggering events only) name: integrationKey required: true type: 4 section: Connect - display: Trust any certificate (not secure) name: insecure type: 8 required: false section: Connect - display: Use system proxy settings name: proxy type: 8 required: false section: Connect description: Alert and notify users using iLert. display: iLert name: iLert script: commands: - arguments: - description: For ALERT events, the incident key can be used to deduplicate or group events. If an open incident with the key already exists, the event will be appended to the incident's event log. Otherwise a new incident will be created. For ACCEPT and RESOLVE events, the incident key is used to reference the open incident which is to be accepted or resolved by this event. name: incident_key - defaultValue: ALERT description: Must be either ALERT, ACCEPT, or RESOLVE. predefined: - ALERT - ACCEPT - RESOLVE name: event_type - description: The event summary. Will be used as the incident summary if a new incident is created. name: summary - description: The event details. Will be used as the incident details if a new incident is created. name: details - description: Must be either HIGH or LOW. Will overwrite the evaluated priority of the alert source. name: priority description: Creates a new event/incident in iLert (in order to use this command you have to enter the Integration Key in the integration settings) name: ilert-submit-event - arguments: - description: The incident key is used to reference the open incident which is to be accepted or resolved by this event. name: incident_key - description: The event summary. Will be used as the incident event reason. name: summary description: Acknowledges an existing event in iLert name: ilert-acknowledge-event - arguments: - description: The incident key is used to reference the open incident which is to be accepted or resolved by this event. name: incident_key - description: The event summary. Will be used as the incident event reason. name: summary description: Resolves an existing event in iLert name: ilert-resolve-event dockerimage: demisto/python3:3.12.13.10116658 runonce: false script: '' subtype: python3 type: python fromversion: 5.0.0 tests: - No tests (auto formatted)