After upgrading the console to version 9.1.5.406, triggers were not generating as expected. Monitors and agents were also updated, but the issue persisted. A user suggests that the issue may be related to the different timezones on the monitors. They recommend opening a ticket if the problem persists.
Read the entire ‘Troubleshooting Trigger Generation after ControlUp Console Upgrade’ thread below:
Hi,
We have a customer who recently upgraded the console to version 9.1.5.406. After the upgrade, we noticed that triggers are not generating as expected, even though they were working fine previously. There were no other changes apart from the console upgrade.
Could this issue be related to the new version?
Just the console? Or every component?
Console and agents
What about the monitors?
Depending on how the agents are configured (inbound vs outbound), upgrading the agents but NOT the monitors would break the connection. As monitors won’t connect to agents that are running a higher version as themselves
Yup upgraded monitors as well
monitors, agents both
🙂
Sorry to be nitpicky.
If everything runs the same version, triggers should work. Monitors are responsible to fire triggers. But I am not aware of any known issues.
If triggers simply stopped working, I’d suggest opening a ticket.
Or alternatively create a simple trigger and see if you can get it to fire
Yeah we recreated the triggers and they started working (we have monitors with different timezones) if that can be issue
That is not how things should work. If the problem still exists (if you haven’t recreated all triggers) I’d strongly suggest opening a ticket
sure will do
Continue reading and comment on the thread ‘Troubleshooting Trigger Generation after ControlUp Console Upgrade’. Not a member? Join Here!
Categories: All Archives, ControlUp Scripts & Triggers