Ad Widget

Collapse

About data representations

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • mahmood
    Junior Member
    • Mar 2020
    • 24

    #1

    About data representations

    What I see on the report page seems to be wrong!
    As you can see the disk usage is said to be >80% and >90%
    Click image for larger version

Name:	Untitled.png
Views:	156
Size:	47.3 KB
ID:	396878

    But in the graph, I see everything to be normal.

    Click image for larger version

Name:	Untitled.png
Views:	141
Size:	33.4 KB
ID:	396879

    In fact, when I run "df -h", the disk usage is fine.

    Code:
    # df -h
    Filesystem      Size  Used Avail Use% Mounted on
    udev            1.9G     0  1.9G   0% /dev
    tmpfs           393M  1.6M  391M   1% /run
    /dev/sda2       196G   11G  175G   6% /
    tmpfs           2.0G     0  2.0G   0% /dev/shm
    tmpfs           5.0M     0  5.0M   0% /run/lock
    tmpfs           2.0G     0  2.0G   0% /sys/fs/cgroup
    /dev/loop0       87M   87M     0 100% /snap/core/4917
    tmpfs           393M     0  393M   0% /run/user/1000
    /dev/loop1       92M   92M     0 100% /snap/core/8689
    tmpfs           393M     0  393M   0% /run/user/1002
  • tim.mooney
    Senior Member
    • Dec 2012
    • 1427

    #2
    I don't use the template you appear to be using, but I think you're mis-reading what the report is saying.

    In the availability report you show, the "OK" column with 100% means that the trigger has not evaluated to a problem condition at any time during the reporting timeframe. The "/: Disk space is low (>80% used)" is only true when the trigger evaluates to a problem. As long as "OK" shows "100%", it means none of the configured triggers have detected any problems.

    Comment

    Working...