Recent Discussions
Kafka Kraft monitoring
Kafka has introduced new solution which is “Kafka Kraft” to eliminate Zookeeper dependency. LM has monitoring metrics for old solution which Kafka with Zookeeper and we are looking for new set of metrics for Kafka Kraft Quorum metrics which has been introduced from last couple of releases. If you go through the below official documentations then you will be getting the context. https://kafka.apache.org/documentation/#kraft_monitoring https://kafka.apache.org/documentation/#kraft_quorum_monitoring16Views3likes0CommentsOfficially Support Citrix Cloud Modules
I've had this topic come up in several support cases, but recently a customer asked that I assist them with a feature request for these specific modules to be under official support by our team. Citrix_Cloud_DeliveryGroups 1.0.0 Citrix_Cloud_Troubleshooter 1.0.0 Citrix_Cloud_OAuth_Token 1.0.0 Citrix_Cloud_Machines 1.0.0 Citrix_Cloud_MachineCatalogs 1.0.0 Citrix_Cloud_LogonPerformance 1.0.033Views5likes0CommentsEnhanced 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.32Views6likes0CommentsFeature request - Add suppression type to the alert list widget
I had a case with Logicmonitor support where I asked if it was possible to filter away alerts that fall under a cluster alert. Here I got the suggestion to use routing state but this does not give anyvalue on a cluster alert. The support engineer looked further into it. "I have tested this further and unfortunately using the routingstate filter is not going to work here as this relates to suppressed by Root Cause Analysis. I'm afraid I'm not seeing an alternative way to removed suppressed alerts from the alerts dashboard widget” So my suggestion is to add suppression type to the filter of the alert list widget.Getting specific datapoints using the REST API
In this post: https://community.logicmonitor.com/archive-13/getting-datapoint-data-via-rest-api-1249 … @Sarah Terry provides information on how to get data for just specific datapoints, reducing load on the API, minimizing network traffic and reducing deserialization load on the client. While this is VERY useful, it is not currently possible to do this for graph data. An example of such a call would be: {{logicmonitor_url}}/device/devicedatasourceinstances/229505122/graphs/-1/data?datapoints=sentpkts …which brings back the default graph data (all datapoints), though this would also work for a specific graph. The advantage of this approach to data fetch is that it permits the retrieval of virtual datapoints. In order to achieve the same benefits, we (Panoramic Data) request that the same datapoint filtering is added to the {{logicmonitor_url}}/device/devicedatasourceinstances/{instanceId}/graphs/{graphId}/data endpoint. Of lesser importance would be other graph API endpoints (e.g. the website graph API endpoint) Thanks in advance! David25Views15likes0CommentsSynthetics - add ability to set device/group properties to reference in the .side file
With synthetic transactions, currently the only way to pass a value into the .side file is within the Authentication step during the initial creation of the synthetic check. The values can be referenced withthe credential.username/password/token variables in the .side file. This is pretty limiting, especially since it can only be defined during the initial check creation. If the password changes for my websites test user, I need to delete/recreate the check to redefine the authentication. This causes a loss of historical data. It would be a huge improvement if we could set a property on the synthetic check in LogicMonitor and then reference that property within the .side file. That way if I want to change the username or password for a check which involves a login, I don’t need to delete/recreate the check.16Views10likes0CommentsSynthetics - add ability to update existing checks and download .side file via configsource
With synthetic transactions, currently you need to delete/recreate a check if we want to update it or change the username/password used for authentication. This causes loss of historical data and is difficult to manage. There are 2 things I would like to request that would make it easier for us to manage synthetic transactions. add ability to update an existing check. This includes updating the .side file or updating the authentication Add ability to download the .side file for an existing check via a companion Configsource. This would make it easier to resolve issues with a check and tweak it without impacting historical data.8Views10likes0Comments