Need 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.Why are websites missing so many features and treated differently than computers?
Every time I try to do something with websites I just get angry. I can't change settings at the group level like I can with resources. Can't easily change thresholds or anything. The Info tab is blank so I can't see any detail about a website. If I try to use the API, the formatting is all different so I can't get any tree/group information to filter results. Everything just sucks about how websites are different than resources. Why is this? Is there any way to pull a list of all the websites under s certain folder in the tree? I can't find any way to do that. I can't even pull a list of all and then filter by a Group field because it only shows the immediate group and nothing about the higher level groups it's in. I need to check all the sites under a particular top level folder, to make sure the alerting is the same. There appear to be absolutely no way to do this without manually going to each sites and checking it by hand. Thanks.
Templates for Web Checks
One feature that makes LogicMonitor so powerful is the combination of Auto Discovery and the AppliesTo feature onLogic Modules. Except that this is entirely missing for Web Checks. Several of our products are web-based. We need to monitor many instances of these products across many client environments. We would like to be able to define a Web Check “template” that uses variables in pre-defined Steps, which can be cloned/deployed for each client. Even better…I’d like to specify an FQDN or base url, and have LogicMonitor perform Auto Discovery to decide which Web Check is appropriate for this instance
need 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.Can a website check look for multiple occurrences of a JSON item?
Hi, Normally I have a website that looks through JSON and picks out a pair like Status = Complete. However, I now have a JSON result that includes multiple statuses in one file. I need to be able to parse through all the occurrences of “state” and verify that all of them are either “running” or “completed”. Is there any way to do this through the LM gui? I was told I might have to use a Groovy script, but I don’t know what that is or how it works (not a programmer). If anyone can guide me towards a solution for this, that’d be great. Thanks!v3 Python SDK outdated?
Hello, I’m trying to use the Python SDK to add websites for monitoring. For my current use case, the primary reason for this is to gain some alerting on our SSL expiry times. Using the SDK has been a generally frustrating experience all around so far, however I’ve noticed that the v3 API is returning fields which aren’t supported or documented by the SDK or API docs. Specifically, for the Website endpoints (GET/POST/PUT), the top-level fields `schema`, `trigger_ssl_expiration_alert` and `trigger_ssl_status_alert` are all unsupported in the 3.0.172 SDK. Unfortunately these also all sound like the fields I need to be setting in order to get SSL monitoring set up. It also appears that the top-level `schema` field is required to enable HTTPS monitoring, as the `schema` field in the `steps` is ignored. I can see that this top-levle field is set to https when toggling the schema in the web UI, when using dev tools to inspect the request. I’ve already done a fair bit of work using the SDK, so I’d hate to have to rip it out at this point and start building all my requests manually in order to support this. I’m using logicmonitor_sdk 3.0.172 at present, which is the latest available release via Pip and tarball. I can see that these fields have been added on the master branch in Github. Is there a timeline for the release of these changes? While I’m here, can I also ask that this functionality is added to your Terraform provider, because that would save me a lot of hours and stress going forward. 😉
Ideas 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.