In an effort to not have over 100 trigger and actions to monitor and alert for each individual ink and toner in our printer fleet, I was trying to craft a smaller number of triggers and actions that would do the same thing. I'm realizing however this might not be possible, but wanted to see if anyone had thoughts on this.
The first issue is the triggers. For a printer with 12 supplies I put each item with a < 15 evaluation in a single trigger. The thought was, any time one of them went under 15%, the trigger would go off. I'm realizing however the trigger probably is not evaluating each item as a separate event, so if one went below 15, then another did before the first was replaced, the trigger would still be in PROBLEM status from the first and not fire a second time, so the Action wouldn't fire again? If that's true, I really do need one trigger per item rather than being able to group them?
The second issue is the action. It already has 20 triggers in it (one for each printer, each trigger of which has 1-12 items monitored as above). If each item needs it's own trigger, this action would have over 100 triggers in it, unless I grouped them out based on some random choice. I'm not sure if there is a limit there? Now past that I think it would work as the action will fire multiple times independently for each trigger, and not just once for any of them, as I have others that seem to work ok in this regard. But, in those cases each trigger is monitoring one item, so again it's a question of can things be grouped to lower clutter, or do I just need to have a ton of things to make this work right?
Hope that makes sense and wasn't too rambling. Ultimately the goal is any time a printer supply in any printer hits 15% I want a warning email, and at 5% another warning, then the ok email when it's replaced. Any thoughts or experience on this is appreciated
The first issue is the triggers. For a printer with 12 supplies I put each item with a < 15 evaluation in a single trigger. The thought was, any time one of them went under 15%, the trigger would go off. I'm realizing however the trigger probably is not evaluating each item as a separate event, so if one went below 15, then another did before the first was replaced, the trigger would still be in PROBLEM status from the first and not fire a second time, so the Action wouldn't fire again? If that's true, I really do need one trigger per item rather than being able to group them?
The second issue is the action. It already has 20 triggers in it (one for each printer, each trigger of which has 1-12 items monitored as above). If each item needs it's own trigger, this action would have over 100 triggers in it, unless I grouped them out based on some random choice. I'm not sure if there is a limit there? Now past that I think it would work as the action will fire multiple times independently for each trigger, and not just once for any of them, as I have others that seem to work ok in this regard. But, in those cases each trigger is monitoring one item, so again it's a question of can things be grouped to lower clutter, or do I just need to have a ton of things to make this work right?
Hope that makes sense and wasn't too rambling. Ultimately the goal is any time a printer supply in any printer hits 15% I want a warning email, and at 5% another warning, then the ok email when it's replaced. Any thoughts or experience on this is appreciated