Monitor LM Logs Monthly Usage
Summary: Matt Whitney, known as Matt Whitney, raised a concern about exceeding the monthly LM Logs quota due to excessive log ingestion. He suggests that LogicMonitor (LM) should have built-in support to monitor and alert on LM Logs utilization according to the contract, rather than relying on community logicmodules which currently need modifications to work properly. Matt proposes some updates, including the addition of core logicmodules for monitoring usage, projecting monthly usage, and exposing the contracted amount as an API endpoint. He mentions existing community-based modules, like LogicMonitor_Portal_LM_Logs_Ingestion and addProperty_LogicMonitor_Portal_ContractInfo, which have limitations and require customization.
We had an issue recently where we were ingesting excessive logs into our portal, and we exceeded our monthly quota for LM Logs. I would like to request a way for us to monitor and alert on our LM Logs utilization relative to our contract.
There are 2 community logicmodules which are meant to accomplish this, but I think that LM should support this out of the box. The community modules have problems and need to be modified in order to work. I will list them at the end for anyone interested.
Below are the updates LM would need to make to accomplish this:
- Add new Core logicmodules for monitoring LM Logs Utilization
- This should be part of the out-of-the-box LM Portal monitoring. Users should not have to rely on community-based modules for this
- Include projected monthly usage in the core datasource. This is not available in the community-based datasource, but can be roughly calculated with the below formula
- Projected EOM Usage = (Usage MTD / days elapsed in month) × days in month
- Expose the contracted amount for LM Logs as an API endpoint. The community-based propertysource tries to use the below API endpoint for this, but it does not work and LM Support confirms it is not a supported endpoint
- /santaba/rest/usage/contractInfo
Below are the community-based modules which are meant to accomplish this. Minor customizations are needed for the datasource because the propertysource does not work.
- Community Datasource: LogicMonitor_Portal_LM_Logs_Ingestion (Locator: P2WHC6)
- Works with minor customizations to allow setting of the contract amount manually
- Community Propertysource: addProperty_LogicMonitor_Portal_ContractInfo (Locator: CLGTY2)
- Does not work due to API endpoint for contractInfo not being supported
Patrick Sites
·5 months agoAdded to existing future roadmap plans for building Usage Notifications for all product types including LM Logs