Tracing
The Tracing screen displays information about traces recorded during cluster operation. You need to enable tracing. The recorded information can include informational messages, error messages, duration of specific operations, stack traces, etc. You can use this information to troubleshoot cluster operation or identify latency issues.
The screen displays a table containing all recorded traces, including the name of the event, its start time, duration and number of spans.
A trace is recorded information about the execution of a specific event. Each trace consists of a tree of spans. A span is an individual unit of work performed by the system in order to process the event.
A trace can include spans from multiple nodes.
Configuring Tracing
To configure tracing:
-
Click the CONFIGURE TRACING button in the upper right corner of the page.
The Configure Tracing dialog appears.
-
Choose one or several Included Scopes from the drop-down list for each scope.
-
For each of the selected scopes, specify a percentage in the Sampling Rate field.
-
Click OK for the changes to take effect.
Viewing Spans
A span contains a set of tags and a set of logs attached to it. A tag is a key-value pair with information about the span. A log is a key-value pair with information about a specific moment or event within a span.
You can click on a trace name to view the spans included in the trace.
You can also click on a span to view the tags and logs attached to the span.
© 2024 GridGain Systems, Inc. All Rights Reserved. Privacy Policy | Legal Notices. GridGain® is a registered trademark of GridGain Systems, Inc.
Apache, Apache Ignite, the Apache feather and the Apache Ignite logo are either registered trademarks or trademarks of The Apache Software Foundation.