On Sun, Jun 28, 2020 at 01:01:31AM +0100, David Kirwan wrote:
Hmm the (prometheus, grafana, alertmanager) stack itself is pretty simple I
would have said, but I agree it is certainly complex when
installed/integrated on Openshift.. (most things are needlessly complex on
Openshift tbh, and its an order of magnitude worse on Openshift 4 with
these operators added to the mix).
Well, they may not be that complex... like I said, I haven't used them
much, so I might be missing how they work.
It would be the obvious choice for me anyway considering this stack
available by default on a fresh Openshift install. We could make use of
this cluster monitoring stack, especially if we're also deploying our
services on Openshift. I might throw a POC/demo together to show how "easy"
it is to get your app hooked into the Openshift cluster monitoring stack,
or the UserWorkload tech preview monitoring stack.
I agree it makes sense to use this for openshift apps.
I am not sure at all we should use it for non openshift apps.
If we did use this stack it would add a little extra pain with
monitoring storage maintenance/pruning. But maybe far less than
running/maintaining a whole separate monitoring stack outside the Openshift
cluster. There are also efficiencies to be made when developers are already
in the Openshift/Kubernetes mindset, creating an extra Service and
ServiceMonitor is a minor thing etc.
Sure, but we have a lot of legacy stuff we want to monitor/review logs
The right answer might be to just seperate those two use cases with
different solutions, but then we have 2 things to maintain.
It's probibly going to take some investigation and some proof of concept