Recent Discussions
Webhook Event Collection & Cisco Meraki
As a Cisco Meraki Strategic Technology Partner, we are always looking for ways to make our integration the best that it can be, so you can get the most out of your investments with Cisco and LogicMonitor. So, today we kicked off R&D planning for [safe harbor statement] the ability to collect webhook events from Cisco Meraki with the following objectives. Mitigate Cisco Meraki Dashboard API rate limiting. Enable [near] real-time alerts for things like camera motion, IoT sensor measurement threshold breach (or automation button press), power supply failure... Facilite sending webhook events from Cisco Meraki to LogicMonitor I have the following assumptions. Customers want to be alerted on most, but not all webhook events. Customers want to have multiple inbound webhook configurations, i.e. for different tenants/customers or different Cisco Meraki organizations. Cisco Meraki is the first but not the only platform that customers will want to use to send webhook events to LogicMonitor. If you had a magic wand and could make such an integration do exactly what you wanted, what would be your number one ask? Thank you!Bug Report: Incomplete Audit Log message
When recording API access failure, we are seeing the following in the logs: Failed API request: API token TOKENID attempted to access path '/santaba/rest/device/groups/1234/devices' with Method: GET The work "TOKENID" should be replaced with the ID of the token causing the issue.
Datasource runs previously cached nodeJS script.
Hello, This is the second time this has happened to me so I guess there is a way to do this? I have created multiple versions (upgrades) to a nodejs script which is stored in a directory mySqlScript. As seen in the example below my previous version was main.js. If I create a new datasourse and refer to a new script file in the same location i.e. main_v2.js the datasourse continues to use the old .js file i.e. main.js? is there something I am missing?Feature Request: Don't show Green on NOC Widget
I would like tooptionally not see green on the NOC widget. The reason is that the widget is extremely slow to render on an Android device. This is probably because we have (say 10 Crits, 20 Errors, 30 Warnings and then 1000 Normals / Greens. The simple UI implmentation would be to have another toggle on the settings screen between "Warning" and "Acknowledge".
Automate the Infra Alerts
I need to perform the poc on the self-healing part to ensure that any infrastructure alerts that are triggered automatically will result in the job being triggered and resolved depending on the circumstances. So that, customers can reduce the resources and time needed to fix common infrastructure issues.
LM datasources backing up
I attempted to post this with Chrome and it did not render at all :/ hence the undefined but here's a tip (No idea how long it will work for LM DataSources -> Github. (We use GitHub actions on a cron schedule with the below) Create a local readonly user with a password You need to know the current portal version here on it replace $PORTAL with your portal name DBV=$(curl -s https://$PORTAL.logicmonitor.com/santaba/|grep -oP '(?<=sbui)\d+'|head -n 1) Now with the user you created before fetch the whole lot! curl -o lm-backups.xml "https://$PORTAL.logicmonitor.com/santaba/api/downloadConfig?version=$DBV&username=$USERNAME&password=$PASSWORD=$PORTAL"
LM Logs Alert Tokens
We are looking at expanding into LM Logs and I am wondering are there any other hidden alert tokens? We are looking at what structure of the message we can send, and there feels to be a lack of items for LM Logs. Is there a way to pull out some of the log fields as part of the message? The closest we found so far is ##logMetaData## which gives us a json string of our custom fields. For future parties here is a little more detail. ##alerttype## logAlert ##datapoint## Log Pipeline Alert Condition Name ##datasource## LM Logs ##dsdescription## Raw Log Value ##dsidescription## Raw Log Value ##instance## Log Pipeline Name ##threshold## Log Pipeline Alerting Condition ##logMetaData## Log metadata fields included in alert from Pipeline Alert ConditionsWindows Least Privilege and polling (WinServer)
Regarding the Dec 31 Windows Least Privilege nightmare fuel (I know the page claims it wont be strictly enforced) I started testing the script. I've just run it on one collector right now, and it seemed to work for me. I had to wait overnight instead of just 10 minutes, but it did switch accounts, and that account does seem to be able to allow the collector service to do what it needs to do. HOWEVER. We also use that same account for the wmi user. So for the subset of windows VMs that run LM Collector software, the collector runs as DOM\user1 (redacted example). We ALSO use DOM\user1 as the wmi polling account for ALL VMs including the collector ones. We make out collectors all monitor themselves, and so its monitoring itself using that same account. I've discovered that MOST LogicModules continued polling normally after I ran the script, but ONE of them does not: File Server (WinServer). Whatever permissions the LM script (Windows_NonAdmin_Config.ps1) gives to that user, it looks like they overlooked something. Most LogicModules such as CPU, Cores, File Systems, Memory, everything ... the user can poll it. But File Server (WinServer) fails (error message: No data collected from sbproxy). So my final TL;DR question is: has anyone else discovered any limitations in this scenario? Not all Windows LogicModules get applied to every server, so I'm wondering if others have had this experience, and if there might be other LogicModules that suddenly cant be collected when polling with the same user that the collector runs as (after running their script). Thanks!
