Monitoring Ec2 instances
Hi All, I have been going through the documentation and it suggests that when we are setting up monitoring for ec2 with autoscaling we should select netscan frequency of 10 minutes. This is the minimum time we can configure and new device may take upto 15 minutes to be monitored. My question is is there a way if a new instance is launched we can bring that into monitoring less than 10 or5 minutes.PKI Password Cache monitoring?
Hello there, I am curious if monitoring can be done for this and how it would be done. Is it possible to monitor the password cache space for a PKI server? In particular, password cache for cert enrollment on Network Device Enrollment Service. By default, cert enrollment attempts are put in the cache for an hour if it is deemed incomplete and 5 attempts are allowed to be cached. You can raise this default with the PasswordMax reg key. I figured it would be helpful to monitor this to know what the key value would need to be set to or to be proactive with solving/troubleshooting issues where the cache becomes full. Perhaps a powershell script would suffice? Thanks in advance for any tips! 😄 https://social.technet.microsoft.com/wiki/contents/articles/9063.active-directory-certificate-services-ad-cs-network-device-enrollment-service-ndes.aspx#Password_and_Password_Cache
Office365 Monitoring
Hi everybody! I've been using Mike Sudings monitoring solution for a while and i've expanded it a bit to monitor more solutions in Office365. TheMonitors included Custom Domains (quantity)WHEKJJ Deleted Users(quantity)ZHADY9 Global Admins(quantity)7GGZWZ Licenses Assignable ((quantity) based on type)R46EGX Licenses Assigned(quantity) based on typeGHRNLL Licensed / Unlicesned Users(quantity)4PJZJ4 MFA Users(quantity of enabled/disabled users)WZFAWK Users and devices in Office365 Tenant(quantity) Devices if clients are joined to Azure ADPLMP22 Hope they are helping the community out
Cisco UCS monitoring doubt
Hello, Nowthat a new suite of data sources is available for the UCS stuff, we're havingsome doubts on the monitoring related with the Cisco UCS Manager & their respective components (Fabric Interconnects, etc...) I'm sure the new suite removes the needof the SNMP legacy datasources (that's great btw!!!), however, we're now kinda lost on what should we add into LM (in terms of components). I'm pretty sure in the past we had to add the UCS Manager + the Fabric Interconnect devices (to fetch some hardware related info that wasn't fetched via UCS Manager), but currently, I see the same datasources applied to the UCS & both Fabrics. I'm assumingthat we only require to monitor the actual UCS Manager from now on (everything else will be monitored under it). Specially the hardware portion of both Fabric Interconnects (at least from what I'm seeing). Is my assumption correct? Or, is there anything else we need to have in mind in terms of the Fabrics. Appreciate the clarificationguys! Regards,UNC Path ability to impersonate specific user
Hello, As an MSP we've the need to monitor a lot of directories/shares for the same client. Some of those shares are accessible with the collector user, however, we've some clients that restrict their share to specific users (not the ones running the collector service). I've tried to create a datasource that's a simple runas where we can pass the user/passwd as a parameter, however, that isn't possible to run from the collector level (confirmed by LM staff in a case that I've raised). Can this be implemented? This feature would be very important (since we monitor +100 clients).