mikaku
commented
11 years ago You're right. After applying the ability to monitor infinite filesystem groups in a previous version, I forgot to name correctly the .png files as fsn[123].1day.png where n means the group number of the filesystem graph (0, 1, 2, ...), and 1, or 2 or 3 are the numbers of the graphs.
So, after applying the fix, to get the first graph (titled as Filesystem usage) in the first group (0) you'll need to use the graph name fs01, for the second graph (titled as Disk I/O activity) of the same group you'll need to use the graph name fs02, and so on.
Following your example, the new correctly URLs would be:
This will be effective in the next 3.2.0 version. Many thanks!
I set up two file system groups to monitor. I then wanted to monitor the FS usage for my second group in a similar manner to how the multi-host web page is put together, i.e. using iframes. However, the results produced by the expected urls are not consistent. For instance something like
http://myhost:88/monitorix-cgi/monitorix.cgi?mode=localhost&when=1day&graph=_fs1&color=black&silent=imagetag
will produce the expected FS usage graph for the first group. However, something like
http://myhost:88/monitorix-cgi/monitorix.cgi?mode=localhost&when=1day&graph=_fs2&color=black&silent=imagetag
produces a page with the expected disk I/O activity for the first group, but also the filesystem usage for my second group (see attached image). The group numbers here are 0 and 1.