Ricardo F.

Results 34 comments of Ricardo F.

The values of ZFS [has changed completely](https://github.com/prometheus/node_exporter/issues/2068) since the migration to OpenZFS. A particular dashboard fits better to cover all their vast details, in FreeBSD and Linux implementations.

A few ZFS dashboards are available on [https://grafana.com/grafana/dashboards/](https://grafana.com/grafana/dashboards/), maybe you could take one of them an modify to fit your needs.

Hi Futatuki, Restarting via system only produces one line on the log: `2024-05-15T12:15:14.865994+02:00 servername opendkim[3413459]: OpenDKIM Filter v2.11.0 starting (args: -x /etc/opendkim/opendkim.conf)` Executing the same instruction via strace, doesn't report...

Thank you for reaching out regarding your experiment. After considering the proposal, I would prefer not to have interventions applied to the repositories at this time. I appreciate your understanding.

Hi Christian, I'd prefer to keep the Y-axis scaled to a fixed 100%. The reason is consistency: it's much easier to compare free disk space across different systems and over...

I just updated the grafana.com revision (41). Sorry for the delay.

Hi, Could you give it a try with these formulas?: Rx in: ``` 100 * rate(node_network_receive_bytes_total{instance="$node", job="$job"}[$__rate_interval]) / on(instance, device) (node_network_speed_bytes{instance="$node", job="$job"} > 0) ``` Tx out: ``` 100 *...

I apologize, but I’m unable to reproduce and verify the issue from my side.

Hi Darnone: You can define dashboards outside of values.yaml, mount them as ConfigMaps, and reference them using: ``` grafana: dashboardsConfigMaps: - my-dashboard-configmap ``` And create the ConfigMap separately: ``` kubectl...

Hi @septatrix, Each of us has different requirements, so please use the dashboard as a starting point and adapt it to your environment. Thanks,