Open javaducky opened 2 years ago
Ideally, if possible, we should centralize the visualization and inject the data source's queries. In this way, keeping the extensions synced would be easier. In this way, we could define the Grafana dashboard in one centralized repository and reference it from the extensions defining how to resolve the data source and the relative queries.
I don't know if Grafana supports this use case, maybe could we do it by setting a data source variable?
Not sure if there is another location for the "official" dashboards, but ultimately being available to the community from this central repository would be nice.
Hello! I was trying to implement k6 in my company as the standard for Load Testing, however, from all the dashboards that showed up under k6, none was working out of the box. I have the default one working, however, it would be truly amazing if it could be improved! I am not very well versed in the Flux language syntax, so it would help out a lot! Thanks
Improve upon the currently provided dashboards (
grafana/dashboards/
).Another goal for this change would be to align the look-and-feel for the Influx-backed dashboard (this extension), the xk6-output-prometheus-remote, and xk6-output-timescaledb possibly with the output provided by the k6 Cloud App. This would provide a consistent user experience for the varied data sources.
Ideally, this dashboard would be promoted to the Grafana site as the "official" dashboard for displaying k6 metrics backed by InfluxDB datasources.