Monitoring and alerts #199
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
NathanCummings
approved these changes
Nov 27, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds two data scrapers (Node_exporter for hardware, cadvisor for docker containers) to monitor the vm. Then adds prometheus to collate this information and pass to grafana where it is graphed in dashboards. Grafana also has alerts setup to inform us if either the api container or pgadmin goes down for more than 3 mins and if the vm is using more than 95% of either its RAM or cpu for over 5 mins.
Note if testing this locally: in the docker-compose file the enviromental variable GF_SERVER_ROOT_URL must be commented out for grafana
Additionally the provisioned contact point for the alerting is a dummy url and in production will need to be changed manually.