Back in April/May I proposed how we set up a metrics CI for Kata.
I have (finally!) gotten to boot (job here) a slave on our cloud system to start providing footprint/density data, and am about to deploy bare metal over on packet.net for further time/noise sensitive tests.
That allows us to take the next step, using the JSON DB hook to store historical data, allowing further long term analysis and tracking, and attaching a UI.
I've mocked this up locally before, and used elasticsearch for the DB and Kibana for the viewer (here is an example:
)
What I'd like to do now is source and agree some space to run up elastic and kibana so we can start gathering the historical data and bring up the UI.
My initial thought is that we can utilise the same cloud resource we use for the Jenkins master machine. We don't need time critical stuff here, but will need:
- 24/7 instances (so the results can be stored when the PRs run, and the GUI invoked at any time)
- probably not lots of RAM
- over time we may need disk space for the DB
@mnaser @cboylan would you be able to resource us for that?
And, if there is anybody out there with elastic or kibana experience, especially around any aspects of security and how we might set up account/login verification (ideally against github like we do with Jenkins), that would be great :-)
Back in April/May I proposed how we set up a metrics CI for Kata.
I have (finally!) gotten to boot (job here) a slave on our cloud system to start providing footprint/density data, and am about to deploy bare metal over on packet.net for further time/noise sensitive tests.
That allows us to take the next step, using the JSON DB hook to store historical data, allowing further long term analysis and tracking, and attaching a UI.
I've mocked this up locally before, and used elasticsearch for the DB and Kibana for the viewer (here is an example:
)
What I'd like to do now is source and agree some space to run up elastic and kibana so we can start gathering the historical data and bring up the UI.
My initial thought is that we can utilise the same cloud resource we use for the Jenkins master machine. We don't need time critical stuff here, but will need:
@mnaser @cboylan would you be able to resource us for that?
And, if there is anybody out there with elastic or kibana experience, especially around any aspects of security and how we might set up account/login verification (ideally against github like we do with Jenkins), that would be great :-)