Jeffrey McGovern

  • Content Count

  • Joined

  • Last visited

  • Days Won


Community Reputation

4 Neutral

About Jeffrey McGovern

  • Rank

Recent Profile Visitors

345 profile views
  1. +1 I agree - this would be a useful feature
  2. Hey Sarah, I picked it up in the release notes and have already started looking at how to implement some of my existing users under this new type. Thanks for the heads up!
  3. Hey Thomas, You need to call GET: /device/devices/{deviceId}/devicedatasources/{deviceDatasourceId}/instances and retrieve the instanceId from there and then pass the output into your call above. I think what you are trying to do is the last example at the bottom of:
  4. I think that this request dove tails with the request to ACL announcements to a role but can stand alone. I would like to have service announcements logged in a central location rather than just having the UI popup banner. Something like Settings --> Account Information --> Platform Messages This way as an MSP if I need to send any information to the user base when the information does relate to them there is the ability pull from an authoritative source. It will also be extremely helpful when you look at the pop up banner and say to yourself that you need to write that informatio
  5. Hey Grant, Have you figured out how to do this? Probably not the most elegant solution to the problem because it will most likely involve changing existing process but a way to solve this would be to create a device group (something like _implementation_) and then using Advanced Netscan dump all new assets into this group rather than unmonitored. This would then allow you to run a standard device inventory report against that group. Not elegant but would get you from here to there. The only other thing I can think of would be to submit a Feature Request to be able to add a custome
  6. I agree that there needs to be a mechanism to hide these from portions of the user base.
  7. Hey James, Another way to do this might be with a property source. If you take a look at this article in the 'From the Front' forum you could do something like create the 'snmp.working=' tag that would then automatically populate once AD runs. This would then allow you to validate based on monitored protocol rather than asset type. The WMI example is pretty easily modified (pull something like winders version) to create a 'wmi.working=' to catch that as well. Cheers!
  8. Problem I have a datasource that collects information from the LogicMonitor API. In order for this to work correctly I need a valid user on the LM platform with a valid API token. I can see two potential paths forward. Case 1 - Use my existing account as the datasource author with my API token. This has a big downside that if I have to leave the company for any number of reasons and my account gets disabled this datasource will stop working and is customer facing. This is probably not so good. Case 2 - Create a 'service account' inside LogicMonitor that can have its' own API tok
  9. Use Case: Provider I am a provider with a substantial amount of customers being monitored by the platform. A single customer requests monitoring to be suspended for 14 days as they do a physical DC move. The move will be 1:1 so all systems will come back up in same logical location and only move physical locations. Requests are filed, meetings are had and the day comes to move and NOC turns alerting off for customer. Uneventful days go by and on the day that alerting is supposed to be turned back on a regional event happens that the provider NOC is responding to for other customers
  10. Use Case: I am a provider with loads of customers using the system. Operators working on MACs must navigate the flat user tree looking for specific users for any number of a myriad of reasons. One of the main use cases for this feature is to avoid mix ups when multiple customers have very similar names only differentiated by domain. Think Jim Smith as an example. Request: Looking for a way to “containerize” users in the User Access -> Users tab. It would be extremely cool and helpful to be able to add groups on this screen to contain customer’s users in a single bucket.
  11. Looking for a simpler way to create standardized dashboards during onboarding process. Use case: I am an MSP who builds three (three is arbitrary but this story gets worse if this number grows) default dashboards for any customer who signs up for my service. As an initial step the provider creates these dashboards using widget tokens and place them in a non-customer facing group so that the provider onboarding operators can clone them. Today this means that the operator must: 1. Go into the dashboard section of the UI 2. Create a new dashboard group for th