I believe I found a bug in the low level discovery.

I am using a custom vfs.fs.discovery that will return the following on each server:

{#FSNAME} - name of the filesystem {#FSTYPE} - type of filesystem {#FSTRIGGER} - value in % that trigger will alert. This value will be pulled in from a file stored locally on a server or return a default. ie 90

...
{
"{#FSNAME}

":"\/",
"

{#FSTYPE}

":"ext4",
"

{#FSTRIGGER}":"90"
}
...

So for each filesystem, I will be able to modify what % the trigger gets set off at.

This is what I want my trigger to look like:
{Template_OS_Linux:vfs.fs.size[{#FSNAME},pused].last(0)}>{#FSTRIGGER}

However, after saving I get:
ERROR: Cannot update trigger

• Array

I receive the error when I try to save the new trigger. The error appears in the web frontend at the top where errors and details normally appear.

Also, I know the

{#FSTRIGGER}

works because I am able to use the macro in the item description.