by admin on
July 31, 2007
July 31, 2007
In my previous blog entry on July 17th I continued talking about defining SLAs. Here I complete that conversation.
In Longitude, you can either use the Statistics Dashboard or the SLA itself to observe transaction response times and get a reasonable first cut estimate for values to use as degraded/unacceptable thresholds. In the statistics dashboard, simply create a widget for the transaction you’re incorporating into your SLA and select “Response Time” as the Statistic to monitor. If you use the SLA itself, the transaction may not be visible in the SLA dashboard if there haven’t been any transaction failures. In that case, select the “Healthy Computers” check box to the left of the SLA detail diagram - the pie chart will be completely green, but each transaction will be listed with an average Response Time value, and an available detail graph displaying a timeline graph of the Response Time values.
by admin on
July 26, 2007
by admin on
July 17, 2007
by admin on
July 10, 2007