financialme
11-17-2006, 01:39 AM
The UsageSummary app & Control Panel APIare very interesting.
It appears that with the API, a dASP can automatically perform "Application Pool Recycle and Site Stop/Start", although this doesnot appear to be a part of the ready-made Usage Summary app.
But, what are the guidelines or circumstances under which "Recycle" or "Stop/Start" should be initiatied, besides a hung application or locked files?
For example, I know that dASP provides separate Application Pool for each customer and that 100 Meg is a memory limit.
Isn'tit important for the client to know how closethe client's app/web memory requirements are in relation to this threshold and shouldn't this be a vital part of < scheduled > usage monitoring (ie. contained as part of the Customer API) due to its importance?
If, for example, memory use was approaching the 100K, wouldn't it be valuable for a dASP client to programmaticallytrigger "Application Pool Recycle" and send an eMail alert to the client (administrator)?
TIA
It appears that with the API, a dASP can automatically perform "Application Pool Recycle and Site Stop/Start", although this doesnot appear to be a part of the ready-made Usage Summary app.
But, what are the guidelines or circumstances under which "Recycle" or "Stop/Start" should be initiatied, besides a hung application or locked files?
For example, I know that dASP provides separate Application Pool for each customer and that 100 Meg is a memory limit.
Isn'tit important for the client to know how closethe client's app/web memory requirements are in relation to this threshold and shouldn't this be a vital part of < scheduled > usage monitoring (ie. contained as part of the Customer API) due to its importance?
If, for example, memory use was approaching the 100K, wouldn't it be valuable for a dASP client to programmaticallytrigger "Application Pool Recycle" and send an eMail alert to the client (administrator)?
TIA