Web Monitoring - Millisecond Trigger Resolution.

[wstiern]

Hi there.

I'm migrating from Nagios and we have some web applications that require us to respond in sub-second intervals. Though it appears that web monitoring does return the response time at that resolution, when setting up a trigger to alert on that value is it evaluating based on seconds or milliseconds? If seconds, is there some way to trigger based on millisecond-level response time values?

Thanks in advance for any assistance offered. Sorry if this is a silly question, I couldn't find such information either in the docs or with some searching.

[wstiern]

Found this in the web monitoring section of the 2.x docs:

"This item will collect information about the response time of the step in seconds. Response time is counted from the beginning of the request until all information has been transferred."

Sure would be awesome if the resolution of the response time item matched the resolution of the web scenario check.

[jschlegel]

I ran into the same problem. It does appear the web monitoring item value is displayed in ms but the trigger is expecting seconds. Since it's floating point I was able to work around the issue by specifiying decimals of seconds. A particular step I was monitoring was supposed to occur in under 100ms so the trigger looked something like:

{HOST.NAME:web.test.time[Download Login Page,Get Initial Login Page,resp].last(#1)}>0.1

Using the decimal the trigger performed as expected, alerting when response time was greater than 100ms.