>>Just catching up on your posts..
>>
>>As far as selecting which recycling events to log:
>>
>>The first four options correspond to the four checkboxes in the Recycling tab of the Application Pool properties window. You'd only need to monitor the ones which were checked. It might be worth adding the IsApiUnhealthy and RecyclePrivate memory - if those events occur it could indicate some problem with the app itself (eg. a memory leak).
>>
>>Also I guess you don't need to generate your own Guid in Application_End - you can access the actual process Id via ProcessInformation.ProcessID which will make it easier to correlate with the IIS log....
>
>Thanks for the additional information
>
>The fact that I create a record, which I can add valuable information in it, makes it easier for me to use the primary key of the IISApplicationCycle record, from that table.
>
>The attached file shows the logging event. Basically, on this server, I see that the recycles happens every 25-35 minutes, which I cannot understand. I also attached the IIS application pooling information. It is presently set to the default, thus 1740, which means at every 29 hours.

On the application pool properties I'd be inclined to use the third option and pick a quiet time for the recycling to occur. The default of recycling every 29 hours is not so good because it will often recycle at busy times.

Also, for current purposes. why not set the LogEventOnRecycle to 255 and catch all of the options.....