Liongard Ideas Portal

Submit and upvote ideas to make Liongard better. You get 20 votes so vote wisely. 🙂

To learn more about our Ideas Portal, check out our FAQs.
To schedule a feedback session with a member of the Liongard Research Team, click here.

See what we've shipped by clicking here!

Implement Environment/System Level Exclusions for Alerts.

Many of Liongard's alerts are incredibly useful, until you encounter an edge case. We have many alerts that are applicable to 99% of our clients, but we will have one or two clients in situations where something that is "broken" will always stay "broken."

We're at a loss as to how to handle these situations, often telling our helpdesk to just put the ticket into an unmapped status so it can sit there forever, preventing new tickets from generating.

Say we have a client with only 2008R2 servers. We know the client should upgrade, the client knows they should upgrade, but circumstances prevent the client from doing so. We do not need an alert for their Domain/Forest functional level being unsupported/out of date. We're stuck with either parking the ticket in an unmapped status in manage, disabling/removing the inspector entirely, or performing very convoluted template hijinks.

I've seen a few ideas in the portal for exclusions for specific inspectors. It would be far more useful if Liongard were to implement exclusion options at the environment and system levels so that we can truly fine tune our monitoring to serve all of our client's best needs.

Please consider implementing exclusion options at Environment and System levels.

  • Kevin Cowgur
  • Oct 1 2020
  • Reviewed - Under Consideration
  • Attach files