EMQX Cloud update: log analysis adds more parameters, monitoring operation and maintenance is more worry-free

Recently, EMQX Cloud, a fully managed MQTT messaging cloud service, has released a function update: the "Log" module has been optimized, and multiple analysis parameters have been added to help users perform more effective system monitoring and operation and maintenance.

Function introduction

As a fully managed MQTT cloud service that aims to relieve users from the burden of infrastructure management and maintenance, EMQX Cloud helps users to understand the system operation status in a timely manner through the real-time online log viewing function, and trace and troubleshoot the discovered faults to ensure the stability of the system. run.

The previous log analysis parameters are only time, log level, and instance ID, and the function implementation is relatively basic. The latest version has carried out a number of low-level optimizations to this function, and added optional parameters, including client ID, client IP, user name, subject, resource ID, and rule ID, for users to filter and search, more accurate and fast. Locate the error and solve the problem. Instead, the node will be displayed directly in the alert details.

function usage

After the user enters the console, click "Log" to query the log. The default parameters include display time, log level, error type, client ID, and client IP. Click more conditions to expand directional log retrieval based on parameters such as username, subject, resource ID, and rule ID.

Descriptions of the fields included in the log are shown in the following table:

parameter	meaning
time	log report time
log level	Mainly divided into the following three types of alarm errors. Emergency users can deal with them according to different priorities.
error type	Mainly divided into the following five types of data integration: errors related to data integration. The corresponding service is not running or an error caused by other reasons. For example, when storing to MySQL, MySQL is not running, unauthorized, or table errors, etc. Client: Client-related errors, including incorrect authentication information, incorrect access control information, and failure to connect due to other reasons. Messages: Errors related to messages, such as encoding problems, dropped messages, etc. Modules: Errors related to emqx modules, such as custom authentication errors caused by not being able to connect to the corresponding service. EMQX internal errors: Erlang and errors that cannot be classified into the above. The user can quickly locate the error generating module according to the error type.
Client ID	Enter the client ID to search the logs generated by the client ID
Client IP	Enter the client IP, search the log generated by changing the client IP
username	Enter username to search the logs generated by the username
theme	Enter the topic name to search the logs generated under the topic
resource ID	Enter the resource ID to search logs related to this resource
Rule ID	Enter the rule ID to search logs related to this rule

Note: EMQX Cloud supports free log storage and retrieval within 14 days. Logs beyond 14 days will not be queried. If you have special needs, you can submit a ticket in the console and contact us.

For common log analysis and solutions, please refer to the document: https://docs.emqx.com/zh/cloud/latest/deployments/logs.html

Copyright statement: This article is original by EMQ, please indicate the source when reprinting.

Original link: https://www.emqx.com/zh/blog/emqx-cloud-update-log-analysis-adds-more-parameters