Recent Discussions
Rubrik Monitoring package - REST API being retired
I am hearing that Rubrik is retiring their REST API in favor of GraphQL. This will likely impact the Rubrik monitoring package in LM since the REST API will no longer work. The below documentation from Rubrik suggests that starting with version 9, the REST API will not be supported. It is not clear if there will be backwards compatibility with old REST API tokens but it could cause monitoring to stop working when customers upgrade to version 9. https://www.rubrik.com/blog/technology/23/1/rubrik-security-cloud-transition-from-rest-to-graphql-api Does LM have plans to update the Rubrik monitoring package to use GraphQL queries instead of API calls?15Views1like1CommentNeed to be able to select NOTHING for Alerting on website checks
When setting up a website check, there are two options for Alerting: Of multiple selected locations Of one selected location The Multiple option is enabled by default, but it doesn't include any details of an alert when one comes in. It just tells me how many checkpoints have a problem. The One option is set to Nothing by default, but that option includes details of website alerts, and is far more useful than the other option. I can enable the second option to start getting alerts there just fine. However, there is no "Nothing" choice for the first option so I can't turn those off. This means that if I enable the second option, I'm going to get duplicate alerts all the time. There needs to be a Nothing option in the first box like there is the second box. For anyone who isn't familiar with the differences between the two alerts, here's a sample of the exact same alert from the two alerting options.13Views1like1CommentEnhanced Azure Subscription Monitoring API
We appreciate the robust monitoring capabilities provided by LogicMonitor. However, we've encountered challenges when managing Azure subscriptions. Specifically, enabling/disabling monitoring for new subscriptions requires manual intervention, leading to potential oversights. Our attempted solution involved using the REST API, but limitations with versioning (v3 vs. v4) hindered our progress. We noticed that adding subscriptions to the custom property `azure.subscriptionIDs` doesn't directly impact monitoring. We kindly request the following enhancements: 1. A dedicated API endpoint to enable/disable subscription monitoring. 2. Clarification on v4 API availability or a preview version. Such improvements would significantly streamline our workflow and enhance efficiency.13Views2likes0CommentsNeed to be able to set Website settings at the Group level
I need to change the external checkpoints for all the website I have in a certain group/folder. That group has multiple levels of subgroups and dozens of websites. The only way I can see to change this currently is to go one by one and uncheck the unneeded checkpoint on every site individually. It would be so much nicer if I could change the setting at the top level group and then do some sort of "Apply to All" to set those settings on all the sites within that group. Thanks.16Views2likes1CommentCan't tell if past alerts were during an SDT or not?!
I consider this a bug, but maybe it's WAD and needs to be reevaluated. When an alert occurs during an SDT, the "IN SDT" field for that alert gets set to True. This is good because the alert is during an SDT. The problem is that once the alert clears, even if it's still in an SDT, the IN SDT field gets changed to False. This is not good. Because it does this, there is no way to run a report on alerts for the week/month/whatever and tell which ones were during an SDT and which ones weren't. Example: We do patching every month and this causes some of our websites and servers to go down, and CPUs to spike, while things are installing and rebooting. We set these to an SDT because we know it's going to happen. When we go to run our monthly alert reports, we see lots of errors for uptime, ping, CPU, etc from the checks that ran during the reboot. We don't need to investigate these because they were during SDT which means they were expected. When I set the IN SDT field to False in the report, assuming it's going to then show me only the alerts that occurred outside of an SDT, that's not what I get. I get EVERY alert because that field gets set to False for every alert when it clears. I don't understand what the rationale is for doing this as it removes very important functionality for anyone who runs reports after-the-fact. Simply leaving the IN SDT field alone, when the alert clears, would solve this problem. If the alerts cleared while in an SDT, leave the field as True. If the alert cleared wile not in an SDT, leave the field as False. That way I can tell, and run reports on, which alerts were expected and which were not. Thanks47Views4likes7CommentsBGP Description
The Datasource BGP- shows per BGP instance a Description based on snmp OID 1.3.6.1.2.1.15.3.1.1 which is the bgp peer identifier. That is not the actual description that's configured in the switch. Here is an example ofBGP configurations. address-family ipv4 vrf t01-WAN bgp router-id 11.226.11.2 network 10.251.0.0 mask 255.255.255.0 network 10.251.1.0 mask 255.255.255.0 network 10.251.2.0 mask 255.255.255.0 neighbor 10.228.3.53 remote-as 65500 neighbor 10.228.3.53 description t01 wan koppeling naar rack z1.3.23 neighbor 10.228.3.53 password *********** neighbor 10.228.3.53 activate neighbor 10.228.3.53 soft-reconfiguration inbound neighbor 10.228.3.53 prefix-list t01-WAN-IP-BLOKKEN out neighbor 10.228.3.53 maximum-prefix 200 50 exit-address-family address-family ipv4 vrf a07-GTT-sip bgp router-id 11.226.11.2 network 10.100.128.16 mask 255.255.255.240 neighbor 10.100.128.1 remote-as 65135 neighbor 10.100.128.1 description a07 gtt euro fiber neighbor 10.100.128.1 password ********* neighbor 10.100.128.1 activate neighbor 10.100.128.1 send-community neighbor 10.100.128.1 prefix-list a07-TO-GTT out exit-address-family A snmpwalk on SNMP OID 1.3.6.1.2.1.15.3 doesn't show the neighbor description. How can we get the bgp neighbor description into the LogicMonitor BGP instance description ?23Views6likes1Commentdashboard display user timeout override
We have several ( hundreds of ) dashboards which show pertinent data to the relevant teams here. Each set of teams sit in separate areas, and they all need to see their dashboards. As such, we have set up dashboard stations ( computers with a bunch of screens attached ) so they can put all their dashboards in their own areas on a specific wall etc.. The only portal which is timing out is the LogicMonitor portal. Is there any way to override a specific account to not be bound by the portal settings for idle logons? We need to keep our. timeout settings as 4 hrs for all other users, but these specific screens need to remain forever not being logged out ( as much as is possible ) Is it possible to have a per-account override for “user session timeout” ?33Views5likes2CommentsScript Functions/Modules
Similar to AppliesTo Functions, we should be able to create Script Functions/Modules that all other scripts, e.g. PropertySource,can call. For example I have an API call function embedded in to a single PropertySource. If I need to do the same thing in another script I have to embedit all inline again. And if that grows to 10s or even 100s of scripts and I need to update the code, then it becomes unmanageable. So instead such shared script functions/modules should be able to go somewhere else that we can then import to another script. Both Groovy and PowerShell support this functionality.18Views8likes1CommentAdd collectorgroupid and collectorgroupdesc standard properties
We already have collectorid and collectordesc standard properties, but in all our deployments we have at least 2 collectors. Since in Dynamic Group custom queries you cannot use inherited properties I’d like to be able to specify the query to include resources from the collector group level rather than individual collectors (using OR / || operators), especially since provisioning a new collector to replace a previous one will generate a new collectorid and collectordesc value so the query will need to be permanently maintained. For us at least, new collectors will always belong to a collector group, so this seems to simplify the requirement of splitting up MSP version of LM between multiple customers. The way we handle hierarchy is to add every resource to a static group, outside of any customer folder, then inside each customer folder we have a dynamic group for ‘All Devices’ looking for that customers resources. Currently we achieve this using the API in a PropertySource to grabthe resource’s collectorid value, pass that to the API and return the collectorgroupname value, thenset that returned value to an auto.organisation value at the resource level. And then in the query we have auto.organisation == “XYZ” . Using the API seems an unneededoverhead. Instead, at the point of adding resources, since they already get collectorid and collectordesc added, the Add Device process should include a lookup to get the used collector’scollectorgroup values and set them directly on the resource as collectorgroupid and collectorgroupdesc (to be consistent with the current ones). Then in each dynamic group we can use something like system.collectorgroupdesc == “XYZ” .63Views4likes11Comments