Create a trigger for files bigger than "x" MB

[Fabrizio We BiNar]

yes, all of these files are located in c:\test\dicom, no subdirectories.

[Semiadmin]

Then I don't know how you get 0, sorry

[Fabrizio We BiNar]

If I can get the item to return "1", you think that the trigger code is fine for my purpose?

[z0nk]

How can I make vfs.dir.size return output in MB or GB, not Bytes?

[ISiroshtan]

If you want it to be translated on graphs and overview in latest data - just add unit type for item as "B"
If you want it to be stored in DB and shown in latest data actual values view (rarely needed) - preprocessing with custom multiplier of 0.0009765625. 1 step of this preprocessing for KB, 2 times for MB, 3 times for GB

[z0nk]

ISiroshtan, thanks. The problem was I didn't declare 'b' in Unit, then it started calculating MB/GB/TB etc regarding to size

[jurgen16]

You can use this kind of key if you want to receive an alarm but this case works if normally you don't have files with size more than 260 MB.
And this will create an alarm everytime that you will have one or more file with size more than 260 MB.

Item key: vfs.dir.count[C:\test\dicom,,,,,,260000000,,,,]
Alarm exxpression: last(vfs.dir.count[C:\test\dicom,,,,,,260000000,,,,])=0