v3.5 Monitoring API

Introduction

Mongoose computes the rich set of the metrics characterizing each load step been performed. It means that the tool may work as a metrics providing service which may be used to build other applications on top of it. The metrics consumer may be a Mongoose-specific UI application either a monitoring infrastructure system.

Requirements

TODO

Limitations

Approach

• JMX used as a metrics service mechanism
• Test step id may be used as a custom metadata

Configuration

1. To enable the remote monitoring add the following JVM arguments to the command line:

   -Dcom.sun.management.jmxremote
   -Dcom.sun.management.jmxremote.port=9010
   -Dcom.sun.management.jmxremote.local.only=false
   -Dcom.sun.management.jmxremote.authenticate=false
   -Dcom.sun.management.jmxremote.ssl=false

Reporting

• JMX bean domain name: com.emc.mongoose.load.monitor
• JMX bean name: test step id
• JMX bean attributes: see below

Attributes reflect the current metric values for each test step:

1. ByteCount
2. ByteRateLast
3. ByteRateMean
4. DurationHiQ
5. DurationLoQ
6. DurationMax
7. DurationMean
8. DurationMed
9. DurationMin
10. DurationSum
11. ElapsedTimeMillis
12. FailCount
13. FailRateLast
14. FailRateMean
15. LatencyHiQ
16. LatencyLoQ
17. LatencyMax
18. LatencyMean
19. LatencyMed
20. LatencyMin
21. LatencySum
22. StartTimeMillis
23. SuccCount
24. SuccRateLast
25. SuccRateMean

Note:

Attributes with names ending with "Millis" provide the time values measured in milliseconds. Other attributes providing the time values (DurationXXX and LatencyXXX) are in microseconds.

Example: monitoring the metrics using VisualVM application for the test step with id "step0":

Standard Output

TODO

Log Files

TODO