More advanced methods of authentication for Website Checks
We would like to ability to easily authenticate into SaaS products where you have to enter a username and password and click the "Login" button or hit Enter. These days, it seems ADFS and SAML are becoming more popular and the vendors are just redirecting a login page straight to our own SSO site. So the website checks never trigger alerts becauseyou can get to the SSO login page, but after that the application is broken which is really what we want to monitor. Is that something in the pipeline for website checks in LogicMonitor? If not, it would be great to see that. Maybe some way to identify the username, password fields on the page with the credentials stored in properties and the ability to define whether to click a Login button or submit an "Enter" key press.27Views0likes2Comments
Three hosts, one service check?
Hi, I have a datasource that uses a regex to pull values out of some JSON and graphs numerous values. This runs onmultiple hosts and the host goes critical if a particular value hits 0. I don't want the individual servers to go critical, I'd like a service/website check to go critical if two out of three sites return the zero value in their JSON response. I can write a datasource to check the JSON from each site but then I have to apply it to a host, or multiple hosts, and that defeats the point as I don't care if a single one goes away. Is it possible to create a website check that takes in the JSON, extracts the data required, then passes it on to be used in another step which checks the next site, can I alert on values within the response? Is this even the right way to do it? It would be great if a datasource could be run from a collector group rather than tied to a specific host!22Views0likes2CommentsExport Datetimes for Downtime in a Website Overview Report
For context, I'm a consumer of LogicMonitor csv/excel report exports only - I am required to aggregate my exports outside of LogicMonitor so I can use the availability data from our website endpoint checks to build Tableau Reports. Thus, it would be incredibly helpful to my organization if I could obtain an export (csv/excel) from LogicMonitor that contained all webservices downtime (NOT aggregated and reported as ##h ##m ##s) with datetimes for each period of missed polls (downtime). For example, each line in the spreadsheet contain the endpoint details and the start/stop time. For periods of flapping, each there would be multiple lines for the same endpoint, each with their own start and end times. Knowing when downtime is occurring AND knowing if it occurred during a scheduled maintenance period are essential pieces of information necessary to advance availability reporting for our cloud applications and ensure we maintain our SLA (which discounts application downtime for planned maintenance). I draw out my data daily, via a website overview report that excludes SDT from the reported downtime in a csv export.12Views0likes0CommentsWeb Page notifications
I noticed that the communities.logicmonitor.com requests rights to "show notifications". It would be awesome if our LogicMonitor instances could do the same and that we could configure in settings, so that we could push style notifications to our workstations on alerts.0Views0likes0Comments
Recurring SDT spanning multiple days
We are using Website monitors to ping a remote printer 13 time zones away. By design, the printer is unreachable between 18:00 Friday and 06:00 Monday. How can I set up an SDT to suppress alerting during that time period, OR, do I need to set up multiple (overlapping) SDTs to cover the time period? Or is there another way...0Views0likes2Comments