this is an incremental improvement of the readability of the concourse
dashboard, focusing on showing only what matters, while still making
periods configurable.
the theory behind this change is that we're usually looking to what the
"highest" of something is (rather than all of it), and in some cases, a
rate (/s) is too awkward to reason about (thus, getting rates over
longer periods of time).
ps.: both changes mentioned above are not hardcoded - a viewer can
change those values anytime.
having a 30GB for the Prometheus server is something that made sense
back then when we had very few machines and services running on the
hush-house cluster, but nowadays, that is not enough, thus, here we
bump from 30GB to 300GB.
aside from the disk bump, now we're being more careful with which
metrics we consume, more specifically:
discarding metrics from all those containers that cadvisor knows about
but that we don't care
removing the whole capturing of labels that we used to do
this is an incremental improvement of the readability of the
concourse
dashboard, focusing on showing only what matters, while still making periods configurable.the theory behind this change is that we're usually looking to what the "highest" of something is (rather than all of it), and in some cases, a rate (/s) is too awkward to reason about (thus, getting rates over longer periods of time).
ps.: both changes mentioned above are not hardcoded - a viewer can change those values anytime.
having a 30GB for the Prometheus server is something that made sense back then when we had very few machines and services running on the
hush-house
cluster, but nowadays, that is not enough, thus, here we bump from 30GB to 300GB.aside from the disk bump, now we're being more careful with which metrics we consume, more specifically:
now we also have a fancier build vis
(more info in the commits themselves)