We are using the Twilio module to send out alerts from within Ignition. On a recent restart of the server for some planned maintenance to our facility, the module failed to reconnect to Twilio. I haven't done a lot of research to determine if this is expected behavior or not at this point, but it brought to light a concern I had failed to previously consider, that we aren't really monitoring this connection status. I get that I can see that in the settings, but it's not something that (at least currently) shows up in the status page & it doesn't generate an alarm of any sort when it's failed.
We are using Twilio to handle text messaging out alarms but we also have redundancy by means of email.
On the reboot, after realizing we had a failed connection, I just went into the Twilio settings, didn't change anything, and clicked on save changes. That seemed to restart it & everything worked after that.
So in an ideal world, I'd be able to monitor for that failure & reinitiate that module automatically, maybe try that a few times & if it didn't work, then create an alarm.
In a less ideal world, I'd at least be able to monitor the status of that as an alarm, so that it would show on the alarms page & would be able to send email notifications as well to state that it had failed. That would at least make the issue more visible & that's better than nothing.
The only thing I've kind of found that ight work would be to periodically trigger a text message through Twilio from scripting & then use that failure to generate an alarm... but it's not really an ideal solution in my mind because I'd rather not be sending meaningless messages that need to be ignored to anyone.
Any ideas for how to go about this would be most appreciated!