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.
Description
Adds default monitoring graphs to the KOTS Graphs section of the app config. This allows users to connect to their own Prometheus instance and for the Gitpod instance to give out simple graphs. The graphs are based upon the published graphs in our monitoring docs.
NB we have limited (documented) control over the Y axis, so we end up with negative time periods by default. My feeling is that this is a convenience inside the KOTS dashboard and that, ultimately, most people will use Grafana over this. However, this should remain as a convenience for those who want a limited monitoring solution over a full-blown Grafana instance.
How to test
Install a Prometheus instance to your cluster and set the
As a convenience, my monitoring repo is already set up - the URL is
http://monitoring-prometheus-prometheus.gitpod.svc.cluster.local:9090
Release Notes
Documentation
Werft options: