diff --git a/docs/managed_victoriametrics/how-to-monitor-k8s.md b/docs/managed-victoriametrics/how-to-monitor-k8s.md similarity index 97% rename from docs/managed_victoriametrics/how-to-monitor-k8s.md rename to docs/managed-victoriametrics/how-to-monitor-k8s.md index 85d14a62ef..15762f726b 100644 --- a/docs/managed_victoriametrics/how-to-monitor-k8s.md +++ b/docs/managed-victoriametrics/how-to-monitor-k8s.md @@ -26,7 +26,9 @@ Install the Helm chart in a custom namespace ``` kubectl create namespace monitoring ``` + 2. Create kubernetes-secrets with token to access your dbaas deployment + ``` kubectl --namespace monitoring create secret generic dbaas-write-access-token --from-literal=bearerToken=your-token @@ -34,8 +36,10 @@ kubectl --namespace monitoring create secret generic dbaas-read-access-token --f ``` > You can find your access token on the "Access" tab of your deployment -> ![access token](./k8s-monitoring-access-token.png) +

+ +

3. Set up a Helm repository using the following commands: ``` @@ -111,7 +115,10 @@ kubectl --namespace monitoring port-forward service/vm-grafana 3000:80 Choose VictoriaMetrics or Prometheus as datasource type. Make sure you made this datasource as default for dashboards to work. -![datasource](./k8s-monitoring-datasource.png) +

+ +

+ > You can find token and URL in your deployment, on access tab diff --git a/docs/managed_victoriametrics/k8s-monitoring-access-token.png b/docs/managed-victoriametrics/k8s-monitoring-access-token.png similarity index 100% rename from docs/managed_victoriametrics/k8s-monitoring-access-token.png rename to docs/managed-victoriametrics/k8s-monitoring-access-token.png diff --git a/docs/managed_victoriametrics/k8s-monitoring-datasource.png b/docs/managed-victoriametrics/k8s-monitoring-datasource.png similarity index 100% rename from docs/managed_victoriametrics/k8s-monitoring-datasource.png rename to docs/managed-victoriametrics/k8s-monitoring-datasource.png