Please Dojo,
Quick follow-up from this previous post:
Element Timeout for protocols with multiple interfaces: is it interface-specific?
I understand that by default, from release 9.5.6, the whole element will go in timeout when at least one of the interfaces configured for timeout are no longer retrieving data: is there a way to include in the Alarm Console what's the interface timing out?
I'd happily rely on this instead of always having to check the streamViewer - was thinking about an alarm property, perhaps, but not sure it would serve any logging use-case for alarm history, as when the timeout is solved the alarm property would be cleared.
Any steer will be helpful.
The comment field of the timeout alarm will contain the IP address and the port which are configured on the interface that is timing out. This should give you the necessary information to link it back to an interface id.
If the timeout alarm would go unnoticed, even at a later stage when checking the alarm history you can still check which interface was causing the timeout as the comment of the original timeout alarm will not be cleared.
When multiple interfaces are in timeout, the comment will contain a comma separated list of the endpoint details that are configured on those interfaces.
Thank you Jeroen, this saved the day 😉
I had completely forgotten about that column – enabling it right now!