|
Definitely. Nice thing about testing with LDAP queries
though is it can be a normal userid. No admin rights required. Also it will take
a more involved tool generally to start doing perf counters. Not saying people
shouldn't have more in depth monitoring such as MOM or OpenView but it is
sometimes an expense people can't get through the system, spinning
up products like MOM and SQL can be costly if you don't get it for free
plus there is admin overhead that has to be accounted for. I know I fought that
battle for several years for a Fortune 5 company and never got heavy duty
monitoring like that due to costs and politics. In the end it all came down
to my basic perl scripts doing basic things like this and and quite honestly,
that combined with being aware of my DCs and how they should be running kept us
running very well. However, that won't work for everyone.
Anyway, once you start seeing any slowness in basic
queries, then you can bounce into more detailed checking of what is going on. I
have used this method to ascertain issues with DCs in a couple of different
companies. It is simple and basic, but if a DC can't do these simple basic
things, there is definitely an issue to investigate.
joe From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Fleischman Sent: Saturday, November 13, 2004 2:25 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] Script to check on GCs response/health? Perhaps a different way to skin the same cat…..the problem with any single query is that it could be performant in the fact of other, slow things. For example, who cares if ldap is fast if you have a bind perf problem due to slow trusted dc. I think you really want to better measure your app, not as much a single query.
That said, I’d be more interested in watching key perfmon counters, where key==what you are interested in. So, ldap response time, bind time, etc. If it exceeds X ms, then kick out.
My $0.02 ~Eric
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of joe
Sure that would be fine, note that scope is by default subtree with adfind so you can cut out the -s subtree switch.
For the initial startup you might want to run the check every 10 or 15 minutes and see what you get. Build up a map in your head of what it is doing. Then once you are confident on how consistent the numbers are, push the frequency back up to once per hour. Alternatively set a threshhold and if a machine exceed it, crank up the frequency for that machine.
joe
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Thommes, Michael
M. Hi Joe, Thanks for ideas! I've built some code that runs every hour and the numbers are interesting. I've found a couple of GCs that are in the 4 second range while the majority are in the neighborhood of 0.3 seconds but I expect the numbers will fluctuate more as I collect more statistics. Can I assume the following query (using each GC passed as %1) is appropriate?
adfind.exe -h %1 -b dc=xxx,dc=gov -f name=admin-renamed -gc -s subtree cn
Thanks again!
Mike Thommes
|
Title: Message
