Richard Durso

Yeah! These look neat! Look forward to trying them.

ok, I'll check it out this weekend! Do you have any way to determine if request = limit then make it blue, otherwise use color scale like something I suggested?

I need to figure out this missing `image=` key. As-is, I get nothing. I'll have to re-work each gauge to remove that reference. 

*sigh* another issue, besides not having the `image=` do not have `container=` The `container_cpu_usage_seconds_total{namespace="mosquitto", pod="mosquitto-mqtt-0"}` yields: `container_cpu_usage_seconds_total{cpu="total", endpoint="https-metrics", id="/kubepods/burstable/podcc153a2a-d87e-4b18-b37b-159fa6907cd4", instance="k3s02", job="kubelet", metrics_path="/metrics/cadvisor", namespace="mosquitto", node="k3s02", pod="mosquitto-mqtt-0", service="prometheus-kubelet"}` Which returns an empty...

Nah... without the container level metrics I can't really test it properly.

Kicking around some other ideas and learned how to merge two metrics which share a common key. ``` "expr": "avg by (nodename) (instance:node_cpu:ratio * on(instance) group_left(nodename) node_uname_info)" ``` 

I think the "REAL" RAM usage is now including all kinds of cached memory as "used". Previous method is reporting 12.9GB RAM used, new method is reporting 39.8GB RAM used...

I think you have the memory right. Checked other tools like LENS and it lines right up. The CPU & Memory by namespace, Memory Utilization by node are dark as...

I still can't use your dashboards unmodified:  My networking metrics are looking good again. But I think my overrides are still in place... I've not been able to find...

I think the key difference is that I'm unable to run the `containerd` that is built into the `k3s` binary as I need to use the ZFS snapshotter. The containerd...