You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
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.
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.
The text was updated successfully, but these errors were encountered: