configAudit.xml

[MikeLockwood]

Spending some time lately on this... Seems promising but the devil is in the details.

We turned on a few items to see what results. Can't believe how screwy this works - unless we're missing something major.

1. About every 3rd login event is recorded twice, at exactly the same second.

2. Adding a user to a Group (or removing from same) results in a separate line for every context to which that group is mapped (~ 500 lines). It's very, very hard to find"this user got added to this group").

3. Delete records the deletion of Workspaces, including every single publish job (worthless).

4. Another curious thing: For each login, it lists how many users are already logged on at time. Why would they program this?

many more like this - just starting to scratch the surface

Just wondering if anyone has ever in fact seriously used this auditing function.

[MikeLockwood]

More on this...

Well, We just had to shut down production and carefully restart all, with all auditing from configAudit.xml disabled. Turning on just a few elementsin this file completely overloaded the system. We normally run4-6 method server concurrency; it jumped to 170 and all became unresponsive. DANGEROUS!!

[MartyRoss]

What's your configuration?

Can you post your audit config file so we can see what items are enabled / disabled?

Also - which version of Windchill, and what other installed assemblies are there?

[VincentQuesnoit]

Regardingpoint 4, I guess they did it in order to easily get the maximum number of licenses usedfor a given period. this saves writing some code to compute that number from the raw data.

Regards,

Vincent

In Reply to Mike Lockwood:

Spending some time lately on this... Seems promising but the devil is in the details.

We turned on a few items to see what results. Can't believe how screwy this works - unless we're missing something major.

1. About every 3rd login event is recorded twice, at exactly the same second.

2. Adding a user to a Group (or removing from same) results in a separate line for every context to which that group is mapped (~ 500 lines). It's very, very hard to find"this user got added to this group").

3. Delete records the deletion of Workspaces, including every single publish job (worthless).

4. Another curious thing: For each login, it lists how many users are already logged on at time. Why would they program this?

many more like this - just starting to scratch the surface

Just wondering if anyone has ever in fact seriously used this auditing function.