This post is part of Operationalize Your World post. Do read it first to get the context.
While a
Bad career move if your Mgmt knows issue before you do, so Alert is not applicable
This post is part of Operationalize Your World post. Do read it first to get the context.
While a
Bad career move if your Mgmt knows issue before you do, so Alert is not applicable
This blog is contributed by my friend Luciano Gomes, a VMwareTAM in Rio de Janeiro Area, Brazil. Thank you, Lucky!
In this post, I would like to show how you can monitor Microsoft Active Directory.
First, let’s get the prerequisites out of the way:
With the above done, download the dashboard I created. Import it into vR Ops.
Once done, follow the steps below to configure the Metric Config XML Files. This is required to drive the widgets, so they show the correct metrics.
The above will take you to the Manage Metric Config screen.
You will need to repeat this step 4 times, please, make a note and repeat the name exactly like listed below:
ad-server.xml
<?xml version="1.0" encoding="UTF-8"?> <AdapterKinds> <AdapterKind adapterKindKey="EP Ops Adapter"> <ResourceKind resourceKindKey="Active Directory"> <Metric attrkey="AVAILABILITY|ResourceAvailability" label="" unit="" yellow="" orange="" red=""/> <Metric attrkey="THROUGHPUT|DSClientBindsperMinute" label="" unit="" yellow="" orange="" red=""/> <Metric attrkey="THROUGHPUT|DSDirectorySearchesperMinute" label="" unit="" yellow="" orange="" red=""/> </ResourceKind> </AdapterKind> </AdapterKinds>
ad-ldap.xml
<?xml version="1.0" encoding="UTF-8"?> <AdapterKinds> <AdapterKind adapterKindKey="EP Ops Adapter"> <ResourceKind resourceKindKey="Active Directory"> <Metric attrkey="Active Directory LDAP:LDAP|AVAILABILITY|ResourceAvailability" label="" unit="" yellow="" orange="" red=""/> <Metric attrkey="Active Directory LDAP:LDAP|THROUGHPUT|LDAPSearchesperMinute" label="" unit="" yellow="" orange="" red=""/> <Metric attrkey="Active Directory LDAP:LDAP|THROUGHPUT|LDAPNewConnectionsperMinute" label="" unit="" yellow="" orange="" red=""/> </ResourceKind> </AdapterKind> </AdapterKinds>
ad-authentication.xml
<?xml version="1.0" encoding="UTF-8"?> <AdapterKinds> <AdapterKind adapterKindKey="EP Ops Adapter"> <ResourceKind resourceKindKey="Active Directory"> <Metric attrkey="Active Directory Authentication:Authentication|AVAILABILITY|ResourceAvailability" label="" unit="" yellow="" orange="" red=""/> <Metric attrkey="Active Directory Authentication:Authentication|THROUGHPUT|NTLMAuthenticationsperMinute" label="" unit="" yellow="" orange="" red=""/> <Metric attrkey="Active Directory Authentication:Authentication|THROUGHPUT|KerberosAuthenticationsperMinute" label="" unit="" yellow="" orange="" red=""/> <Metric attrkey="Active Directory Authentication:Authentication|THROUGHPUT|KDCTGSRequestsperMinute" label="" unit="" yellow="" orange="" red=""/> </ResourceKind> </AdapterKind> </AdapterKinds>
VM-OS-AD-metrics.xml
<?xml version="1.0" encoding="UTF-8"?> <AdapterKinds> <AdapterKind adapterKindKey="EP Ops Adapter"> <ResourceKind resourceKindKey="Windows"> <Metric attrkey="FileServer Logical Disk:C:|UTILIZATION|Avg.Disksec/Transfer" label="" unit="" yellow="" orange="" red=""/> <Metric attrkey="FileServer Mount:C:\ (local/NTFS)|UTILIZATION|UsePercent" label="" unit="" yellow="" orange="" red=""/> <Metric attrkey="FileServer Physical Disk:0 C:|UTILIZATION|%DiskTime" label="" unit="" yellow="" orange="" red=""/> <Metric attrkey="FileServer Physical Disk:0 C:|UTILIZATION|Avg.DiskQueueLength" label="" unit="" yellow="" orange="" red=""/> <Metric attrkey="FileServer Physical Disk:0 C:|UTILIZATION|CurrentDiskQueueLength" label="" unit="" yellow="" orange="" red=""/> <Metric attrkey="FileServer Physical Disk:0 C:|UTILIZATION|DiskReadBytes/sec" label="" unit="" yellow="" orange="" red=""/> <Metric attrkey="FileServer Physical Disk:0 C:|UTILIZATION|DiskWriteBytes/sec" label="" unit="" yellow="" orange="" red=""/> <Metric attrkey="NetworkServer Interface:Network Interface eth10 (ethernet)|THROUGHPUT|BitsReceivedperSecond" label="" unit="" yellow="" orange="" red=""/> <Metric attrkey="NetworkServer Interface:Network Interface eth10 (ethernet)|THROUGHPUT|BitsTransmittedperSecond" label="" unit="" yellow="" orange="" red=""/> <Metric attrkey="UTILIZATION|CpuUsage" label="" unit="" yellow="" orange="" red=""/> <Metric attrkey="UTILIZATION|PercentUsedMemory" label="" unit="" yellow="" orange="" red=""/> <Metric attrkey="UTILIZATION|PercentUsedSwap" label="" unit="" yellow="" orange="" red=""/> </ResourceKind> </AdapterKind> <AdapterKind adapterKindKey="VMWARE"> <ResourceKind resourceKindKey="VirtualMachine"> <Metric attrkey="cpu|capacity_contentionPct" label="" unit="" yellow="" orange="" red=""/> <Metric attrkey="cpu|usage_average" label="" unit="" yellow="" orange="" red=""/> <Metric attrkey="diskspace|actual.capacity.normalized" label="" unit="" yellow="" orange="" red=""/> <Metric attrkey="diskspace|underusedpercent" label="" unit="" yellow="" orange="" red=""/> <Metric attrkey="mem|host_contentionPct" label="" unit="" yellow="" orange="" red=""/> <Metric attrkey="mem|usage_average" label="" unit="" yellow="" orange="" red=""/> <Metric attrkey="storage|totalReadLatency_average" label="" unit="" yellow="" orange="" red=""/> <Metric attrkey="storage|totalWriteLatency_average" label="" unit="" yellow="" orange="" red=""/> </ResourceKind> </AdapterKind> </AdapterKinds>
That’s it!
To use the Dashboard, watch the 45 seconds video below:
PS: If you like the soundtrack, the music is Plain Truth offered for free by Gunnar Olsen. Nice right! 🙂
You can reduce the following resources from a VM:
Network isn’t something you can reduce, but you know that already 🙂
You can check which VMs need more resources by building a dashboard like the one below. It’s a simple dashboard, which you can customize and enhance. It lets you reduce the resources independently.
I’ve marked the above dashboard with numbers, so we can refer to them:
The CPU and RAM have limitations. For example, they may show high utilisation during AV backup. You want to ignore those period. At this moment, the only way is to plot the high usage over a line chart. We use Log Insight for this. The chart below shows VMs that hit high CPU usage in a given period. Every time a VM hits high CPU usage, it will show up here. As you can see, there are only 4 VMs that hit high CPU usage. All other VMs do not need more CPU.
The above is an example from a healthy environment. What about an environment where a lot of VMs are under-sized? You expect to see lots of alarm! That’s what you have below
Hope the above is useful. If not, drop me an email.