Recent Discussions
Grouping name in graph title
I have a module that creates instances via Active Discovery, and groups them based on an instance level property, "auto.host", which is being assigned via Active Discovery. When applied to a resource, the module name shows up below the resource, the groups appear as children of the module, and then the individual instances show up as children of the groups. The module also has overview graphs that can be viewed by clicking on the group name. But you also get to see all of those graphs when you click on the module name inside the resource. But all of these graphs have the same title, which makes it very hard to figure out which group the graph is for. Is there a way to apply the group name (or some other group-level information) to the graph titles? I've tried adding tokens, but very few seem to work. In particular, I've tried to use the same property that's being used to create the group, and it just shows up as the literal string "##AUTO.HOST##". The only other way I can think of to identify these graphs is to change the actual instance names to include the group names, but that would require hovering over the graph to see.wfaulk5 days agoNeophyte9Views1like0CommentsBug Report: Cisco_NTP DS lacks proper error handling output
If you're getting no data on Cisco NTP and you can't tell why, even after running poll now or running the script in debug, it's because there's some helpful information that wasn't included in the catch block of the script (at least for NX OS). Today I was trying to troubleshoot why we were getting no data on Cisco NTP for a Nexus device. That device happens to have 10+ peers (this is important later on). Running the script in poll now/debug would only result in this: Something went wrong: java.io.IOException: End of stream reached, no match found This is a common thing with expect scripts. The script issued a command and is waiting for a response from the device that matches the prompt. If we were to get a response matching the prompt, it means the device has received the command, executed it, put the output to stdout, and returned to the prompt; the device is ready for the next command. However, this error means that the device responded with something that doesn't eventually match the prompt; the device is not waiting for the next command, it's waiting for something else. The script is waiting for the prompt and the device is waiting for something else. The script waited an appropriate amount of time then executed the catch block, outputing the helpful message above. It would be nice if the catch block output more so we could tell what's going on. How about it outputs the entirety of the SSH session? That would be helpful. Go to line 438 and insert the following in the catch block: println("==================== SSH SESSION TRANSCRIPT ====================") println(ssh.stdout()) println("==================== END SESSION TRANSCRIPT ====================") After adding this, when I executed the script in the debug console, i got this output: $ !groovy agent has fetched the task, waiting for response agent has fetched the task, waiting for response agent has fetched the task, waiting for response agent has fetched the task, waiting for response agent has fetched the task, waiting for response agent has fetched the task, waiting for response returns 0 output: Something went wrong: java.io.IOException: End of stream reached, no match found [MOTD Omitted] sxxxxxxxxxxxxx1# show ntp peer-status Total peers : 11 * - selected for sync, + - peer mode(active), - - peer mode(passive), = - polled in client mode remote local st poll reach delay vrf -------------------------------------------------------------------------------- --------------------------------------- =xxxx:xx:xxxx::x :: 16 64 0 0.00000 =xxx.xxx.xxx.xx x.x.x.x 2 64 0 0.07820default =x.x.x.x x.x.x.x 2 64 0 0.04123default =x.x.x.x x.x.x.x 2 64 377 0.07166default =x.x.x.x x.x.x.x 2 64 377 0.07191default *x.x.x.x x.x.x.x 1 64 377 0.05200default =x.x.x.x x.x.x.x 4 64 337 0.01245default +x.x.x.x x.x.x.x 16 64 0 0.00000default .[7m--More--.[m In this case, the device was waiting for me to press the enter or space keys because the last line of the output was " --More-- ". It took overly long to find this out because the module needs that one thing in the catch block to help troubleshoot.Anonymous6 days ago22Views3likes0CommentsSetting SDTs for the weekend
To set SDTs for "The weekend", it's currently necessary to set three separate SDTs. This is because it's not possible to set the number of hours AND it's not possible to set a 24-hour period. So you have to set ones from: 00:00 Sat -> 00:59 Sat 00:59 Sat -> 00:59 Sun 00:59 Sun -> 00:00 Mon This seems like a fairly basic requirement: "Set a weekend SDT". Fix please? While I'm ranting... what's with the AM/PM nonsense on time selectors?! Anyone who's configuring LM will prefer the 24-hour clock.David_Bond17 days agoProfessor22Views4likes0CommentsLogicMonitor Integration with ServiceDesk Plus
Has anyone been able to get a custom HTTP delivery integration for alerts setup with ServiceDesk Plus? I found a very old article with the V1 API that don't work anymore. Trying to get it setup with the V3 API but I keep getting an error when doing key/value pairs and the RAW JSON is not supported by ServiceDesk Plus anymore.RVanHouten23 days agoNeophyte19Views0likes0CommentsDashboard Table Widget column auto-widths
In the dashboard table widget, the column widths are not dynamic. This may be a good design choice to prevent unexpected UI movement on refresh, but it causes real issues with variable width content. For more than about 4 columns on a regular monitor, you have to zoom out so far to see anything that the font becomes unreadably small. Please provide an option to allow variable-width, autofit columns.David_Bond25 days agoProfessor15Views3likes0CommentsA Push Connector for ServiceNow Event Management
Hi, this is a Push Connector for ServiceNow Event Management. If you are looking to send alerts from LogicMonitor to the Event Management feature this may be helpful. There is a connector for LogicMonitor created by ServiceNow, but it has a number of issues. Some fields are not mapped well to the ServiceNow event, website alerts for example have multiple fields not populated. It doesn't properly handle the non-standard date format LM uses in the alert tokens, and certain time zone identifiers like "BST" or "CST" cause the connector to "crash". This one fixes those issues and does some better mapping for the event fields, additional details are in the repository linked below. https://github.com/chrisred/snow-itom-push-connectorschrisred2 months agoNeophyte30Views1like0Comments