Add a new functionality to Kangal to measure performance by some key metrics.
Problem:
Currently, Kangal doesn't have a way to estimate the performance of the service responding to the load. Probably all requests got 4** or latency was too high, etc. Users have to monitor logs and metrics of service under test to understand how it's behaving under load. Users can't see if the previous test run showed the better results than the next one.
Possible solution:
JMeter backend has a built-in functionality to generate the report showing some statistics. It can provide the following information:
average response time during the test
max response time during the test
% and the number of errors during the test
Max hits per second during the test
...
Examples of JMeter report graphs:
Kangal can read the key values from JMeter report and calculate some simple metrics based on this data. These metrics can be used as thresholds for the next runs to spot the degradation or improvement of performance.
Acceptance Criteria:
User can understand if the service was behaving well under load or not.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Goal
Add a new functionality to Kangal to measure performance by some key metrics.
Problem: Currently, Kangal doesn't have a way to estimate the performance of the service responding to the load. Probably all requests got 4** or latency was too high, etc. Users have to monitor logs and metrics of service under test to understand how it's behaving under load. Users can't see if the previous test run showed the better results than the next one.
Possible solution: JMeter backend has a built-in functionality to generate the report showing some statistics. It can provide the following information:
Examples of JMeter report graphs:
Kangal can read the key values from JMeter report and calculate some simple metrics based on this data. These metrics can be used as thresholds for the next runs to spot the degradation or improvement of performance.
Acceptance Criteria:
User can understand if the service was behaving well under load or not.