helm-charts VS helm-charts

https://github.com/VictoriaMetrics/helm-charts/commit/128d2a7fa23c717e780655f03df83b03e3d637ac could be the reason

There is also victoriametrics-operator and victoriametrics k8s stack helm chart.

BTW, you can use victoria-metrics-k8s-stack as a drop-in replacement for kube-prometheus-stack.

It is possible to replace kube-prom-stack with VictoriaMetrics stack in every k8s cluster - see https://github.com/VictoriaMetrics/helm-charts/blob/master/charts/victoria-metrics-k8s-stack/README.md

I'm monitoring CPU, memory, disk, network usage etc, the basic stuff available from kubernetes metrics via api. I also have a sidecar pod to send CPU temperature via opentsdb endpoint of Victoria Metrics. I run this helm chart which has operator and db - it can be added to grafana as a Prometheus data source.

There is a k8s stack Helm Chart which can provide the same functionality. Also check VictoriaMetrics Operator docs and our guides .

For metrics there is VictoriaMetrics operator and helm chart, which can be used for monitoring Kubernetes. See this guide.

Prometheus can be deployed using the Prometheus Helm Chart. This helm chart contains a lot of features such as the already mentioned Push Gateway, Alert Manager and so on. For simplicity reasons of this tutorial I will not show all the Helm chart configuration but you can see a real example used by me here.

Building upon Bartłomiej Płotka's insightful blog on Prometheus and its passthrough agent mode, this post dives into implementing multi-cluster Prometheus support. Notably, the official inclusion of support in the widely-used kube-prometheus-stack came with the release in July 2023, making it easier to extend Prometheus monitoring across clusters.

The first thing you'll need, of course, is at least one backend to store metrics. So install Prometheus now:

For the request following, something like jeager https://www.jaegertracing.io/, because you are talking more about tracing than necessarily logging. For just monitoring, https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack would be the starting point, then it depends. Nginx gives metrics out of the box, then you can pull in the dashboard like https://grafana.com/grafana/dashboards/14314-kubernetes-nginx-ingress-controller-nextgen-devops-nirvana/ , or full metal with something like service mesh monitoring which would provably fulfil most of the requirements

kube-prometheus-stack is a Helm chart that contains several components to monitor the Kubernetes cluster, along with Grafana dashboards Grafana Dashboards to visualize the data. This option will be used in this article.

This one I highly recommend: https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack

We use kube-prometheus-stack for metrics and have added the K8s views dashboards from grafana-dashboards-kubernetes. You should check out the k8s-views-global dashboard. I believe it's just what you are looking for.

You should take a look at "kube-prometheus-stack". It not only includes prometheus, node-exporter and Grafana but also a ton of preconfigured alerts and dashboards. Will save you a lot of work!

Since their are different ways to install what exactly did you install? Vanilla charts , stack, operator? https://github.com/prometheus-community/helm-charts/tree/main/charts