# OPC-UA fsm logs

**URL:** <https://forum.inductiveautomation.com/t/opc-ua-fsm-logs/116412>\
**Category:** Ignition\
**Created:** [July 15, 2026, 9:23am UTC](https://forum.inductiveautomation.com/t/opc-ua-fsm-logs/116412 "2026-07-15T09:23:19Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andre\_Hennecke](https://avatars.discourse-cdn.com/v4/letter/a/e95f7d/32.png) [@Andre\_Hennecke](https://forum.inductiveautomation.com/u/Andre_Hennecke)\
**Post date:** [July 15, 2026, 9:23am UTC](https://forum.inductiveautomation.com/t/opc-ua-fsm-logs/116412/1 "2026-07-15T09:23:19Z")

</div>

Hi,

we 've observed some onWatchdogTimerElapsed() warnings from OPCUASubscriptionManager and SessionFSM (Keep Alive failureCount exceeded).

This is most likely not an issue on the Ignition side. However, troubleshoting is difficult because th warnings don't identify which OPC-UA connection is affected.  
Would it be possible to include the OPC-UA connection name in these warning messages in a future release?  
We also tried to set the log level to debug, but the log volume is quite high to leave enabled for an extended period to catch the root cause / connection.

Thank you,  
André

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [July 15, 2026, 12:54pm UTC](https://forum.inductiveautomation.com/t/opc-ua-fsm-logs/116412/2 "2026-07-15T12:54:11Z")

</div>

I can't get the connection name plumbed in because it's all part of the OPC UA library, but I could probably get SessionFsm to log the session id any time it logs while a session is available, which also gets logged in the `onSessionActive` and `onSessionInactive` callbacks implemented by Ignition, and those log messages do include the connection name as an MDC key/value. So there would at least be a path to correlating the messages.

---

<div class="post-metadata">

**Author:** ![Andre\_Hennecke](https://avatars.discourse-cdn.com/v4/letter/a/e95f7d/32.png) [@Andre\_Hennecke](https://forum.inductiveautomation.com/u/Andre_Hennecke)\
**Post date:** [July 15, 2026, 1:19pm UTC](https://forum.inductiveautomation.com/t/opc-ua-fsm-logs/116412/3 "2026-07-15T13:19:42Z")

</div>

Yes, the MDC context would also help, I guess 👍

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [July 16, 2026, 5:10pm UTC](https://forum.inductiveautomation.com/t/opc-ua-fsm-logs/116412/4 "2026-07-16T17:10:07Z")

</div>

That was fast--saw the logger change in your Milo 1.1.5 merge. Will this make 8.3.9?

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [July 16, 2026, 5:12pm UTC](https://forum.inductiveautomation.com/t/opc-ua-fsm-logs/116412/5 "2026-07-16T17:12:21Z")

</div>

Yeah, 1.1.5 is released, PR is up internally for the upgrade.