Customer is currently having occasional issues with EZD startup process. Support doesn't seem to be able to isolate a specific problem based on received debug logs. Customer wants to know if customer side applications can have some API functionality to generate logs to detect and troubleshoot EZD startup issues.
Hi @nicolas.ooka, unfortunately EZD does not expose any API's for monitoring. Even the monitoring tools like ITRS scrape the EZD logs to look for issues. There is an ezdmon process available in the /bin directory, which works just like TREP monitoring tools - using the shared memory.
These tools will be of little use, if the EZD process itself is failing to start. EZD needs to run with administrative privileges. The client application can either read the EZD log file or use the failure to connect message in the API, to detect that the EZD process isn't running.