K3s monitoring with default Observability->Kubernetes->Workloads

Grafana Cloud
, ,
1

Hi,

I’m new here, and I’ve a k3s kubernetes cluster, i’ve enabled on grafana cloud the Observability→Kubernetes, I’ve installed successfully the chart with the values, but plenty of data is totally missing on grafana cloud if i enter to a workload, all cpu and ram metrics are not there, is supported k3s?

helm upgrade --install --timeout 300s grafana-k8s-monitoring grafana/k8s-monitoring --namespace “monitoring” --create-namespace --values values.yaml

cluster:
name: my-cluster
destinations:

  • name: grafana-cloud-metrics
    type: prometheus
    url: https://prometheus-prod-58-prod-eu-central-0.grafana.net./api/prom/push
    auth:
    type: basic
    username: “2808467”
    password: …
  • name: grafana-cloud-logs
    type: loki
    url: https://logs-prod-039.grafana.net./loki/api/v1/push
    auth:
    type: basic
    username: “1399911”
    password: …
    clusterMetrics:
    enabled: true
    annotationAutodiscovery:
    enabled: true
    clusterEvents:
    enabled: true
    nodeLogs:
    enabled: true
    podLogs:
    enabled: true
    kubelet:
    enabled: true
    cadvisor:
    enabled: true
    alloy-metrics:
    enabled: true
    alloy:
    extraEnv:
    • name: GCLOUD_RW_API_KEY
      valueFrom:
      secretKeyRef:
      name: alloy-metrics-remote-cfg-grafana-k8s-monitoring
      key: password
    • name: CLUSTER_NAME
      value: my-cluster
    • name: NAMESPACE
      valueFrom:
      fieldRef:
      fieldPath: metadata.namespace
    • name: POD_NAME
      valueFrom:
      fieldRef:
      fieldPath: metadata.name
    • name: GCLOUD_FM_COLLECTOR_ID
      value: grafana-k8s-monitoring-$(CLUSTER_NAME)-$(NAMESPACE)-$(POD_NAME)
      remoteConfig:
      enabled: true
      url:
      auth:
      type: basic
      username: “1442117”
      password: …
      alloy-singleton:
      enabled: true
      alloy:
      extraEnv:
    • name: GCLOUD_RW_API_KEY
      valueFrom:
      secretKeyRef:
      name: alloy-singleton-remote-cfg-grafana-k8s-monitoring
      key: password
    • name: CLUSTER_NAME
      value: my-cluster
    • name: NAMESPACE
      valueFrom:
      fieldRef:
      fieldPath: metadata.namespace
    • name: POD_NAME
      valueFrom:
      fieldRef:
      fieldPath: metadata.name
    • name: GCLOUD_FM_COLLECTOR_ID
      value: grafana-k8s-monitoring-$(CLUSTER_NAME)-$(NAMESPACE)-$(POD_NAME)
      remoteConfig:
      enabled: true
      url:
      auth:
      type: basic
      username: “1442117”
      password: …
      alloy-logs:
      enabled: true
      alloy:
      extraEnv:
    • name: GCLOUD_RW_API_KEY
      valueFrom:
      secretKeyRef:
      name: alloy-logs-remote-cfg-grafana-k8s-monitoring
      key: password
    • name: CLUSTER_NAME
      value: my-cluster
    • name: NAMESPACE
      valueFrom:
      fieldRef:
      fieldPath: metadata.namespace
    • name: POD_NAME
      valueFrom:
      fieldRef:
      fieldPath: metadata.name
    • name: NODE_NAME
      valueFrom:
      fieldRef:
      fieldPath: spec.nodeName
    • name: GCLOUD_FM_COLLECTOR_ID
      value: grafana-k8s-monitoring-$(CLUSTER_NAME)-$(NAMESPACE)-alloy-logs-$(NODE_NAME)
      remoteConfig:
      enabled: true
      url:
      auth:
      type: basic
      username: “1442117”
      password: …
2

The values file seems pretty standard.

Are the missing CPU and Memory metrics related to the nodes or to the pods? Node metrics comes from Node Exporter, while pod resource metrics come from kubelet and cadvisor.

Can you list a specific metric that is missing and I can help with the next troubleshooting step.