You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We recently started adding Prometheus metrics to ERDDAP™. The main goal of this project is to build an example Prometheus Server which can monitor one or more ERDDAP™ instances. This may involve adding new metrics to the ERDDAP™ project which is where Java would be used.
Expected Outcomes
A Prometheus Server configuration that is runnable through Docker and can be used to monitor one or more ERDDAP™ instances. This will help ERDDAP™ admin's monitor their servers and provide usage insight that can help guide future ERDDAP™ development.
I'm running a grafana monitoring stack for the MBON dashboard server. I've read about prometheus but haven't tried it. Could be a great solution for improved ERDDAP monitoring and reporting.
Is there an achitecture in mind for this? Will we have an erddap-monitoring module in the current repository or something like a new repository for everything related to monitoring?
And since this example server will be containerized and runnable through docker, we use the existing image for prometheus on docker hub or do we get the entire prometheus server binary and configure that to be run through docker?
Project Description
We recently started adding Prometheus metrics to ERDDAP™. The main goal of this project is to build an example Prometheus Server which can monitor one or more ERDDAP™ instances. This may involve adding new metrics to the ERDDAP™ project which is where Java would be used.
Expected Outcomes
A Prometheus Server configuration that is runnable through Docker and can be used to monitor one or more ERDDAP™ instances. This will help ERDDAP™ admin's monitor their servers and provide usage insight that can help guide future ERDDAP™ development.
Skills Required
Java, Prometheus, YML, Docker
Additional Background/Issues
The main ERDDAP™ repo is here.
Mentor(s)
Chris John (@ChrisJohnNOAA)
Expected Project Size
175 hours
Project Difficulty
Intermediate
The text was updated successfully, but these errors were encountered: