Design

Log Viewer component is introduced to view all the server logs through User interface.

All the logs corresponding to the server components are streamed to fluentd and the same is displayed on the UI using Grafana and Loki.

Zipkin is used to trace the logs. This provision enables user to track the progress of the events/messages progressed among different components and the present status.

Display

Below is the snapshot of how the logs are viewed on the UI. Logs from different components could be tailed or search for a specific keyword or filter the logs based on different criteria. The available querying mechanisms help in retrieving data based on required conditions.

All the logs are displayed with the latest logs first.

• The maximum retention period of logs is one week.

Features

Component Filter

Though all the server component logs are available on the UI, user has provision to view specific component logs as well. Each server component will have corresponding label that is displayed under the query parameters which needs to be selected to view the logs of that specific component.

This helps if the user is interested in viewing the logs of specific component and/or when required to monitor the specific component. Instead of selecting all the components, user will provide the label corresponding to the component. The below snapshot illustrates the filter criteria.

Time Filter

Along with/out component filter, user could filter the logs based on the time filter. There are different pre-defined time filters available and have an option to provide specific filter conditions.

Log Level Filter

Logs could be filtered with Log level as well. This filter could be applied for all components or specific components based on the query logic.

Below is an example where only “INFO” logs are required from one component and all logs from other components.

Below is an example to get Error logs.

Trace

All the logs will have traceId which will be used to track the progress of the message or event being progressed between different components. Zipkin provides detailed chart of the message’s progress with timings.

Search

Search functionality is available where a keyword is searched across different log files. This will help during debugging based on any task execution ID or user ID activities.

It also provides options to auto-refresh the query results, limit the display of lines in the result, and live tailing.