How to creat a custom report to find out what devices are currently in SDT
I want to create a report regarding all devices that have been out into SDT in the last month. When I check the Reports secion in LM andSelectReports | Add | Report.it gives me the following Report types: Can anyone advise which would be the best Report type to use for generating which devices have been in SDT over the last month?Solved235Views14likes3Commentsneed 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.25Views12likes1CommentMultiple Device Select when setting SDT
As an MSP we also manage a number of customerpatching cycles, this entails a number of servers needing to be placed into SDT individually for a customer across a number of there groups, with some of our customers this means 60+ servers at a time. (devices can be spread across several groups & not all devices within each said group willbepatched at the same time, so setting at the grouplevel is out). Can we please have the function of being able to select a group and then a number of individualdevices from that group (+sub-group) at the same time - ideally being able to see a list of devices contained with group (+ sub-group) and have checkboxesalongside them so that multiple selections can be made at once. This will make life a lot easier and faster for such scenarios.39Views4likes1CommentAnsible Time Zone Support
Hello! I currently use Ansible to schedule a task which updates Windows on the servers we manage, roughly 300 in Azure. These servers are spread throughout the world in many different time zones. In my playbooks for configuring the “patching task”, I would like to set a SDT in Logic Monitor. Currently there is no “time zone” setting with the Logic Monitor Ansible module. I’m sure I could get around this by doing some sort of math on the date / time within the SDT playbook. Does anyone do anything like this? Some other notes about our setup: We have a mix of Windows Server 2022 and Windows 11 VMs Azure Automation / Update Management does not support Windows 11 VMs Time zones on the servers are local to the region they are deployed in Our patching schedule is … staging 1 week after “patch Tuesday” production 2 weeks after “patch Tuesday” Because of this, reoccurring SDTs need to be reconfigured twice a year, say when the first of the month falls on a Wednesday Sometimes patching needs to be rerun, so it would be nice to SDT the servers / device groups whenever needed Thanks! Jerry34Views3likes0CommentsTime zone set for group of devices
We have requirement of setting SDT to some servers which are in different time zones. The current time zonesetting isportal-wide, so it is not based on group of devices as we require. This would be a very welcome feature for any companies that have sites inmultiple timezones, suggest LM should look into this and implement this feature on priority.12Views2likes5CommentsSchedule SDT for specific events within a EventSource??
Hello everyone, We've multiple Event Sources setup (each one of them covers multiple events (different sources & event IDs). They're kinda in the same category but they cover different events (example Backup Related Events - within those there'smultiple applications, event IDs, etc...). Our question here comes if we need to filter a specific event (within one of those Event Sources) on a specific period of the day. For example, ServerA is returning some events at 2AM EST but those are related with a scheduled job that occurs daily, one of our clients requested us to filter those events (daily from 2AM to 2:20 AM EST). Is there any way to do an SDT (but with a specific criteria)? Without filtering the whole Event Source (that contains more events that shouldn't be suppressed at that time). The reason we've multiple events within a event source is to don't create a lot of Event Sources (thinking on the WMI usage here). We have multiple events on the same Event Source, that way we don't do so many WMI queries. Just asking because in our old monitoring tool we were able to specify specific criteria on the suppression rule(s) & this is really important for us (since we have a lot of those requests). Appreciate the help!38Views1like8Comments