Feature Requests

This currently provides ipv6 failover information, which is not useful. The command has changed slightly and we need to specify ipv4 here to pull the ipv4 FailoverLBStatus.

With the new "managed printer" inspector, it would be great to have printers auto discovered via the windows inspector.There is already a metric by Liongard for windows printer list:Printers[?Local == true && Shared == true ].Name | sort(@)And the windows Printer list has PortName already... Printers[?Local == true && Shared == true ].join( , , [join( : , [ Name , to_string(Name)]), join( : , [ PORT ,to_string(PortName)])])

When Roar brings over the SonicWALL serial number to ConnectWise Manage it puts in dashes. The dashes are preventing Warranty Master providing lookup of warranty information.

For example, if the client can install Intercept-X or not.

When setting up the Amazon Web Services Inspectors, In the bottom of the settings you have to choose regions..I am missing the Eu-north-1 in the dropdown listLooks like the regions added the last 2-3 years is missing in the list.Here is the complete list of current regions to datehttps: //docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.RegionsAndAvailabilityZones.html

Synology has a builtin tunneling system that allows you to access your NAS via URLs like mymachine.quickconnect.to . It does some magic to determine if you are on the local LAN or remote and redirects you to the local machine or via another URL like mymachine.us1.quickconnect.to . It appears to be a pretty direct tunnel equivalent to using 5001 on the LAN.I tried using the existing inspector with the us1.quickconnect style link and it didn't work, but the URL it referenced in the logs seemed to return valid data, so it may not be much work to get the inspector happy using that kind of URL. The work to cope with the full quickconnect redirect magic would take a bit more.

The auvik inspector is collecting the device data and the device details data separately and exposing it as two seperate objects. Unfortunately it does not appear that JMESPath supports a rich enough query syntax to be able to join these two data structures together on ID. That makes the devicedetails section less than useful since you don't even have access to the device name.In reality, it'd be more useful for that extended info to just live under the device itself - maybe as a deviceinfo key. This would allow me to do queries such as a list of devices that are managed (billing yes) and a network type that have broken SNMP.

Add windows server local firewall (wf.msc) to Windows inspector. Powershell commands:Get-NetFirewallProfileGet-NetFirewallRuleThis would help with security checks, as well as tracking changes.

Currently the inspectors and agents only support RedHat, Debian and Ubuntu which is leaving out distros such as CentOS, Fedora, Kali, and others.It would also be nice to support non-standard distros. For example we use a product called FreePBX who re-package the standard CentOS 7 distro into their own called Sangoma OS. This was for licensing purposes but under the hood it's still CentOS. Support for these would be great as we have no way of monitoring these critical servers with Liongard right now.

This would be nice to see under the Network Configuration tab next to the vlan name. This would help identify all the vlan's in the network and their vlan id (especially for VMware networking and voip) NetworkConf[? vlan_enabled == true ].[vlan, name] [] | join( , , @)