Search the Community

Showing results for tags 'SDT'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • From LogicMonitor
    • Product Announcements
    • LM Staff Contributions
    • Community Events
  • LogicMonitor Product Discussion
    • Feature Requests
    • LM Exchange
    • Ask the Community

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 19 results

  1. 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's multiple 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 tho
  2. I would like to see a prompt for SDT that when I specify "[location].All" LM asks if I would like to place the Collector in SDT. I would never think to look in "Settings" area to place the collector in SDT, or that when I specify "All" the collector is not included. I understand why it separate, but the location for SDT on the collectors is not intuitive. I naturally went to [Domain].Collectors, which was incorrect, after I was told the collector SDT is separate. Thanks
  3. Please implement more granular permissions for SDT function. We would like to be able to grant permission to apply SDT to data sources elements, but NOT on the resource itself. We often encounter situations where by accident or carelessness our staff apply SDT to a resource instead of the data source element.
  4. The SLA report does not have an option to include information about SDT if the event is in the past. Since reports are often developed to look at sla information post-event it's imperative that report columns be added that reflect historical SDT info as well. I recommend not just including the sdted field to indicate whether or not the alert began in a SDT window, but to instead add a new field/column for % in SDT or SDT Duration that provides an indicator as to how much of that alert's period was happening in a SDT window. Example: Planned maintenance window is 2-4. IT change
  5. As an MSP we also manage a number of customer patching 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 will be patched at the same time, so setting at the group level is out). Can we please have the function of being able to select a group and then a number of individual devices from that group (+sub-group) at the same time - ideally being able to see a list o
  6. 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...
  7. Team, Is is possible to make a feature request to allow us to add an SDT on multiple devices but not at the group level? Context: one of our customers have hundreds of servers in one group, and might be turning off a few dozens that need to go in SDT to prevent alerts flooding out, though because they are not turning them all off in the group this involves a lot of manual input. The option to select multiple devices with a tick box, with a select all option, which then allows to apply an SDT to selected would be very helpful. Many thanks, Auriane
  8. We NEED to be able to schedule repeatable scheduled down time, not just on a specific day, but something e.g. 3rd Sat of every month. Can this please be entered as a feature request ASAP!
  9. Hello, I have made a support request (98189) already about this and learned that setting SDT via a Port "Description" is possible through the API. For those that are not API-savvy, I thought making a feature request to do this in the Lomo GUI might be a good idea. I would like to see if the possibility of setting SDT in the Lomo GUI can pull up something like a search page for matching criteria. It could be tags, device names, port descriptions, etc. The use case is for when I do VMware Host Updates, I have to set 11 SDT's individually. 4 for each Core Switch (we have 2, so 8 tota
  10. When we reboot a Server or a Application Set our NOC does not know all the Devices, Instances and/or services impacted so we get flooded with alerts for a known event. Example: I need to reboot device WebServer-xyz - The Server, the Switch ports, Storage Sessions and HTTP/S Service are all monitored in LM Like to be able to SDT just these items with one SDT, and not entire switches or devices. So be able to create an "Alert-Group" ie "WebServer-xyz" where you can then add Instances from multiple devices, entire device, Service, Instance Groups, Device Group aka any defined in LM.
  11. LM, A request that we would like to make is to have any new device added to logicmonitor be placed in SDT for the first 5-10 minutes. We are finding that the devices are not responding to LM initially and throwing Host down errors. Thank you,
  12. Please add an option to add an SDT for multiple groups and services at the same time. I just had to add a SDT for a few groups that are all on the same hosting facility and had to move all of these groups under one parent so I can add the SDT on that parent and today once the SDT is over I will break down this group back into it's sub groups as I do not need this top level group
  13. Hi All, I am looking for powershell script which it can read a device names from txt file and schedule a SDT. Can some one help on this.
  14. Trying to schedule a new SDT for January 1, 2018 1:00 AM to 1:30 AM for a device group, but getting a Status:1007 and a blank response. <# account info #> $accessId = 'SHj6Hub8e63FUwkc5' $accessKey = 'xz37=(][{qb6ANLp}5$-S9Hvn6HV292P' $company = 'api' # stdTYpe (integer) # 1 - one time, 2 - Weekly SDT, 3 - Monthly SDT, 4 - Daily SDT # we have to use "one time" style values because LM has no concept of day of month $stdTYpe = 1 # type (string) # ServiceGroupSDT, DeviceGroupSDT, CollectorSDT $type = "DeviceGroupSDT" # deviceGroupId (string) # $deviceGroupId = 18 # dataSourceId (in
  15. We have requirement of setting SDT to some servers which are in different time zones. The current time zone setting is portal-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 in multiple timezones, suggest LM should look into this and implement this feature on priority.
  16. Currently, Alert sounds are persistent even when an instance is placed in SDT. We need functionality added to suppress all alert sounds while an instance is in SDT.
  17. I want to have a report that will give me all devices that are currently under an SDT, that will show the device name, SDT Start Date, SDT End Date, and the comments of the SDT>
  18. Dear LogicMonitor Team, Greetings. I searched through the forums for a similar request and I apologize if I did not find one previous to this. After continuous use of LogicMonitor with an integration, it has been determined that in the event an alert is generated before SDT is enabled, if the alert should clear the SDT prevents that update from being passed into the ticketing system. This means that there is no notification, nor confirmation, of an issue being cleared during or after an SDT window. What could be implemented to address this issue is a simple toggle switch, in
  19. We do monthly maintence for our clients on the last Sunday of every month. It would great if we could set a scheduled SDT for the last Sunday of every month, rather than specific dates.