Recent Discussions
Citrix Cloud Monitoring
Installation 1. Install the package from LM Exchange "Citrix Cloud" 2. Install Cloud Connector property source: Locator JYW9D7 Configuration This datasource requires several properties to be set: CITRIX.CLOUD.CUSTOMER - This is found in the Citrix Cloud Portal: Identity and Access Management > API Access > Secure Clients. Copy the bolded customer ID on the page. CITRIX.CLOUD.ID - Create a secure client, you can name it "LogicMonitor". The ID here will be used for this property. CITRIX.CLOUD.PASS - This is the secret when you created the secure client. CITRIXCLOUD.OAUTH.KEY - This will be autogenerated and populated by LogicMonitor using the above credentials. There is a Citrix Cloud OAuth datasource that will generate a bearer token and save it as a property on the device. LM.API.ID - Create an API token in LogicMonitor with administrator privileges, copy the Access ID. LM.API.KEY - This is the API token access key that was created above. LM.API.ACCOUNT - This is your LogicMonitor account name, you can probably copy the subdomain of your LM portal. https://yourco.logicmonitor.com 1. Set the properties above (except CITRIXCLOUD.OAUTH.KEY) wherever you'd like depending on your folder structure. I like to set the LM API properties at the root and the Citrix Cloud properties per client (folder). 2. Find your cloud connector device in LM and add the category "PrimaryCC". Make sure you have the Cloud Connector property source installed as well! 3. The OAuth datasource should run, generating a token that the other datasources will use to query Citrix Cloud's API. You can also do a manual "poll now" to speed up the process. You should now see the CITRIXCLOUD.OAUTH.KEY property on the device. If you have any issues, feel free to private message me!Modules for Zerto monitoring
Hi, here are some modules to monitor Zerto via their API. Appliances (ZVM/ZCM) and the Zerto Analytics portal are supported. I have made the .xml export of each module available on Github, they can be downloaded from here: https://github.com/chrisred/logicmonitor-zerto The modules are: ZertoAnalytics_Alerts.xml ZertoAnalytics_Datastores.xml ZertoAnalytics_Sites.xml ZertoAnalytics_Token.xml ZertoAnalytics_VPGs.xml ZertoAppliance_Alerts.xml ZertoAppliance_Datastores.xml ZertoAppliance_PeerSites.xml ZertoAppliance_Token.xml ZertoAppliance_VPGs.xml ZertoAppliance_VRAs.xml I'll try to keep an eye on this post for any questions.Modules for Citrix Cloud/DaaS/VAD monitoring
Hi, here are some modules to monitor Citrix DaaS/VAD via the Citrix Monitor API. These might be helpful with mixture of DaaS and on-prem VAD environments as the same modules can be used for both. Setup details are in the module notes, see the CitrixDaaS_Token notes for the Citrix Cloud API setup. I have made the .xml export of each module available on Github, they can be downloaded from here: https://github.com/chrisred/logicmonitor-citrixdaas The modules are: CitrixDaaS_ApplicationUsage.xml CitrixDaaS_ConnectionFailures.xml CitrixDaaS_DeliveryGroups.xml CitrixDaaS_LogonPerformace.xml CitrixDaaS_Machines.xml CitrixDaaS_Token.xml I'll try to keep an eye on this post for any questions.
DFSR Replication Backlog
XKJNGZ Uses Powershell to make WMI queries to get the current backlog file count for each outbound DFSR partner on each DFSR share. These queries can be expensive if the backlog is large, so the polling interval is set to 10 minutes. If there is no backlog, the script finishes quickly. No default alerting is set, but I would recommend adding a threshold to be notified of potential replication issues. NOTE* - The collector must be able to reach both DFSR partners and will use the same credentials to make the queries for both.Fortigate Managed Switches
We were having trouble monitoring Fortigate switches once they had been brought under Fortimanager control as they no longer can be queried directly with SNMP. The switches get onboarded to a 169.x.x.x management network and while it might be possible to make firewall rules etc and use the Fortinet_FortiSwitch datasources it wouldnt be fun or practical in all collector deployments. So we made an addition to fortigate Fortinet_FortiGate_ManagedSwitch Published with identifier MK3TRR Collects; 1. switch status (up/down) with an alert 2. Status of ports 1-52 and collates into a total switch port utilisation complex datapoint with graph. Hope this is helpful
Rubrik: Cloud Data Management & Enterprise Backup
* FYI: Official LogicMonitor supported Rubrik modules are now in CORE * Here's some Rubrik LogicModules. *NOTE: Alert thresholds have been lightly/conservatively set. Requires rubrik.user & rubrik.pass be set. PropertySources Rubrik_Product_Info CDA9LK addCategory_Rubrik NGLPWA DataSources Rubrik_Archive_UnmanagedObjects 4376C6 Rubrik_Cluster_Hosts X6CXZN Rubrik_Cluster_Nodes 6D43GA Rubrik_Global_IOStatistics PGJYTY Rubrik_Global_PhysicalHostIngest 6RGWMJ Rubrik_Global_Storage EZHJFX Rubrik_Global_Streams EHX4RZ Rubrik_JobMonitoring_ActivePast24Hours 2NP6RY Rubrik_MSSQL_Databases Z622YK Rubrik_Node_Drives RHZT4F Rubrik_Reports_ObjectBackupTaskSummaryBySLADomain MH2Y6J Rubrik_Reports_ObjectProtectionSummaryBySLADomain TDXHH9 Rubrik_Reports_SLAComplianceSummaryBySLADomain 6Y9NNM Rubrik_SAML_SSOStatus TFHRFN Rubrik_SLA_Domains 44THK9 Rubrik_Storage_CompressionStatistics AC7WEE Rubrik_Storage_ManagedVolumes RW6ZCA Rubrik_VMware_VMs XLT9LL
windows certificate store scan
I have written a DS that uses PowerShell to discover any SSL Certificate within the Windows certificate stores and generates alerts for those expiring soon and for those that have already expired. The alert messages are still generic as I am fighting a weird timeout issue with the data collection code against remote devices. The AD code works fine and the data collection code is virtually identical, simpler in fact as we have the serial number on hand. If I run it from the collector itself in a PS console, it also works fine. Just seems to go to lunch when run from within LM itself. If anyone wants to take a look and see if they can find the problem, that would be much appreciated -- my intent is to polish it up and release it publicly. It is in code review, not clear how long that will take with the new LMExchange feature. 2YPMLNWindows Scheduled Task(s) monitoring
Hello folks, We had a request from a client where he had the need to monitor some important scheduled task(s). While checking the documentation, we wanted to avoid the procedure on the actual 'Job Monitor' for scheduled tasks (since the clients is kind of harsh when it comes to make changes in their boxes, even if those represent no harm). Since we were only interested in the actual task return code (after its run), we've done a quick DS (powershell). Just sharing it here in case it's useful for anyone. GitHub repo -> Here For now, we're alarming on the actual task return code != 0. Since MS advises that anything differing from that represents some sort of issue. However, if you've any ideas/improvements just let me know :)/emoticons/smile@2x.png 2x" title=":)" width="20" /> Thank you!
