-
Notifications
You must be signed in to change notification settings - Fork 4
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
[Operations] How to better visualize OpenSearch-Project status? #65
Comments
I build a tool to generate badges off of https://shields.io/, called opensearch-build-badger through a GitHub action. Maybe this can be built-up to be part of our monitoring mechanisms. Here is a snippet of the output, see the project for a full visualization. Release Readiness
|
[Triage] @peternied Thanks you for this great idea. We will look in to adding this feature soon. |
Discussed this more with @anasalkouz we came up with a list of items that would be useful to add to project readme, then we can see about operationalizing the output. I'll play around with workflows that can accomplish this
|
Thanks @peternied. I am currently planning to use it for 2.4.0 release issue - [RELEASE] Release version 2.4.0 |
Adding more detailed badges generated with https://github.com/peternied/opensearch-build-badger - Related https://github.com/opensearch-project/opensearch-build/issues/2629 Signed-off-by: Peter Nied <[email protected]>
Adding more detailed badges generated with https://github.com/peternied/opensearch-build-badger - Related https://github.com/opensearch-project/opensearch-build/issues/2629 Signed-off-by: Peter Nied <[email protected]>
Adding more detailed badges generated with https://github.com/peternied/opensearch-build-badger - Related https://github.com/opensearch-project/opensearch-build/issues/2629 Signed-off-by: Peter Nied <[email protected]>
Adding more detailed badges generated with https://github.com/peternied/opensearch-build-badger - Related https://github.com/opensearch-project/opensearch-build/issues/2629 Signed-off-by: Peter Nied <[email protected]> Signed-off-by: Stephen Crawford <[email protected]>
Moving to opensearch-metrics repo under project health category. |
[Triage] Thank you |
Closing this issue, feel-free to re-open or create a new one for new metric (to better visualize the OpenSearch Project status) if required. |
Is your feature request related to a problem? Please describe
During the weekly operations meeting, there has been an ongoing question- how do we know if we are on track or not? Using release issues is focused on individual releases and there can be as many as 3 active release actions happening at once. Getting a good 'feel' for the project health doesn't have strong mechanisms
Describe the solution you'd like
There should be a place where the OpenSearch project can visualize projects and critical metrics about them. Number of stale issues/PRs. How many issues are untriaged. How many outstanding release specific issues are still unresolved.
Additional health metrics could include community engagement, incoming issue rate, or time since last release.
The text was updated successfully, but these errors were encountered: