Nick

Members
  • Content Count

    33
  • Joined

  • Last visited

  • Days Won

    8

Everything posted by Nick

  1. There is a definite need for the ability to carry out synthetic transactions/test ability to access (auth), websites/open links, Desktop/Applications etc in Azure, AWS & other environments, to verify availability, load/run times, (latency etc). This would give confirmation of User/Customer experience and help identify issues, which in this form is not available in LM at this time, but should be. This capability needs adding asap, at a CAB I attended in November this, (synthetic trans.), was on the road map for 2020 (poss release Sept.) and was 'vigorously' discussed by many there stating the sooner the better as it is a large gap in performance/service level offering monitoring.
  2. As an FYI - I have added the following OID to the datasource I have downloaded so that we can see the Maximum Session count (Raw Data) - this may be of use to others as well. alSslStatsMaxSessions - 1.3.6.1.4.1.3076.2.1.2.26.1.3.0 Description - "The maximum number current of active sessions at any one time."
  3. Thanks for getting this pushed through, with all that's going on at the moment it saved a little time in putting something like this together. & Thanks to @Sawer.lef for publishing in the first place
  4. @Stuart Weenig it would be good to have this anyconnect sessions module asap, my company use the cisco anyconnect for vpn and due to corvid19 have just been told to all work from home so this would be useful to track VPN connection usage etc thanks
  5. Unable to download, states it is "LogicModule is Private, Cannot Read" - is this because LM are vetting it?
  6. 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
  7. 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.
  8. 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
  9. 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?
  10. 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??
  11. 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.
  12. 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
  13. 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.
  14. 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?
  15. 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.
  16. 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
  17. 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.
  18. 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.
  19. 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.
  20. 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.
  21. Would like to see this at the individual Role level as well as being able to select multiple roles at the same time - as an MSP with multiple customers/users and different contractual/service requirements being able to select which Role/Customer to send notification emails to would be great I also agree with Mosh on the ability to configure the number of inactive days prior to an automatic 'deactivation' of a user account + auto email notification will be a good step in helping user clean up, we are not always notified of when users leave organisations - would like to see this as a Global Role/User option & with the ability to override at a role/user level to help compensate for customers or individuals (directors or suchlike) that only log on once in a blue moon.
  22. Agree with this, our service desk guys would like this feature/ability very much
  23. Hi Joe, Whilst this may work in some circumstances it would not allow for the layering of action based upon alert rule/chain, requirement across multiple devices over multiple Cloud tech, cloud/Geo-location & Technology groupings within a defined customer group structure. The ability to apply SDT & Aert Rules based upon selectable custom properties, 'Tags', (if under customer group with tag 1 Or If under customer group with tag 1 & tag 2 etc) would give a logical option for lightest touch on admin and a form of automation. I am looking at this to help with AWS & Azure, (application of secondary tags via cloudwatch/on VM's etc based upon criticality or ?), with the follow-on of this within/across hybridised environments. I hope that I have put enough up here for the train of thought to be followed as I do not want to bore everyone with several paragraphs, more than willing to discuss at length offline.
  24. Ability to set Alert Rules & SDT based upon ‘Tags’ (Auto/Custom/System properties) As an MSP with service desk we are looking to automate & dynamically assign alerts and incidents as much as possible, to this end we would like the ability to set either Alert Rules &/or SDT based upon ‘Tags’ (Auto/Custom/System properties) – this would enable dynamism within alert notification & allocation? The main case scenarios for this are; Cloud devices (AWS/Azure) there are times when certain VM's, WebApps etc only need to send alerts during specific time periods, such as from 0830 to 1800hrs, outside of these hours no alert notification to be sent. Whilst manually setting SDT on individual devices is available it is not dynamic, so if a secondary 'Tag' was applied to Cloud VM, Webapp, etc and in turn that this can be shown within the devices Info page (Auto/Custom/System properties) and then have the ability within SDT &/or Alert rule configuration to select these so that we can associate a specific alert notification schedule/allocation based upon the 'Tag' - in effect making the process dynamic as the customer/MSP team would define within their cloud administration secondary 'Tags' on devices they want specific alerting times/allocation setting up on - given the dynamism & fluidity of Cloud based system provision and requirements the current model is not flexible enough and increases the admin burden within LogicMonitor. Alert Rule application based upon Multiple ‘Tags’ (Auto/Custom/System properties) – There is already the ability to set ‘Tags’ at customer group &/or device levels; to enable more dynamism, being capable of setting ‘Alert Rules’ based upon ‘tags’ and multiple ‘tags’ in layers will allow the distribution of alert notifications to teams based upon service level/contract & device/datapoint importance. Customers invariably have devices/systems/services of differing importance and need actions/notification accordingly. For example; Different (Auto/Custom/System properties) can be set at ‘Group’ & ‘Device’ levels – ‘Tag 1’ (customer/service desk team group – Platforms, Cloud, Networks, Apps), ‘Tag 2’ Criticality (High, Medium, Low) based upon service level & customer requirements. ‘Alert Rule’ config would be created with the option of selecting ‘Tag 1’ & then ‘Tag 2’ and then applying an escalation chain. Notifications are then sent to the correct team/individual who can then act accordingly.
  25. Currently the HTML widget allows the display of externally available webpages which is great and enables an active view of customer-chosen websites within dashboards, however, we are getting a number of requests for the ability to display internal only facing webpages for the same reasoning as the external. Many customers have Internal CRM/Accountancy/Tech Administration/virtual desktop systems that are accessed via Web Gui and not available to the Internet. This will help as a visual availability check on dashboards, but the main reason for this is from IT staff/teams where they have storage, proxy, network & other systems that are not always monitored by LogicMonitor or offer the ability to do so but have their own status dashboards within their webpages – to be able to display these within the LogicMonitor HTML widget would enable the single pain of glass pov. Can options be created within the HTML widget to select a collector to run the display from? I realise that polling/refresh times for internal website monitors would need to be larger than the external to reduce collector strain/bandwidth considerations, say min (shortest) refresh of once every 15mins??