I'm trying to create a trigger which will be used for an image item in a map to indicate that there is a problem with one or more of a group of ~10 servers. This involves creating a trigger with around 30 expressions, linked with an OR. I've found I'm able to enter the expression as:
{server01:icmppingsec[,,,,,].last(0)}=0 | {server01:ssh.last(0)}=0 | {server01:ssh.run[load01,,,].last(0)}>10 |
{server02:icmppingsec[,,,,,].last(0)}=0 | {server02:ssh.last(0)}=0 | {server02:ssh.run[load01,,,].last(0)}>10 |
{server03:icmppingsec[,,,,,].last(0)}=0 | {server03:ssh.last(0)}=0 | {server03:ssh.run[load01,,,].last(0)}>10 |
{server04:icmppingsec[,,,,,].last(0)}=0 | {server04:ssh.last(0)}=0 | {server04:ssh.run[load01,,,].last(0)}>10 |
{server05:icmppingsec[,,,,,].last(0)}=0 | {server05:ssh.last(0)}=0 | {server05:ssh.run[load01,,,].last(0)}>10 |
{server06:icmppingsec[,,,,,].last(0)}=0 | {server06:ssh.last(0)}=0 | {server06:ssh.run[load01,,,].last(0)}>10 |
{server07:icmppingsec[,,,,,].last(0)}=0 | {server07:ssh.last(0)}=0 | {server07:ssh.run[load01,,,].last(0)}>10 |
{server08:icmppingsec[,,,,,].last(0)}=0 | {server08:ssh.last(0)}=0 | {server08:ssh.run[load01,,,].last(0)}>10 |
{server09:icmppingsec[,,,,,].last(0)}=0 | {server09:ssh.last(0)}=0 | {server09:ssh.run[load01,,,].last(0)}>10 |
{server10:icmppingsec[,,,,,].last(0)}=0 | {server10:ssh.last(0)}=0 | {server10:ssh.run[load01,,,].last(0)}>10
and then click 'Toggle input method' and the expressions show up correctly, lettered A-^. However when I save the trigger and go back to look, unly A-U have been saved, a total of 20 expressions. Is there a hard limit on the number of expressions in a trigger, and if so, anyone know where it could be modified in code?
{server01:icmppingsec[,,,,,].last(0)}=0 | {server01:ssh.last(0)}=0 | {server01:ssh.run[load01,,,].last(0)}>10 |
{server02:icmppingsec[,,,,,].last(0)}=0 | {server02:ssh.last(0)}=0 | {server02:ssh.run[load01,,,].last(0)}>10 |
{server03:icmppingsec[,,,,,].last(0)}=0 | {server03:ssh.last(0)}=0 | {server03:ssh.run[load01,,,].last(0)}>10 |
{server04:icmppingsec[,,,,,].last(0)}=0 | {server04:ssh.last(0)}=0 | {server04:ssh.run[load01,,,].last(0)}>10 |
{server05:icmppingsec[,,,,,].last(0)}=0 | {server05:ssh.last(0)}=0 | {server05:ssh.run[load01,,,].last(0)}>10 |
{server06:icmppingsec[,,,,,].last(0)}=0 | {server06:ssh.last(0)}=0 | {server06:ssh.run[load01,,,].last(0)}>10 |
{server07:icmppingsec[,,,,,].last(0)}=0 | {server07:ssh.last(0)}=0 | {server07:ssh.run[load01,,,].last(0)}>10 |
{server08:icmppingsec[,,,,,].last(0)}=0 | {server08:ssh.last(0)}=0 | {server08:ssh.run[load01,,,].last(0)}>10 |
{server09:icmppingsec[,,,,,].last(0)}=0 | {server09:ssh.last(0)}=0 | {server09:ssh.run[load01,,,].last(0)}>10 |
{server10:icmppingsec[,,,,,].last(0)}=0 | {server10:ssh.last(0)}=0 | {server10:ssh.run[load01,,,].last(0)}>10
and then click 'Toggle input method' and the expressions show up correctly, lettered A-^. However when I save the trigger and go back to look, unly A-U have been saved, a total of 20 expressions. Is there a hard limit on the number of expressions in a trigger, and if so, anyone know where it could be modified in code?
Comment