Feature Requests

Databases exclusions for MSSQL inspectors

By default (at least in CW) when an actionable alert is sent to the PSA, it adds ROAR links in the public facing initial description.We have clients with access to our CW, but do not give them access to Liongard which makes the LG hyperlinks that appear in tickets a very awkward conversations...It would be great to have better flexibility over this by chosing which links to include, and whether they go in the body of the alert, or the comments.Further to this, it could be configured and inherited at the different levels:PSA integration (Default):Include Roar Links in PSA tickets: yes/noAlert Link: yes/noInspector Link: yes/noRoar Links location: Body (Public)/Comments (internal)Service Board level:Inherit PSA integration settings: yes/noInclude Roar Links in PSA tickets: yes/noAlert Link: yes/noInspector Link: yes/noRoar Links location: Body (Public)/Comments (internal)Actionable alert levelInherit Service Board settings: yes/no (inInclude Roar Links in PSA tickets: yes/noAlert Link: yes/noInspector Link: yes/noRoar Links location: Body (Public)/Comments (internal)

We want to be able to monitor our vendor IP's in their SPF records, to ensure we add them to whitelists when they are updated and we do not get notified about them.

If you have activated Autotask ticket and status sync, the ticket queue is synchronized between Autotask and Liongard. When an alert is created, it enters the designated queue in Autotask. We are accustomed to transferring a ticket in Autotask to a different queue, such as the 1st line or 2nd line helpdesk. However, when the alert is closed in Liongard, the sync process reverts the queue back. This mechanism is not desirable for us.

Please give administrators a way to close an alert while making sure it does not re-open for this specific instance without having to wait 7 days or silence it.Best way for me to explain this is probably through an example:A client of ours had a legitimate A record change to their domain's DNS, but every time we try to close the ticket, it just gets re-opened. Support informed me that the only way to avoid these tickets from getting re-opened is to change the record back to the original value, edit the alert to not detect this change any further, or to wait 7 days before closing it.This seems like a bit of an oversight, administrators should be able to have a status which tells LG that an alert was the result of a false positive and to recognize it as legitimate.

For our customers that are working to become compliant with the ACSC Essential 8 maturity level, we need to have a method of asset discovery on the corporate network. The FortiGate units have this, but we need to have a view of it. So I was hoping LG pulls that so we can tick the box and we know if new devices are discovered on the corporate network. The FortiGate has an option for device discovery. Hence it is on the gate, but I am not sure if that is pulled through to Lionguard. I suspect the inspector just logs the change. Where this comes in handy for us is not only in that it would make clients that need to work towards the ACSC Essential 8 standard compliance but for cloud-first clients that typically have no infrastructure on site, we have something to perform the task since there is no option to run an inspector on-site. I do suspect we might need to work on an inspector in our environment though.

Microsoft has released a dashboard into preview for monitoring Onedrive sync agents in a customer's endpoints.The amount of issues we run into with sync clients and shortcuts is pretty high, and most of the time, the users don't say anything we happen to notice when dealing with another support request.As this feature moves from preview into GA, I think it would be amazing to have an LG alert on when there are issues with the OneDrive sync client to enable our support teams to be proactive when an issue with a sync client has been identified.The alerting will need to be configurable to specify how long a sync issue should be present before generating that alert.