Generic RSS EventSource
This is a generic RSS EventSource. Setrss.urlon a host with an RSS URL and it will start monitoring it. Of course, for an LM EventSource yourevents must include key/value pairs for "happenedOn" and "message". If your RSS feed doesn't use these keys, you can override them with therss.event.mapproperty. For example, if the event timestamp is labelledpubDateand the event message is labelledtitleyou can usehappenedOn:pubDate,message:titlefor yourrss.event.mapproperty. You can also userss.event.mapto add other attributes. Locator:YHM79Y Feel free to clone/rename the EventSource if you want more context in the name.49Views0likes2Comments
EventSource - LogicMonitor_Audit_Logs
EventSource to trigger Warning, Error or Critical Alerts from your LogicMonitor Audit Logs, using Resource Properties as search strings to identify matching patterns in each Audit Log's username, ip and description fields: lm.auditlogs.warn lm.auditlogs.error lm.auditlogs.critical LM Locator:763DHG9Views0likes0Comments
Use SOURCENAME for alert value for Windows Events instead of EVETNID
Currently the Value field of an alert shows the EVENTID, which is a number and not very useful. Please add option to instead show SOURCENAME. Even better would be if we could specify our own message in the EventSource to be used instead.3Views0likes1CommentAdd "Test" functionality to Event Sources
I have found the new "Test" button on the Datasources'LogicModule setuppages to be invaluable for testing which hosts are associated with my "Applies to" filter. I can make a change to the filter and then get instant feedback, pointing out typographical errors, mispellings, or even possibly that I got it correct! This will be equally valuable for the Eventsources LogicModule setup pages.2Views1like0Comments
SOLR Error Logs
W9PN3Y I thought I had already posted this one, but regardless - here it is. This does not apply to any servers by default as it can be extremely noisy if you don't have it tuned. This makes an API call to solr to pull error and severe logs and then formats them so that LogicMonitor can understand them. Before applying this, it's not a bad idea to review those logs manually to make sure something isn't repeatedly triggering (as is common with SOLR). Still - it's helped us detect and diagnose a range of issues that would have otherwise been difficult to see.0Views0likes0Comments