|
So a few ideas have been floated out on
this thread. I can float a few myself if you can answer a question first: what
is your goal? Common goals I’ve heard of:
Or do you have another goal? ~Eric From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of joe One way to do this is set up
"stations" that on some frequency will send ldap queries to your DCs.
You will then simply record the time it took to process the query. Obviously do
something that is consistent (rootdse or specific attribs from the default context) so
your times don't deviate based on amount of information returned. This gives
you data you can track long term for how fast or slow a given DC is. If you
exceed some average you define as bad, you alert on it. This could warn you of
network issues (say a virus is eating up more and more bandwidth) or your DC is
getting overloaded or hurting. joe From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Anyone
found a clever way to monitor and alert on this stuff? J Counters maybe? |
Title: LDAP Query Response Time
- [ActiveDir] LDAP Query Response Time Marcus.Oh
- RE: [ActiveDir] LDAP Query Response Time Chuck Oppermann
- RE: [ActiveDir] LDAP Query Response Time joe
- RE: [ActiveDir] LDAP Query Response Time Eric Fleischman
- RE: [ActiveDir] LDAP Query Response Time Gil Kirkpatrick
- RE: [ActiveDir] LDAP Query Response Time Marcus.Oh
- RE: [ActiveDir] LDAP Query Response Time Centenni, Jason
