EMQX Cloud Update: More Parameters Added to Log Analysis for Better Monitoring and Operations
Recently, EMQX Cloud, a fully managed MQTT messaging cloud service, has released a feature update: the “Log” module has been optimized and several new analysis parameters have been added to help users conduct more effective system monitoring and operation and maintenance.
As a fully managed MQTT cloud service designed to relieve users of the burden of infrastructure management and maintenance, EMQX Cloud helps users keep abreast of system operation through real-time online viewing of logs, tracing and troubleshooting problems found to ensure stable system operation.
The previous log analysis parameters included only time, log level and instance ID, which are relatively basic. The latest version has optimized the feature and added optional parameters, including client ID, client IP, username, topic, resource ID, and rule ID, for users to filter and search, so as to locate errors and solve problems more accurately and quickly. And the node will be displayed directly in the log details.
Users can query logs by clicking “Logs” after entering the console. The default parameters are display time, log level, error type, client ID and client IP, and click on “more” to expand targeted log search based on username, topic, resource ID and rule ID.
The fields contained in the logs are described in the following table:
|Time||Time of log reporting|
|Log Level||There are following 3 main types of alert errors:WarningErrorCriticalUsers can handle them according to their priorities.|
|Error Type||There are 5 main types of errors：Data integration：Data integration related errors caused by the corresponding service not running or other reasons. For example, when storing to MySQL, MySQL is not running, unauthorized, or table error, etc. Clients: client-related errors, including incorrect authentication information, incorrect access control information, and other reasons for not being able to connect. Messages: message-related errors, such as coding problems, message loss, etc. Modules: emqx module related errors, such as custom authentication errors due to inability to connect to the corresponding service. EMQX Internal Error: Erlang and errors that cannot be classified to the above cases. 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 client IP to search the logs generated by the client IP|
|Username||Enter username, search the logs generated by the username|
|Topic||Enter topic name, search the logs generated by this topic|
|Resource ID||Enter resource ID, search the logs related to this resource|
|Rule ID||Enter rule ID, search the logs related to the rule|
Note: EMQX Cloud supports free log storage and retrieval within 14 days, logs beyond 14 days will not be supported for query, if you have special needs, you can contact us by submitting a work order within the console.
Common log analysis and resolution measures can be found in the document: https://docs.emqx.com/en/cloud/latest/deployments/logs.html