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

k6 future functions #83

Open
z1054136399 opened this issue Nov 21, 2024 · 1 comment
Open

k6 future functions #83

z1054136399 opened this issue Nov 21, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@z1054136399
Copy link

I hope K6 can add real-time monitoring and dashboard export functions, which can view dashboard data based on test ID instead of time, and then make the data persistently stored.

@av av added the enhancement New feature or request label Nov 24, 2024
@av
Copy link
Owner

av commented Nov 24, 2024

Hi 👋🏻

Thanks for the suggestion!

real-time monitoring

Indeed, the current k6 setup is designed more around one-off performance tests, but I understand the desire for continuous monitoring. Is it more about uptime or more about continuous performance monitoring?

For uptime, we might integrate Kuma into Harbor:
image

For continuous performance monitoring - also possible, but the solution would have to be much more comprehensive and custom. It's something that is typically built by larger companies on-prem tied to their tools and tech, I'm curious to learn more about the use-case in your instance.

dashboard export functions, which can view dashboard data based on test ID instead of time, and then make the data persistently stored.

After some research - I don't see any quick options to do export dashboards with self-hosted grafana, but I might be missing something. Viewing based on test ID/etc - can be done by creating another Grafana dashboard that'll query the data collected by k6 in a different way. It's unlikely I'll have time to configure these in such way any time soon.
Persistence can be enabled by adjusting the k6.compose.yml, but it's not enabled out of the box to avoid a case with a storage that grows indefinitely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants