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.
33
●0 ●1 ●1
App side Debugging to troubleshoot EZD Startup Issues available?
From your description, it sounds like the customer is already capturing some basic debug logs - are these at the application level generated by the API?
IF so, the additional logging we could enable is low-level trace.
Please advise which API the customer is using (e.g. RFA, EMA, ETA) including language (Java/C++ etc) so that we can provide the appropriate information on how to enable trace.
It may be worth sharing the debug logs here in case we can glean some additional information from an API perspective.
Also, note that if the failure is before the API manages to establish a connection, the API may not generate any trace.
13k
●32 ●12 ●18
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.
33
●0 ●1 ●1
Hello and thanks for the reply.
I had a feeling there would likely not be an API based method to monitor the EZD startup process itself. I will share this for now.
