List of minimum requirements to use the Liongard Integration in Synthesize billing module.
Before you take wing and truly experience the value of Liongard and Synthesize billing module, please take a few minutes and review the minimum requirements.
The Liongard user that’s being used to set up the integration between Liongard and Gradient must have have Global access in Liongard to all Environments.
Users that are scoped down as an Environment Admin/Reader to certain Environments would be limited in their results.
The following are required when building a custom Metric to map to service(s) in Synthesize billing module.
- Parent/Child Inspector Type (for a list of verified inspectors that work with Synthesize billing module, click here).
- Query results be in the form of a number (aggregated whole number).
- Metric Display enabled.
- Prefix metric name with 'Gradient' (Synthesize billing module filters custom Metrics by this prefix).
Caution Your query may return a string (example: "2") for each system. Use the function to_number to return the parsed number from a string. If you do not convert the query result to a number, Synthesize billing module will run into an error.
For us to evaluate a Metric, the above requirements need to apply. This is an example of a Metric, that evaluates the number of active users for the Inspector Type, Duo Security.
Users[?status == 'active']|length(@)
Use Child Inspector types when creating a Metric
Child Inspector types are required when evaluating data from a multi-tenant account. There are two inspector types within Liongard, a parent and a child inspector. Think of a parent inspector type as an MSP multi-tenant account and the child inspector type as their customers. Parent inspectors and child inspectors may return different Data Prints (raw data).
When creating a Metric, the Metric itself is tied to the inspector type. When you are using the Query Builder in Liongard (Admin > Metrics) one of the first drop-downs you will select is the Inspector, in which you would like to build the query against. Although the Metric itself is tied to both the parent and child inspectors, this ties the Metric you are building to that inspector type. If you were to create a Metric query that would only apply to a child inspector, then the parent inspector would evaluate null.
Bottom line, when you create a Metric it will apply to all inspector types, so once more Discovered Systems are activated and associated to an Environment, we will return data from that System, and the Metric will be active, without any further action.
Map Accounts in Synthesize billing module
Although not required, it's recommended that all your Accounts in Synthesize billing module be mapped. When you first connect the Liongard Integration, you will be prompted to map all accounts to environments. Drag and drop the accounts from Synthesize on the left to the environments from Liongard on the right.
Update Account Mapping
If you need to update Account Mapping after the initial Liongard Integration, simply go to Integrations > Liongard > Configure > Update Account Mapping.
Map Discovered Systems to Environments in Liongard
Only when an Environment is mapped to a Discovered System will Liongard fetch data from that particular system. Once activated, data will be returned from a Metric evaluation.
Best Practices for Using Liongard
Tip Review the Liongard Recommended Weekly Best Practice. Refer to Liongard Helpful Resources for best practices.
Review Discovered Systems
If you have any systems in a discovered state for which you would like to start collecting data, activate them. For any systems for which you would not like to start collecting data, archive them.
To ensure you are taking advantage of Liongard's automated documentation for all applicable systems, review your Discovered Systems by navigating to your Dashboard > Discovered Systems tab.
Liongard's Agents check in with Liongard every few minutes. To ensure your Agents are working properly, check your Agents' status by navigating to Admin > Agents > Last Heartbeat column.
Review Failed Inspectors
To ensure all of your Inspectors are working properly, review your Inspectors' status to see if any may be failing and/or have setup issues. To do so, navigate to Admin > Inspectors > Failed and Setup Issue columns.
Review and implement any next steps to get your Inspectors up and running.