Forrest Evans - LM

LogicMonitor Staff
  • Content Count

  • Joined

  • Last visited

Everything posted by Forrest Evans - LM

  1. Hi Cole, predef.* attributes are used by our Topology Service and can't be updated through the API, only through LogicModules. They aren't specific to Azure as they may be applied to standard devices as wel To update a device with Properties and not affect others you'll want to update the device using PATCH command documented here: Pay particular attention to the customProperties opType option. Note: I haven't looked through the code. I'm just offering this based on the last two posts. ~Forrest
  2. Yes. ABCG can properly address collectors of different sizes. The JVM memory value is used to determine how many instances should be assigned to each collector. The configured threshold is used for Medium collectors and the value is scaled up/down.
  3. In my tests I had to wrap the preferredCollectorId value of zero in double quotes: { "name": "", "displayName": "My Device", "autoBalancedCollectorGroupId": 4, "preferredCollectorId": "0" } I acknowledge it's not really consistent with the other ID value for the Collector Group, but give it a try and let me know. ~Forrest
  4. Seems reasonable. I've added a Feedback ticket in our system to track this for upcoming sprints. ~Forrest
  5. Thanks for the idea guys. I saw your Feedback tickets come in that were submitted through your portal and I'll look into how we might be able to accomplish this. ~Forrest
  6. While you pass 0 to set it to AutoBalanced the actual collector that is currently doing the monitoring will be represented in the return value for 'preferredCollectorId' I'd have to try and test your specific scenario and potentially confirm with the developers to see how it would respond.
  7. If you are changing the collectorId within Auto Balanced Collectors there are some other "rules" to follow. If you want to switch a device from being Auto Balanced to directly assigned you have to set `autoBalancedCollectorGroupId` to 0 and `preferredCollectorId` to the collector ID you want it directly assigned to. To set it back to AutoBalanced from directly assigned do the reverse: `autoBalancedCollectorGroupId` sets to id of the group and `preferredCollectorId` to 0 With Version 2 of the API you don't need the $queryparam part. You can just patch with the payload.
  8. Thanks for the feedback. I'm confused why user logins would have such an impact on a collector, but I look forward to seeing your datasource.
  9. When you enable Auto Balanced Collectors on a Collector Group a new column is added with the instance count. I do have an enhancement on the list to always show this count rather than only on Auto Balanced Groups.
  10. Few clarifications around the Auto Balanced Collector solution and when it chooses to balance devices: The AutoBalance is intentionally conservative because when devices are moved between collectors there is a risk of them missing polls. The balancing activity will not trigger a rebalance (even if the button is pushed) if the collector is not over it's own unique threshold limit. In the current iteration, all instance types are treated equally. Since collectors of different sizes can handle different loads we set the default threshold to 10,000 as the number of instances threshold for 2GB of JVM memory, which corresponds to a medium sized collector. The math to determine how many actual instances a collector can handles is the following: (Target_Collector_Mem/Medium_Mem)^1/2 * Medium_Threshold For example, if user sets (2G) collector's threshold to 10,000, for a large(4G) collector, the threshold will be scaled to: (4/2)^1/2 * 10000 = 14140 I checked out your current collectors and none of them are over their corresponding thresholds. The biggest one only had 12,209 instances on a large collector. As for adding devices if you want to add a new device to an AutoBalance Collector Group without choosing the collector the payload below would be a very minimal example to do that. The key parts being the autoBalancedCollectorGroupID is provided as an integer and 'preferredCollectorId' is set to 0 for the device to be AutoBalanced. This should add the device to the collector with the lowest instance count. To create a new device POST to .../device/devices on V2 of the REST API { "name": "", "displayName": "My Device", "autoBalancedCollectorGroupId": 4, "preferredCollectorId": "0" } ~Forrest
  11. We just finished with LevelUp. I'll connect with Support to review the issues you were running into and get back to you tomorrow (Friday)
  12. Hey Cole, Are you having trouble with the newly released Auto Balanced Collectors feature? If so please open a ticket so we can look into it and help. ~Forrest
  13. Hi Akash, We are close to releasing a new feature that will include functionality to spread fail-over of devices among multiple collectors. ~Forrest
  14. Hi DarrylG, I've added this as a feedback ticket in our feature request queue. I believe a few customers might have done this previously. If I can find details I'll reshare them here. ~Forrest
  15. Our official ServiceNow CMDB Integration is now available.
  16. Hi Joe, We have an active project to address this issue which will allow RBAC permissions to be applied to the User Listing. ~Forrest
  17. Hi Samuel, Sending specific alerts from LogicMonitor to ServiceNow is handled through our Alert Rule / Escalation Chains. ~Forrest
  18. Hey Joe, This is actually on our Integrations Road Map for 2019. Look for a much richer integration later this year that will include actions like ACK/SDT and a chatbot to get information back from LogicMonitor. ~Forrest
  19. Hey Mark, For the PagerDuty situation and their V2 of the API we are aware of this and working with PagerDuty on some updates to our Integration. I hear you on the on the bigger picture item though and will enter a feedback ticket in our system to track the request. ~Forrest
  20. Hi Paul, We are actively working on an enhancement to LogicMonitor to support Load Balanced Collectors. One of the key features is that when adding a device you can pick a Collector Group instead of an individual collector. More to come in the next month or two! ~Forrest
  21. Hi Will, For #2, on the latest version of that datasource there is a field for snapshot_age_hours, which, by default doesn't have an alert threshold but if applied could alert if a particular snapshot is over a certain age. #1 is a bit more tricky since it would require an aggregate measure across multiple instances. It could be done with a scripted datasource but but the good news is we are working on an upcoming feature that will be a much better way to solve this. More to come when we are ready to release. ~Forrest
  22. Hi Mosh, Not quite as radical as you think!! We've considered this in the past and the workflow and UI/UX benefits are definitely there. We are working on 2019 roadmap planning and it's on the list to be discussed. ~Forrest
  23. Hi Horace, At this time LogicMonitor supports EventSources to alert on your log entries, but sounds like you are looking for something more in depth. I've sent you a direct message to try and connect and discuss further. ~Forrest
  24. Hi Mark, We are actively discussing options and ideas around this internally and hope to address it in the next calendar year. ~Forrest
  25. I've seen customers export the datasource XML file and programmatically generate the <datapoint> node for all the new data points you want to add. You can then import the updated XML file and the datasource is updated with all the new data points. ~Forrest