• Content Count

  • Joined

  • Last visited

  • Days Won


Community Reputation

8 Neutral

About Nick

  • Rank
    Community Whiz Kid

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Nick

    SDT "groups"

    This is a serious headache for us as well, we need the ability to set Mass select/administer SDT as the current either at an overall group or individual device/instance level is far too restrictive/labourious. I have Feature Requested through our CSM '+' for the following that would certainly improve/help with the various patching/maintenance scenarios across WAN, Hybrid, Application, Azure/AWS environments, as well as make customer/service desk users lives easier for those that do not know or want to jump through API - prep/upload - (post) verify in LM resource views that actions applied; keeping these bulk action within the LogicMonitor UI would keep the process streamlined. 1 - At Group & Datasource level, 'SDT' tab - checkbox's alongside 'Device'/'datapoint' instances so that multiples of devices/datapoints can be selected and added to SDT at the same time without having to do all or each individually, (Think along the lines of the 'Instances' tab already under resources but with the ability to select/apply SDT) 2 - Ability to submit/apply SDT by selecting 'Properties' (custom, system, auto) - this again would give more flexibility to either create custom properties for specific instance scenarios or use properties that apply across multiple instances/groups, allowing for bulk administration for 'Resources' & 'Websites' here's hoping the idea or variation gets traction
  2. A much-needed feature, pop-up confirmation on drag n drop etc - I would, however, leave out the option to 'do not ask me again' as some people might select that option the first time and then they would be back to the same scenario now. The extra mouse click of a confirmatory action is very minor when comparing the potential consequences of dragging one customer device group into another, especially if individual customer 'ServiceNow' or other integrations have been set up.
  3. Totally agree the need for the ability to set escalation chains (+time based)/alert rules with 'Public holidays' in mind is a missed feature that should be standard within the LM Admins toolbox
  4. In addition to the above request and being able to use 'checkboxes' alongside devices under groups to multi-select numerous individual devices and place them into SDT at the same time, (consider windows server patching). I would also like to have the ability to place multiple devices into SDT based upon 'custom properties' (tags), this will help with various scenarios within cloud/hybrid environments where dynamic grouping does not. We are now able to set alert rules based upon custom properties (tag's), can we get the same with SDT?
  5. Agree, need the ability to merge/take into account existing datasource customisation with a new/updated version from LogicMonitor - there is already a difference test in place when you look at the repository/updated ds, taking this to the next level by listing differences found and then giving the 'admin' the option to approve/reject those specific difference changes could/would be useful - I realise there will be limits/caveats to this but..... I believe that LogicMonitor has the Datasource update/merging process on their roadmap for later this year??
  6. Ditto - we have an "xx Not Live xx" Group any new onboarding projects get added to subgroups of this, we then set alert rule to this 'not live' group with email notifications etc going to null@null.null i.e. nowhere. this enables us to see all alerts on newly imported devices and work on them from there.
  7. Hi Mike, There are a number of alarms only visible/shown by the vCenter above & beyond the Alarms seen at the ESX host level. The ability to alert on these is greatly needed, however filtering of these alarms at one level or another to cut the noise is also vital, especially when dealing with multiple vCenter's. vSAN monitoring yes please, we are seeing more and more of this. Also VCSA - (vCenter appliance), with VMware 6/6.5 onwards we will only get these Linux based virtual appliances, we already have a significant number deployed, whilst the vCenter datasources are good for the 'vCenter' application there is a big hole in the monitoring capability for the underlying disk space & VM services - we can configure SNMP on these appliances and then use the Linux ds to see the disk space there is nothing for the services out of the box - we have also seen some potential performance/stress related issues with running SNMP on some of these appliances, so preferably any new DS should be using the New VCSA 6.5 API to look at and pull the various stats/status information. Thanks Nick
  8. I Agree with this request for the reasons given and would ask that it is taken one step further in also having a "Note's" section on the device 'info' tab/page. This would give administrators the ability to add notes of interest/url links etc for a specific device for any known issues or special instructions etc as the 'Description' field is not fit for this purpose.
  9. Agree, we need a couple more Website check locations in the LM cloud side - The USA has 3 checkpoints, Asia, Australia & Europe have 1 a piece how about a further website checkpoint from the London DC & another from a Central Europe location?
  10. I agree that this is a tricky one, not just for iDRAC but also iLO & CIMC which is all the same just different manufacturers. We have to create 2 devices and associate them together by the name, i.e. servernamexx & servernamexx_iDrac / servernameyy & servernameyy_cimc, Invariably these cards are accessed via there own NIC/IP Address, the IP Address at times being on a different range from the main server device. Although it would be good to get away from the 2 device license cost for this scenario type, it would also be really good if the device object upon 'add' or later 'manage' would include the ability to have 2 IP Addresses associated to it so that in effect the Server device and associated iDrac/iLO/CIMC could appear within LogicMonitor as one device entity.
  11. Agree with this and would like to see it taken further. We do a lot of Alert Analysis on a bi-weekly/monthly basis and any data we pull will only show alerts that are 'actually' in SDT at the time of data being pulled, there is no additional marker to state/indicate that an alert was generated whilst the device/datapoint was in SDT - this means that we invariably investigate & misreport on alert numbers as there is no way to differentiate. This aspect needs addressing urgently so that those carrying out deep SLA & Alert Analysis can obtain accurate data from which to base reports on. Thanks
  12. Can confirm, once SNMP is setup on the individual CIMC's (standalone 'C' Series etc) and that you have added the CiscoUCS category to the device you will then get the UCS Component Health datasources applying - we have been using this for some time now. CIMC's that are part of 'B' series (Blades) managed by UCS Manager pick up the config from this and hardware health of the blades show under the overall UCS view.
  13. I have submitted this as a request previously and would hope to see some movement on it soon. Ability to view vCenter alarms within LogicMonitor & then to be able to select/filter which alarms trigger LM Alert notifications (warn/error/crit) will greatly help, especially MSP's like us with multiple vCenters to monitor/manage.
  14. 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 of devices contained with group (+ sub-group) and have checkboxes alongside them so that multiple selections can be made at once. This will make life a lot easier and faster for such scenarios.
  15. Agree with Tim, Also it would be extremely useful to be able to use the ##dsidescription## (datasource instance description) within dashboards, our particular use case is for showing WAN/Firewall Interface descriptions (circuit id's) within table widgets etc, this is something else we cannot currently do.