Liongard Ideas Portal

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


The Product Team is constantly reading your ideas and while we can’t promise that all ideas will become a reality, we value your feedback and promise to always have our Partners in mind when building and improving Liongard.

Check out our FAQs to learn more.

See what we've shipped by clicking here!

Ability to Audit Inspector Configuration (Quality Control)

The intent behind this idea is that I want to have quality control with respect to how consistent my company's engineers are with properly configuring inspectors to our standards. Like most MSPs, we have a naming convention that spreads across our supported customer environments. Our processes are dependent upon that level of predictability.


My expectation is if my company's engineers are following standards, then all inspectors of a certain type will all look alike. Those that don't will need to be corrected.


What's currently missing is the ability to audit all inspectors for their configured values. In this case, it would be for the inspector's configured username.


  • Travis McMurry
  • Mar 1 2021
  • Reviewed - Under Consideration
Last Reviewed Date 2022-01-09
  • Attach files
  • Guest commented
    26 Sep 10:51pm

    Thinking outside of quality control for just a moment, just being able to monitor what is configured for customer environments and what changes due to any one variable Audit Logging 101. Here's an example -- When you configure your Metrics and then enable Change Detection to monitor that for your customer sites --- and that setting is disabled you NEED TO KNOW --- not being able to see when/who disabled that setting is a HUGE security issue. It baffles me that knowing what Liongard stands for --- CHANGE MONITORING --- that they did not BUILD THIS INTO the environment as its own inspector or even a basic audit log or report.

    This is a huge flaw in what I consider one of the most amazing systems I use and recommend to so many IT professionals on a daily basis.

  • Travis McMurry commented
    24 Mar 03:16pm

    Adding more to this idea, there is no way to know how an inspector was created, either manually or automatically. It's impossible to determine in Liongard's UI how a given inspector was created.

    Consider the case where an internet domain is created because it's auto-discovered. Nothing in the inspector will state what it was created from, though it may be possible to search through related inspectors for domains and find the link manually. Also consider the case where an inspector was auto-created however the thing it was auto-created from no longer exists, so now there's no obvious causal link with the discovery. There would be no possible means in the UI to link the inspector to either manual or auto-creation.

  • Travis McMurry commented
    1 Feb 11:47pm

    Adding to this idea, we had an inspector be moved to an incorrect company. However, we don't have a way to audit who made the change to the inspector so we don't know whom to hold accountable for the change.