Reviewed-by: Mützel, Andrea <andrea.muetzel@t-systems.com> Co-authored-by: Liu, Siying <liusiying@noreply.gitea.eco.tsi-dev.otc-service.com> Co-committed-by: Liu, Siying <liusiying@noreply.gitea.eco.tsi-dev.otc-service.com>
12 KiB
Setting Structured and Tag Fields
Setting Structured Fields
You can set extracted fields after cloud structuring. For details, see Table 1.
Template Name |
Field Name |
Field Type Can Be Changed |
Field Can Be Deleted |
---|---|---|---|
Regular expressions (auto generate) |
User-defined. The name must start with a letter and contain only letters and digits. |
Yes |
Yes |
Regular expressions (manually enter) |
|
Yes |
Yes |
JSON |
Names are set automatically, but you can set aliases for fields. |
Yes |
Yes |
Delimiter |
Default names such as field1, field2, field3 are used. You can modify these names. |
Yes |
Yes |
Nginx |
Names are set based on Nginx configuration, but you can set aliases for fields. |
Yes |
Yes |
Custom templates |
User-defined. |
Yes |
Yes |

When you use regular expressions (manually entered), JSON, delimiters, Nginx, or custom templates to structure logs, field names:
- Can contain only letters, digits, hyphens (-), underscores (_), and periods (.).
- Cannot start with a period (.) or underscore (_) or end with a period (.).
- Can contain 1 to 64 characters.
Setting Tag Fields
When you structure logs, you can configure tag fields, so you can use these fields to run SQL queries on the Visualization page.
- In Step 2 Extract fields, click the Tag Fields tab and Add Field.
- In the Field column, enter a name for the tag field, for example, hostIP.
- To add more fields, click Add Field.
- Click Save.
- Tag fields can be the following system fields: category, clusterId, clusterName, containerName, hostIP, hostId, hostName, nameSpace, pathFile, and podName.
- Tag fields cannot be the following system fields: groupName, logStream, lineNum, content, logContent, logContentSize, and collectTime.
- You can configure both field extraction and tag fields during log structuring.