In a separator log, the entire log data can be structured according to the specified separator, and each complete log ends with a line break
\n. When CLS processes separator logs, you need to define a unique key for each separate field.
Assume the raw data of a log is:
10.20.20.10 - ::: [Tue Jan 22 14:49:45 CST 2019 +0800] ::: GET /online/sample HTTP/1.1 ::: 127.0.0.1 ::: 200 ::: 647 ::: 35 ::: http://127.0.0.1/
If the separator for log parsing is specified as
:::, the log will be segmented into eight fields, and a unique key will be defined for each of them as shown below:
IP: 10.20.20.10 - bytes: 35 host: 127.0.0.1 length: 647 referer: http://127.0.0.1/ request: GET /online/sample HTTP/1.1 status: 200 time: [Tue Jan 22 14:49:45 CST 2019 +0800]
test-separatoras Log Topic Name and click OK.
The log file collection path is in the format of [directory prefix expression]/**/[file name expression]. LogListener matches all paths with common prefixes that satisfy the [directory prefix expression], and monitors all log files under these directories (including subdirectories) that satisfy the [file name expression]. The detailed parameter description is as follows:
|Directory prefix||The directory prefix for log files, which supports only the wildcard characters
|/**/||Current directory and all its subdirectories.|
|File name||A log file name supports only the wildcard characters
Common configuration modes are as follows:
- [Common directory prefix]/**/[common filename prefix]*
- [Common directory prefix]/**/*[common filename suffix]
- [Common directory prefix]/**/[common filename prefix]*[common filename suffix]
- [Common directory prefix]/**/*[common string]*
|No.||Directory Prefix Expression||Filename Expression||Description|
|1.||/var/log/nginx||access.log||In this example, the log path is configured as
|2.||/var/log/nginx||*.log||In this example, the log path is configured as
|3.||/var/log/nginx||error*||In this example, the log path is configured as
- Only LogListener 2.3.9 or above allows adding multiple collection paths.
- The system does not support uploading logs with contents in multiple text formats, which may cause write failure, such as
- You’re advised to configure the collection path as
log/*.logand rename the old file after log rotation as
- By default, a log file can only be collected by one log topic. If you want to have multiple collection configurations for the same file, please add a soft link to the source file and add it to another collection configuration.
Select the target machine group from the machine group list and associate it with the current log topic. Please note that the associated machine group must be in the same region as the log topic. For detailed directions, please see Machine Group Management.
You need to select a unique separator first. The system segments the sample log according to the selected separator and displays it in the extraction result box. You need to define a unique key for each field. Currently, log collection supports a variety of separators. Common separators include space, tab, comma, semicolon, and vertical bar. If your log data uses other separators such as
::: , it can also be parsed through custom delimiter.
Time configuration is described as follows:
Keep Collection Time as enabled.
Disable Collection Time and enter the time key of the original timestamp and the corresponding time parsing format in Time Key and Time Parsing Format respectively. For more information on the time parsing format, please see Configuring Time Format.
Below are examples of how to enter a time parsing format:
Example 1: the parsing format of the original timestamp
Example 2: the parsing format of the original timestamp
2017-12-10 08:00:00 is
Example 3: the parsing format of the original timestamp
12/10/2017, 08:00:00 is
Second can be used as the unit of log time. If the time is entered in a wrong format, the collection time is used as the log time.
Filters are designed to help you extract valuable log data by adding log collection filter rules based on your business needs. If the filter rule is a Perl regular expression, the created filter rule will be a hit rule; in other words, only logs that match the regular expression will be collected and reported.
For separator-formatted logs, you need to configure a filter rule according to the defined custom key-value pair. For example, if you want to collect all log data with a
status field whose value is 400 or 500 after the sample log is parsed in separator mode, you need to configure
status and the filter rule as
The relationship logic between multiple filter rules is "AND". If multiple filter rules are configured for the same key name, previous rules will be overwritten.
Log in to the CLS console, select Log Search in the left sidebar, select the target logset and log topic, and click Search to search for logs.
Index configuration must be enabled before you can perform searches.