Reading Actionable Alerts
View Actionable Alerts in Liongard
Navigate to your Dashboard screen, and select the "Total Open Alerts" section or the "Open Alerts" tab. Here, you will see the list of open Actionable Alerts across all Systems and Environments in Liongard.
To dive deeper into the alert, click into the Title of the alert.
- To send Liongard's Actionable Alerts to your PSA as tickets. Visit our How to Set up Actionable Alerts documentation.
You can also view Liongard's Actionable Alerts in an Environment's Single Environment Dashboard. Navigate on your Dashboard to your Environments tab. Click into an Environment. Then, select the Total Alerts Tab. Here, you will see a list of alerts for the Environment you've selected.
Find everything you need inside the Actionable Alert
Here's what you'll see when you open an Actionable Alert.
Every Actionable Alert will contain the following information to help you understand and resolve the issue:
|Priority||Priority of the alert. This can be changed from Low, Medium, High, or Critical.|
|Start Date||Assign a date for your team to take action|
|Due Date||Assign a date for your team to complete the action|
|Status||The following are the only auto-generated statuses for alerts:|
New: A new alert has been created based on an Actionable Alert rule. This status maps to the PSA. Liongard will automatically update this status.
Reopened: An alert's status will automatically change to "Reopened" if the Actiobale Alert rule is retriggered within the last seven days. This status maps to the PSA. Liongard will automatically update this status.
Closed-Complete: Based on the last inspection, the Actionable Alert rule condition has been resolved. This Status maps to the PSA. Liongard will automatically update this status.
Silenced: An alert's status will automatically change to "Silenced" if the Alert or Alert Rule is silenced using our Silence Actionable Alert Rules and Alerts feature.
The following statuses can be manually used to update Liongard's alerts.
These statuses are NOT mapped to the PSA and are not updated by automation.
Closed-On Hold: The alert has been placed on hold. This status does not map to the PSA. If Liongard's automation moves the alert's status to "Closed-Complete," then, the status of the alert in your PSA will be updated by automation.
|Finding||The issue Liongard identified in the system.|
|Concern||An explanation of why this is an issue to educate your team and customers.|
|Attack Vectors||Potential areas of weakness or exposure to third-party attacks|
|Action||How your team can remedy the issue right now|
|Keywords||Tags to categorize issues for your own internal sorting and filtering|
|Comments||A space for your team to add notes|
Do know that once an alert is closed in Liongard, if the issue duplicates within seven days of the close date then Liongard will reopen the ticket.
Get Liongard's Actionable Alerts as Tickets in your PSA or Microsoft Teams
Liongard's Actionable Alerts can generate tickets in any PSA Liongard integrates with by using Liongard's Actionable Alert templates.
To set this up, you'll first turn on the integration:
- Turn on the Autotask Ticketing Integration
- Turn on the ConnectWise Ticketing Integration
- Turn on the Kaseya BMS Ticketing Integration
- Turn on the ServiceNow Ticketing Integration
- Turn on the Syncro Integration
- Turn on the Microsoft Teams Integration
From there, using Liongard's templates, you'll select which rules you'd like to turn on, for which companies.
On the Open Alerts page, you can always navigate to view Liongard Actionable Alerts in your PSA by selecting the link button.
Linking Tickets in PSA Integrations
Once an Actionable Alert is generated in a template that is set to send tickets to one of our PSA integrations, a link is created in Liongard to view the alert in your PSA.
If this link is deleted in Liongard, the alert will not update your PSA integration.
Example ConnectWise Ticket
Example Autotask Ticket
Example Kaseya BMS Ticket
Example Syncro Ticket
Example Email Ticket
Example Microsoft Teams Card
Change Detection Alerts
Liongard's Change Detections allow you to capture critical changes to the systems you are managing.
Change Detection Alerts are considered to be any alert rule that uses the "changed" operator. Additionally, when the "changed" operator is selected, a Change Detection will automatically be enabled for that alert rule.
After an Inspector runs, Change Detection alerts will trigger if the Metric the Actionable Alert rule is built on changes. The alert exists to notify you of the change.
In the alert, you will find, in addition to the Body and Alert Comments, a RoarBot comment detailing the change to the Metric.
Any changes added will be noted in green. Any changes that were removed will be noted in red with a strikethrough.
If you are sending these Change Detection alerts to ConnectWise, once you have reviewed the alert, close the ticket in ConnectWise. This will then close the ticket in Liongard.
If you are using Liongard's alerts in Liongard and/or other PSA integrations/Email, you will need to close the Change Detection alert inside Liongard once you have reviewed it.
To close an alert, please review our Closing Liongard's Actionable Alerts documentation.
Reading Change Detection Alerts in PSA Tickets
When Change Detection alerts are sent to PSAs (Autotask, ConnectWise, Kaseya BMS, etc.) changes will be notated differently than in Liongard.
Any changes that were added will be noted by "+" and any changes that were removed will be noted by "-"
For example, here is how a change that was added will be displayed in the RoarBot Autotask comment:
Here is how a change that was removed will be displayed in the RoarBot Autotask comment:
Here is how a change that was removed will be displayed in the RoarBot ConnectWise comment:
Updated about 1 year ago