Steps to reproduce:

1. i am using DB EC2 instaces template for os mem ,cpu and partition alert monitoring. it is working properly if the partition is in GB . if the any partition is in tb and its utilisation goes above 90% it's alert not displaying on dashboard.

by default {$VFS.FS.PUSED.MAX.CRIT} is 90 . and {$VFS.FS.FREE.MIN.CRIT} 5G.

Operational data  

Space used: {ITEM.LASTVALUE3} of {ITEM.LASTVALUE2} ({ITEM.LASTVALUE1})

Expression

last(/DB EC2 INSTANCES/vfs.fs.size[\{#FSNAME},pused])>\{$VFS.FS.PUSED.MAX.CRIT:"{#FSNAME}"} and
((last(/DB EC2 INSTANCES/vfs.fs.size[\{#FSNAME},total])-last(/DB EC2 INSTANCES/vfs.fs.size[\{#FSNAME},used]))<\{$VFS.FS.FREE.MIN.CRIT:"{#FSNAME}"} or timeleft(/DB EC2 INSTANCES/vfs.fs.size[\{#FSNAME},pused],1h,100)<1d)

i have tried below changes it is giving fake alert for GB size partition but showing alert properly for TB size partitions

operational data

Space used: ({ITEM.LASTVALUE3}) of ({ITEM.LASTVALUE2}) ({ITEM.LASTVALUE1})

Expression

last(/DB EC2 INSTANCES/vfs.fs.size[\{#FSNAME},pused])>\{$VFS.FS.PUSED.MAX.CRIT:"{#FSNAME}"} or
((last(/DB EC2 INSTANCES/vfs.fs.size[\{#FSNAME},total])-last(/DB EC2 INSTANCES/vfs.fs.size[\{#FSNAME},used]))<\{$VFS.FS.FREE.MIN.CRIT:"{#FSNAME}"} and timeleft(/DB EC2 INSTANCES/vfs.fs.size[\{#FSNAME},pused],1h,100)<1d)

please suggest if any other changes required IN trigger prototype option?