[QUESTION] Raspberry Pi Dockers Monitor error

[ramsrq]

Question I got an error in Grafana Raspberry Pi Dockers Monitor with charts "CPU Busy" and "Disk IO"

Context I just install the stack RaspberryPi-Docker-Monitor in a RPi 4 with: pi@raspberrypi:~ $ cat /etc/os-release PRETTY_NAME="Raspbian GNU/Linux 10 (buster)" NAME="Raspbian GNU/Linux" VERSION_ID="10" VERSION="10 (buster)" VERSION_CODENAME=buster ID=raspbian ID_LIKE=debian HOME_URL="http://www.raspbian.org/" SUPPORT_URL="http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

After follow all steps documented on https://github.com/pi-hosted/pi-hosted/blob/master/docs/rpi_docker_monitor.md in Grafana dashboard a got an error in "CPU Busy" and "Disk IO" charts:

bad_data: 1:38: parse error: not a valid duration string: "2.147483647s"

Is it possible to correct it?

[DavideVairetti]

Installed now and I have the same error.

Edit: The problem is in the string $__rate_interval. I temporaly set the range to calculate rate() function as $__interval instead using $__rate_interval but I can't optimize the monitor of CPU and I/O Disk in this way. You can read this docs to have a better idea. (https://grafana.com/blog/2020/09/28/new-in-grafana-7.2-__rate_interval-for-prometheus-rate-queries-that-just-work/)

Hope someone can help us to find a better solution.

[Bluesguy1984]

Installed now and I have the same error.

Edit: The problem is in the string $__rate_interval. I temporaly set the range to calculate rate() fonction as $__interval instead using $__rate_interval but I cin this way an't optimize the monitor of CPU and I/O Disk. You can read this docs to have a better idea. (https://grafana.com/blog/2020/09/28/new-in-grafana-7.2-__rate_interval-for-prometheus-rate-queries-that-just-work/)

I am getting the same error. Where did you make the change? What file?

[DavideVairetti]

Installed now and I have the same error. Edit: The problem is in the string $__rate_interval. I temporaly set the range to calculate rate() fonction as $__interval instead using $__rate_interval but I cin this way an't optimize the monitor of CPU and I/O Disk. You can read this docs to have a better idea. (https://grafana.com/blog/2020/09/28/new-in-grafana-7.2-__rate_interval-for-prometheus-rate-queries-that-just-work/)

I am getting the same error. Where did you make the change? What file?

You need to modify it in the query. Clink on the box title (like CPU busy), go in to the edit menu and you can find the query that the monitor use to get the data from database.

[ramsrq]

Thanks @davide-v15 I'll try this workaround Edit: I change the variable from $__rate_interval to $__interval and work for me.

[Colcobau]

Installed now and I have the same error. Edit: The problem is in the string $__rate_interval. I temporaly set the range to calculate rate() fonction as $__interval instead using $__rate_interval but I cin this way an't optimize the monitor of CPU and I/O Disk. You can read this docs to have a better idea. (https://grafana.com/blog/2020/09/28/new-in-grafana-7.2-__rate_interval-for-prometheus-rate-queries-that-just-work/)

I am getting the same error. Where did you make the change? What file?

You need to modify it in the query. Clink on the box title (like CPU busy), go in to the edit menu and you can find the query that the monitor use to get the data from database.

Thank you! Was having the exact same issue, modified the query and works like a charm. Star!

[Macleykun]

Thanks @davide-v15 I'll try this workaround Edit: I change the variable from $__rate_interval to $__interval and work for me.

ya can close this issue :)

[Macleykun]

This isssue can be closed @ramsrq