Could you please guide me on how I can manage the usage of LM logs?

It appears that our current usage of LogicMonitor logs storage has exceeded the allocated limit of 180GB. How could we address this over usage issue? Do you have ideas on how to prevent this from happening in the future?

tuco

Posted 1 year ago·Last reply 10 months ago

3 comments

Balint Pelhos

·10 months ago

Thanks patricksites , it helped us.
By default I filter on modules with "Official" support only, and therefore I never found the "LmLogs_Ingestion" datasource by myself. This datasource has the "Community" support tag only, but works properly, it gives back same value as seen on Settings-Usage page.

tuco

OP1 year ago

Hi Patrick,

Thanks for responding but I would like to know if how can we prevent this from happening in the near future? Your solution is alerting but its not really resolving the issue

Patrick Sites

·1 year ago

Hi Tuco,

Some LogicMonitor customers have experienced unexpected overage charges related to their contracted monthly LM Logs data ingestion limit and looking for ways to be notified or alerted when/if they exceed a limit or nearing.

Here is the installation process and module information for two new LogicModules that extend the functionality of LogicMonitor Portal Monitoring to include log data ingestion and generate alerts on monthly ingestion contract milestones.

Installation

Check to see if the portal has already set up LogicMonitor Portal Monitoring. If so, their portal should contain a resource with display name "portalsubdomain".logicmonitor.com
If LogicMonitor Portal Monitoring has not already been setup, instruct or help the customer to configure it as described here: https://www.logicmonitor.com/support/logicmonitor-portal-monitoring
Go to the LM Exchange and search for package called LogicMonitor Portal Monitoring Add-ons – alternatively, search for the two LogicModules by their locator codes (below)
Install the package of LogicModules (2)
Allow time for Active Discovery and PropertySource modules to run; after complete you can validate that the modules are working by checking the portal resource (“portalsubdomain.logicmonitor.com”) to validate that it contains contract information as properties on the resource (“auto.lm.contract….”) and shows metric activity on the graphs for the DataSource called LogicMonitor Portal LM Logs Ingestion
Inform appropriate parties of changes needed to Alert Rules and/or Escalation Chains to ensure that the contract milestone alerts are routed appropriately

Module Information

LM Exchange Package: LogicMonitor Portal Monitoring Add-ons
PropertySource LogicModule locator code: CLGTY2
DataSource LogicModule locator code: REZ3HG

I also suggest using the links to the right of the usage number which resources or resource groups might be your top talkers and use our new LogPatterns feature to narrow in on the noisiest logs and consider filtering those out to reduce some of the noise.

You can read more about Patterns here:
https://www.logicmonitor.com/support/log-patterns

Please reach out to the LM Support team if you need assistance.

Cheers!

Patrick

1	SUYASH GAIKWAD
2	PJ Pankaj Jain
3	KT Kyle Taylor
4	KV karthikeyan VG
5	ME Mir Ehtesham Ali
6	SN Sangeetha Nataraj