Viewing a Trace
When tracing is enabled, the logs for each Zoomdata microservice contains several values injected into the log message. A sample log message might look like:
2018-08-20 09:26:14,032 [qtp2117495919-31] ERROR [<traceID>, <currentSpanID>, <true|false>] [c.z.c.s.i.s.SourceService] Save source My FLAT FILE Source, old source id 5b7a886030c49e00013616f0
The following substitutions are shown in this sample following the log level (ERROR in the sample):
- <traceID>: the trace ID
- <currentSpanID>: the current span ID
- <true|false>: indicates whether this item was sampled and sent to the tracing microservice.
You can use the trace ID to view the trace and to download a diagnostics bundle that includes tracing information
To view the trace:
Using a web browser, navigate to the Zoomdata tracing microservice. Its default port is 9411. For example, if running locally, the URL would be http://localhost:9411.
A search box should be available in the upper right corner with the placeholder text Go to trace.
Enter the trace ID from the log into the search box and click Search. A screen containing the trace ID should appear:
If you receive an error message such as the following error message, it means that either the trace ID was improperly typed or copied or that it is very old (e.g., several days) and is no longer retained by the tracing microservice.
Go to trace ERROR: Cannot load trace 37518589215bc3e6: server error (Not Found)
Tracing information is generally intended to be retrieved within several hours of its creation.
Was this topic helpful?