I’m looking to see whether Unimus can provide more detailed error information when a device discovery fails.
Right now, when a device fails in discovery, I often need to manually troubleshoot (credentials, connectivity, etc.). If there were a way for Unimus to display clearer failure reasons - for example, authentication issues, unreachable device, timeout, or unsupported protocol - it would save a lot of time and make it easier to immediately target the cause.
Is there an existing feature or setting that exposes these errors during discovery?
[Solved] Request: Error Messages or Logging for Discovery Failures
We have pretty extensive debugging available in the Zones menu:
https://wiki.unimus.net/display/UNPUB/L ... +Subsystem
Please note, I wouldn't recommend leaving it on all the time as the logs can become quite extensive and I have encountered times where I frustrated my diagnostic efforts with months of debugging logs.
https://wiki.unimus.net/display/UNPUB/L ... +Subsystem
Please note, I wouldn't recommend leaving it on all the time as the logs can become quite extensive and I have encountered times where I frustrated my diagnostic efforts with months of debugging logs.
Just as a side-node, even the basic logs for Discovery failures should suggest what is wrong. You can just click the red job indicator on the Devices page, or check Dashboard > Device Job History > Latest failed job > select job > Show result.
That will have a nice write-out of what failed for Discovery. In case that is not sufficient, like Tommy mentioned, you can always enable Debug logging through Zones > Debug Mode.
That will have a nice write-out of what failed for Discovery. In case that is not sufficient, like Tommy mentioned, you can always enable Debug logging through Zones > Debug Mode.