Andrew, I'd point out that the alert you have is from when the average
response over a period of time hit 20 seconds, which could have been from a
request(s) finished by the time the alert was generated. To be clear, there
is a separate alert that can fire when more than x requests are running for
Thanks for the suggestions guys.
On 28 March 2012 10:11, Kai Koenig wrote:
> Agreeing here - the internal monitor is a performance drain - known issue :)
>
> I'd support using FR, version 4 has also a few nice improvements re memory
> monitoring over version 3.
>
> If you don't want to use an ext
Agreeing here - the internal monitor is a performance drain - known issue :)
I'd support using FR, version 4 has also a few nice improvements re memory
monitoring over version 3.
If you don't want to use an external product you can use JRun Metrics or just
plainly cfstat to monitor and log thin
I had big issues a while ago using the built in coldfusion monitor,
the monitor itself seems to cause performance problems. I would
recommend turning it off and using third party monitoring tools.
I can recommend Fusionreactor but there are other ways to capture
performance metrics besides the buil
Hi,
I have the "built in" ColdFusion Monitor enabled on one of my instances,
and it regularly sends me a slow server alert. I set it to send a snapshot
when it sends the alert, and the snapshot seems to indicate the server
isn't processing any requests:
Average server response time is more tha
