Observability
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
* gradually we are getting to the place where we have many processes running in various ways / locations
* for example:
* [snowpack analysis - github action](https://github.com/bcgov/nr-rfc-processing)
* [cmc grib - github actions](https://github.com/bcgov/nr-rfc-grib-copy)
* cmc grib - listener - openshift (same repo but in the backend folder)
* [Demo of soil moisture - github action](https://github.com/bcgov/nr-rfc-reanalysis)
* [climate observations - in progress](https://github.com/bcgov/nr-rfc-climate-obs/actions)
* [discharge observations - in progress](https://github.com/bcgov/nr-rfc-dischargeobs)
* [snowpack frontend - openshift](https://github.com/bcgov/nr-rfc-snowfrontend)
This ticket would create an application status dashboard that allows us to quickly view what's working and what's not. Could tie in with "One Teams" observability stack.
Contributor guide
No contributing guide indexed for this repository
Research direction
Review the listed GitHub Actions workflows, the CMC GRIB listener in the backend folder, and the OpenShift-hosted snowpack frontend to inventory the processes and their status signals. Clarify how this should integrate with the One Teams observability stack. Done means an application status dashboard provides a quick view of which listed processes are working and which are not.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100