Hello All,

DataMiner Webservice API calls are being used to simply set a writable parameter on an element to a numeric value, then minutes later, another set is sent to set the parameter back to Zero.

For the majority of time, this is working fine without issue. During normal operation as these sets are occurring on the expected interval, I can find in SLNet logging the successful connection and parameter sets.

However, there are reports that occasionally these sets are not occurring as expected.
I have not yet been able to observe the SLNet logging at the time when a Set fails to due the unpredictability, although I'm worried the SLNet logging is clearing itself too fast in order to see this within a reasonable time after receiving a report of the issue.

Note:

• Within the 3rd party system that is querying DataMiner through the webservice API, we are seeing 2 kinds of errors.
  1. ./log-InterfaceDataminer.log.3.gz:Unable to authenticate as [user name hidden]
  2. ./log-InterfaceDataminer.log.21.gz:I/O error: Read timed out; nested exception is javax.net.ssl.SSLException: Read timed out

I'd like to see what is reported on the DataMiner side when these occur.

With that said, is SLNet logging the best place to find information about the Webservice failures? If so, is there a way to allow the data to persist a bit longer than it currently does?

I did also find the WEB logging which seems like it could potentially catch the necessary details and also does not get wiped from the DMA as fast as SLNet - however, looking at the existing WEB logs, I only see errors when the Agent is not running.
Example:

• 2025-09-22 03:58:39.702|PID:30136|TID:195|Error| [PersistentDMAConnection] Failed to connect: Failed to setup a connection with the DataMiner Agent: DataMiner is not running
  System.Exception:
  Message="Failed to setup a connection with the DataMiner Agent: DataMiner is not running"
  Source="WebApiLib"

Thank you in advance!

Regards,
Thomas