In its current implementation AnaLog agent keeps producing messages despite server's availability. In periods of server downtime it leads to a lot of error messages being logged.
It may look as a basic retry mechanism but in fact is is not because actual retry is provided by the clients - they re-initiate the last watching session themselves as soon as the server returns online. So if the agent has its own tracking process it can receive a command to establish another one for the same target resource. It seems needless.
May be, it's worth to check the server's availability from the agent during the registration. It would help to early detect network access issues (when server can reach the agent but not vice-verse).
In its current implementation AnaLog agent keeps producing messages despite server's availability. In periods of server downtime it leads to a lot of error messages being logged.
It may look as a basic retry mechanism but in fact is is not because actual retry is provided by the clients - they re-initiate the last watching session themselves as soon as the server returns online. So if the agent has its own tracking process it can receive a command to establish another one for the same target resource. It seems needless.