Title: NTDS Diagnostics

Phew J

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Fleischman
Sent: Thursday, April 14, 2005 1:52 AM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] NTDS Diagnostics

 

Oh, so basically, my read on levels confirms what Kevin posted. J

~Eric

 

 


From: Eric Fleischman
Sent: Wednesday, April 13, 2005 10:52 PM
To: 'ActiveDir@mail.activedir.org'
Subject: RE: [ActiveDir] NTDS Diagnostics

 

I’d answer this question two ways:

 

1)       Our general answer to this for all of the ntds diagnostics logging values is “none”, “a bit”, “a good amt”, “a lot”, “a whole lot”, “yowsers” J
Because there is so much logging throughout for each reg value, it’d be very hard to summarize every entry you get for every value in that key. There is no doc of any sort that summarizes what you get with each level in each reg value.

2)       Field engineering is a bit easier, just because it is not weaved in so many places in the code.
Most of the logging for field engineering really gets kicked on when you’re set to 5. My quick read of the logging section for levels tells me that sev_verbose will only get you some summary data, the every-search-filter spew comes with sev_internal. Just took a quick glance at the search stuff, I didn’t look all over, but that’s what it looks like at first glance.

 

So basically, use sev_internal for field engineering. J

 

~Eric

 

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Sullivan
Sent: Wednesday, April 13, 2005 8:48 PM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] NTDS Diagnostics

 

I saw an article showing what you would get if set to 4 or 5 but not specifically 3. I always look at those levels as superfluous. If I need to get info I crank it up get what I need and crank it back down. I guess if you have to leave it running for a while 3 would be an option.

 

·                     DS_EVENT_SEV_VERBOSE
To log a message about the number of expensive and inefficient search operations performed in the last collection period, set the Field Engineering logging severity level to 4 (DS_EVENT_SEV_VERBOSE).

·                     DS_EVENT_SEV_INTERNAL
To log a message about the number of expensive and inefficient search operations performed in individual searches, set the Field Engineering logging severity level to 5 (DS_EVENT_SEV_INTERNAL). This event logs the exact filter used for each search operation that was expensive or inefficient, immediately after any expensive or inefficient search completes.

From http://msdn.microsoft.com/library/default.asp?url="">.  

 

Kevin

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Isenhour, Joseph
Sent: Wednesday, April 13, 2005 2:14 PM
To: ActiveDir@mail.activedir.org
Subject: [ActiveDir] NTDS Diagnostics

 

Hello,

Has anyone out there found a book or a web site that contains a comprehensive list of what each of the NTDS debug levels will show you.  I'd like to know what information will be revealed if Field Engineering is set to 3 for example.

Reply via email to