Custom Inspector - Build Your Own
under review
K
Kevin Walker
I would like the option to build my own inspector, given a strict structure from Liongard, that would allow me to query an API not yet available in Liongard and capture the response JSON as a data print. Opening this up to a "community space" could allow us all to write and contribute custom inspectors adhering to the strict structure required by Liongard. The community could review, share and implement custom inspectors in their system for the benefit of all.
J
Jean van Zyl
Yes please!
A
Abriyanna Turner
Merged in a post:
Ability to create custom inspectors
A
Aaron-Admin Gitlin-Admin
I would like to have the ability to create custom inspectors or add our own queries to inspectors. This feature would allow us to monitor our SaaS-based voice product, which has an API, more effectively. It would be beneficial to have this capability to tailor the monitoring to our specific needs.
A
Abriyanna Turner
Merged in a post:
Custom Inspectors
S
Sid Pandey
Creating our own inspectors for the apps that are not listed in Liongard
J
Josh Archibald
My idea for this was simple. Allow a custom inspector and in the config, you put the file path to the JSON to import. The layout of the JSON is dictated by the creator of the JSON. For example, you could create a PowerShell script that pulls data for a system into a JSON and places it in an arbitrary path like "C:\Liongard_Custom\System1.JSON" and the inspector runs and reads this path to import the data. In Liongard, there are no tables to extrapolate the data, only the Data Print Explorer tab, because it would be far too restrictive to force a format that the tables can parse.
From there, we can make metrics and alert on the data as we see fit.
It's simple and effective. With this method, you can make as many custom inspectors as you'd like, just feed the local path to the JSON from the agent's perspective when you create the inspector.
Your attack surface by a threat actor is also limited because the path can be anything you want and the JSON file can have any name you want. I'm not sure what attack surface there would be, other than manipulating data to not get alerted, but I'm not a threat actor, so I can't attest to their reasoning. :)
Just the ability to get custom data like this into Liongard for metrics, reporting, and alerting would be a real game-changer. For those that oppose this for the sole reason of not having the skill or staff to create custom scripts, stick with the inspectors that Liongard provides, this isn't for you. :/
A
Austin Unger
Merged in a post:
Custom Inspectors (Inspectors the users build and link into their Roar instance)
C
Craig Butler
I would like the ability to develop custom inspectors. Inspectors that are kinda drag and droppy or generically built. Like "read a windows event log and report things based on it" or Check a registry key. Or run a powershell script and parse the results.Then the inspector reports the results.
A
Austin Unger
Merged in a post:
Ability to create own custom system inspector
S
Shawn Sailer
American Frontier - James Evans
Is it possible to create our own device… like a generic SSH device. We’d specify IP, credentials, and one or more CLI commands to just capture the output from… then build rules based on that?
There are a lot of devices out there (network switches in particular come to mind) that have some general equivalent of the Cisco “show running-config” that would be good to capture and monitor for changes. It wouldn’t be feasible to build a full integration for every manufacturer/model.
A
Austin Unger
Merged in a post:
Ability to create our own inspctors
A
Austin Unger
Having the ability to create or make modificiations to current inspectors in platform will help as we can then integrate with other systems.
A
Austin Unger
Merged in a post:
Build Your Own Inspector
S
Shawn Sailer
On call with established MSP inquiring about ability to bring in data from a system where we have not built an inspection; BYO inspector SDK. Customer is Cyberlogic Stellenbosh.
Give them a path to land data in an inspector that they add calls to bring in data and land in a uniform dataprint that allows them to build their own metrics, alerts and reports from.
A
Austin Unger
Merged in a post:
Custom API inspector type
J
Jesper Jønsson
We would like support for custom API inspectors that can receive data from any authenticated source.Imagine that we want to create a custom "Warranty inspector" type and wish to collect (with push to the API inspector) and inject data (i.e. computer name, serial number and warranty expiration date) from 3rd party systems for processing, reporting and alerting in Liongard. I understand we can get warranty in other ways, but it is a good example to get the point across.
A
Austin Unger
Merged in a post:
Custom Inspectors
R
Roar Support
Custom Inspectors, would be nice to be able to build a custom inspector.
We need for Synology, UPS's.
Would be nice to have a library for these as well so MSP's can share.
Load More
→