This is more a Kubernetes question. Maybe read this blog post first . Also remember that Prometheus is not a database. It's a monitoring system that happens to have a built-in time-series database for its function of monitoring the health of your systems. Imagine Nagios, but instead of "checks" it uses math. More on reddit.com

I believe this one is referred in the discuss.istio thread https://github.com/istio/istio/blob/master/samples/addons/extras/prometheus-operator.yaml More on reddit.com

We just did this a couple months ago, also from ~0.38. Read through the release notes and there were 1-2 breaking changes noted with fixes noted More on reddit.com

I think everyone else has covered the logs question, and the fact that you can use labels to group your metrics by customer. I think the only thing I'd point out here is something that u/krysinello points out as well. With the setups described here you will only get infrastructure level metrics, relating to your pods, nodes and overall cluster. You will not see anything relating to your actual microservices and customer experience unless you generate suitable metrics and expose them. This most likely means instrumenting your code. There's client librarie s in most languages that make this possible and are reasonably straight forward. If you're using a particular framework it's quite possible there's a prometheus instrumentor for that framework, e.g fastapi has the prometheus-fastapi-instrumentor . There's also open source frameworks that can help you do this in a variety of languages, my personal favourite is autometrics . Good luck with it! Implementing monitoring is an always evolving task that will never be finished. Even those of us with years of experience are still learning. There's not really a 'right' or 'wrong' either so don't be scared to experiment to see what works best for you. More on reddit.com