Skip to content

Performance Metrics

Emakin nodes are designed to collect and expose a range of performance metrics and traces. These features are crucial for system administrators to effectively monitor the system's health and performance. The metrics are exposed using OpenTelemetry and Jaeger export formats.

Deploying Trace Tool

Jaeger is employed as the trace tool for monitoring and troubleshooting distributed systems based on microservices, providing capabilities for:

  • Distributed context propagation
  • Distributed transaction monitoring
  • Root cause analysis
  • Service dependency analysis
  • Performance and latency optimization

To deploy the Jaeger trace tool, execute the following Docker command:

1
docker run --rm --name jaeger -p 16686:16686 -p 6831:6831/udp jaegertracing/all-in-one:1.21

For more comprehensive information regarding Jaeger setup and configuration, please refer to the official Jaeger documentation available at https://www.jaegertracing.io/docs/1.22/getting-started/.

Upon successful deployment of the trace tool, all Emakin nodes within the same network will automatically begin transmitting trace data to the tool via the UDP protocol.

Trace List

The Jaeger trace tool graphical user interface (GUI) can be accessed through a web browser at the address http://localhost:16686.

Within the Jaeger UI, the Service list enumerates the host names of the Emakin nodes contributing trace data. The * Operation* list dynamically populates with a list of operations being traced. Due to the dynamic nature of Emakin, the operations listed may vary across different nodes, reflecting the specific activities being performed by each node.

Jaeger Trace Tool GUI

Trace View

Selecting a specific trace from the trace list will display the Trace View, providing detailed information about that particular operation. The trace details include:

  • Operation Name: The name of the operation being traced.
  • Start Time: The timestamp indicating when the operation commenced.
  • End Time: The timestamp indicating when the operation concluded.
  • Duration: The total time taken for the operation to complete.
  • Tags: A collection of key-value pairs providing contextual information related to the operation.

The content of the Tags section is operation-specific and may contain diverse information depending on the type of operation being traced. These tags offer valuable insights into the execution context and parameters of the operation.

Trace Detail View

By utilizing the Jaeger trace tool and the performance metrics exposed by Emakin nodes, administrators can gain a comprehensive understanding of system behavior, identify potential performance bottlenecks, and effectively troubleshoot issues within the Emakin environment.