Was wondering if there is a mechanism for allowing gateway event scripts to execute on the redundant/non-active ignition gateway – was hoping to collect diagnostics on all of my gateway machines regardless of their duty/standby state (would prefer to know if we have an issue with our backup gateway before we fail over to it!).
I currently have my diagnostics gathering/logging running as a “timer” script.
There’s no such mechanism.
ok – thanks Kevin
Assuming the only way would be to write a custom module? Or would the module not execute while the gateway is in “standby” either?
Modules still load and run and decide what to do with redundancy status.
I’m not sure what you’d be listening to to decide to execute, and what execute would mean in the context of your own module.
Consider using an external (i.e., not in Ignition) webserver health checker. Something that hits Ignition’s
/main/StatusPing address on some useful interval. (Use just
/StatusPing on v8.0.)
Thanks @pturmel – will definitely consider for some of the high level info… was trying to adapt the Ignition Diagnostics script embedded in the “Ignition Diagnostics” UDT that was shared at the Ignition CIC this year → gateway event script.
I have it working with all of my “master” gateways – but am only able to get the “backup” gateway info to log while I force the failover… was hoping that some of the non-licensed functionality (e.g. gateway event scripts?) would run if I had redundancy standby activity level set to “warm”
Was hoping to log Ignition-specific info like status of database connections, tag providers, tag groups/scan classes, error logs, etc. – not sure if it is possible to do this with an external tool like you mentioned (e.g. outside of the gateway context)