adoptium / adoptium/aqa-test-tools

[Discussion] Consider add Grafana based dashboard for test and release status

Open
#680 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Jupyter Notebook
Stars
33
Forks
97
Avg merge
7h 9m
Merged PRs (30d)
5

Description

Hi, https://trss.adoptium.net/dashboard showed how to monitor performance histories, but we need to maintain a webpage jsx for every single perf test, which might get heavy as we continue adding those tests.

And I notice [grafana](https://grafana.com/) could easily set up multiple dashboards from datasource for free, so might worth considering add this to TRSS.

Hopefully we could discuss this, and I setup a [minimal-demo](http://8.218.3.188:3000/d/O84bTLC7z/frameworkbenchmarks-spring-json-totalrequests?orgId=1&from=0&to=0&viewPanel=4) for FrameworkBenchmarks, with a [server](https://github.com/joeyleeeeeee97/FrameworkBenchmarksWithGrafana) that converts results to database.

The upside on this is:
- No need to maintain multiple web pages, instead we setup easily with sqls.
- More demonstration formats, bars, timelines...
- We could share them with links, with customized permissions, or private dashboards.

The downside is:
- Mongodb datasource is only working with enterprise product, so I am using influxdb for the demo. So if use grafana we need to pay for enterprise or add a influxdb database to coexist with mongodb.

Overall personally I think we should consider doing this, as we are certainly getting more tests and results to show.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the existing TRSS performance dashboard and the linked FrameworkBenchmarksWithGrafana demo, then compare their data-source assumptions with TRSS's MongoDB setup. Done would require an agreed implementation scope and data-source decision for test and release dashboards; this discussion identifies no files or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
grafana, mongodb
Domain
observability
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.