Issues with "victoria-metrics-k8s-stack", monitoring k8s targets

This page summarizes the projects mentioned and recommended in the original post on

Our great sponsors
  • InfluxDB - Access the most powerful time series database as a service
  • ONLYOFFICE ONLYOFFICE Docs — document collaboration in your environment
  • SonarQube - Static code analysis for 29 languages.
  • CodiumAI - TestGPT | Generating meaningful tests for busy devs
  • helm-charts

    Helm charts for VictoriaMetrics (by VictoriaMetrics)

    I understand there's a "hack" folder with a Python script which provisions the many json files for the dashboards into Grafana (using the sidecar?), but IDK how/where to run it or if it was "missed" during the Helm install...?

  • kube-prometheus

    Use Prometheus to monitor Kubernetes and applications running on Kubernetes

    - I'm missing a lot of the Grafana dashboards that are provisioned during the deployment, not sure why as it has worked before, and wanted to add them after install... I believe it's different ConfigMaps like the one in kube-prometheus but I was wondering if there's a way to force provisioning them all again at once (multiple k8s, node_exporter, vm, etc)?

  • InfluxDB

    Access the most powerful time series database as a service. Ingest, store, & analyze all types of time series data in a fully-managed, purpose-built database. Keep data forever with low-cost storage and superior data compression.

  • local-path-provisioner

    Dynamically provisioning persistent local storage with Kubernetes

    It is better to use (or similar) for this case which will do PVC on local directories because manually linking PV<>PVC will not work.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts