Thanks Steve, that worked like a charm. :-) It's interesting that the report compiler chooses to summarise even though the reports themselves are different.
Another thing that struck me as a little strange is the fact that only the first LDAP search to trip the rules thresholds generates a warning. In other words, all subsequent searches that exceed the threshold appear in the report without a warning. On the whole I really like it, especially with the detail shown when setting the expert level to 10. Tony ---------- Original Message ---------------------------------- From: "Steve Linehan" <[EMAIL PROTECTED]> Reply-To: [email protected] Date: Thu, 24 Aug 2006 20:36:18 -0700 The tracing code still fires even if the data is cached, i.e. an LDAP request is still made. What I believe you are seeing is the report compiler summarizing the results. You can change to expert level to 10 which will cause the report to have all entries in it. Thanks, -Steve -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tony Murray Sent: Thursday, August 24, 2006 10:23 PM To: [EMAIL PROTECTED] Subject: [ActiveDir] Server Performance Advisor Hi all I've been looking at SPA and have been trying to get it to report all LDAP searches. I've managed to get it to report searches, but the results are inconsistent. For example, if I kick off the performance capture and then run an LDAP search that exceeds the configured warning levels I will see something like this in the AD.XML file: <item level="1"> <data name="Client">192.168.102.11</data> <data name="Choice">deep</data> <data name="ObjDn">dc=colours,...</data> <data name="Filter">SAM Account Name with multiple AND parts and wildcards</data> <data name="Index">idx_samaccountname</data> <data name="DsSimpleStatus">Success</data> <data name="ObjVisited" warning="adTopObjectVisited">900</data> <data name="ObjReturned" warning="adTooManyObjectReturned">900</data> <data name="requestRate">0.02</data> <data name="responseTime">103</data> <data name="cpu">0.22</data> </item> If I run a subsequent capture, using the same (or similar) search criteria it doesn't log the LDAP search activity in the AD.XML file. I suspect this perhaps has to with the DC caching search criteria, but I'm not sure. Can anyone shed any light on this? Or, put another way, has anyone successfully and consistently captured all LDAP search activity using SPA? Tony ________________________________________________________________ Sent via the WebMail system at mail.activedir.org List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.activedir.org/ml/threads.aspx List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.activedir.org/ml/threads.aspx ________________________________________________________________ Sent via the WebMail system at mail.activedir.org List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.activedir.org/ml/threads.aspx
