Need to be able to select NOTHING for Alerting on website checks
When setting up a website check, there are two options for Alerting: Of multiple selected locations Of one selected location The Multiple option is enabled by default, but it doesn't include any details of an alert when one comes in. It just tells me how many checkpoints have a problem. The One option is set to Nothing by default, but that option includes details of website alerts, and is far more useful than the other option. I can enable the second option to start getting alerts there just fine. However, there is no "Nothing" choice for the first option so I can't turn those off. This means that if I enable the second option, I'm going to get duplicate alerts all the time. There needs to be a Nothing option in the first box like there is the second box. For anyone who isn't familiar with the differences between the two alerts, here's a sample of the exact same alert from the two alerting options.13Views1like1CommentNeed to be able to set Website settings at the Group level
I need to change the external checkpoints for all the website I have in a certain group/folder. That group has multiple levels of subgroups and dozens of websites. The only way I can see to change this currently is to go one by one and uncheck the unneeded checkpoint on every site individually. It would be so much nicer if I could change the setting at the top level group and then do some sort of "Apply to All" to set those settings on all the sites within that group. Thanks.16Views2likes1Commentneed better SDT support for website checks
At this time, you can schedule SDT for website checks from one or more (or all) locations, but you cannot specify which test is in downtime (like you could for a resource datapoint). As a result, if I want to pause SSL expiration warnings, I must also pause ALL checks against the site, which far from ideal. Please fix SDT for website checks to allow selection of all alertable criteria.18Views12likes1CommentIdeas for tracking LM website docs changes?
Hi gang! I’ve raised this issue to our CSM but I want to raise the topic here for conversation. There might be a technical solution I’m not imagining. When LogicMonitor updates their own support documents on their website, there’s no way to see what exactly has changed - unless the page content explicitly includes such details. Case in point: “Tokens Available in LogicModule Alert Messages” https://www.logicmonitor.com/support/logicmodules/about-logicmodules/tokens-available-in-datasource-alert-messages It reads “Last updated on 13 January, 2023” OK, great - but what changed?? (We make extensive use of Alert Tokens in custom JSON payloads in our LM Integrations which send to PagerDuty. If there’s changes to the Alert Tokens in a way which would affect how PagerDuty ingests and/or routes the Alerts - and I didn’t know about it to make adjustments -that would really stink, and that’s putting it mildly.) Disregarding that specific page however…. Do people have any ideas on how to track LM website changes in a way that would expose the specific changes? I don’t want to have to resort to ConfigSource monitoring of LogicMonitor’s own website, nor do I want to have to resort to writing a web crawler which would download the entire site and commit it to version control like Github - but I’m tempted, which is sad.29Views2likes4Comments