Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kangal can use JMeter report to measure performance of the service under test #187

Open
s-radyuk opened this issue Feb 16, 2022 · 1 comment
Labels
enhancement New feature or request pinned issues that should be kept open

Comments

@s-radyuk
Copy link
Contributor

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:

  • 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:
Screenshot 2022-02-16 at 16 24 22
Screenshot 2022-02-16 at 16 23 57

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.

@lucasmdrs lucasmdrs added the enhancement New feature or request label Feb 16, 2022
@stale
Copy link

stale bot commented Mar 30, 2022

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.

@stale stale bot added the stale label Mar 30, 2022
@lucasmdrs lucasmdrs added the pinned issues that should be kept open label Mar 30, 2022
@stale stale bot removed the stale label Mar 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request pinned issues that should be kept open
Projects
None yet
Development

No branches or pull requests

2 participants