Configuring Service Threshold

If the duration of the transaction exceeds a certain threshold, the transaction will be flagged as slow. The decision is made by comparing the threshold set for a particular service to the actual time of completing a transaction. If the transaction completion took longer than the predetermined threshold, the transaction is flagged as slow. By default, Plumbr sets a 5,000ms threshold for all the services detected. You can change the default threshold via Settings – Thresholds menu.

Having a single threshold for all services can trigger false alarms or missing information as services exposed by a JVM can have different requirements in regards of performance. For example, an application might expose services for which the latency requirements are strict and require transactions to complete under 1,000ms. On the other hand, there can be services for which the latency is more relaxed and response times of several minutes can be considered tolerable.

Service-based thresholds allow setting the threshold per individual service. Specifying the threshold for individual services will override the generic threshold. Setting the specific threshold for a service is accessible after opening a particular service in question. In the Impact view, you get exposure to the current behavior of the service in terms of latency distribution. In the very same view you can change the threshold for this particular service.