Release Notes and Announcements

Release Notes

Announcements

User Guide

Product Introduction

Overview

Features

Available Regions

Limits

Concepts

Service Regions and Service Providers

Purchase Guide

Billing Overview

Product Pricing

Pay-as-You-Go

Billing

Cleaning up CLS resources

Cost Optimization

FAQs

Getting Started

Getting Started in 1 Minute

Getting Started Guide

Quickly Trying out CLS with Demo

Operation Guide

Resource Management

Permission Management

Log Collection

Metric Collection

Log Storage

Metric Storage

Search and Analysis (Log Topic)

Search and Analysis (Metric Topic)

Dashboard

Data Processing documents

Shipping and Consumption

Monitoring Alarm

Cloud Insight

Independent DataSight console

Historical Documentation

Practical Tutorial

Log Collection

Search and Analysis

Dashboard

Monitoring Alarm

Shipping and Consumption

Cost Optimization

Developer Guide

Embedding CLS Console

CLS Connection to Grafana

API Documentation

History

Introduction

API Category

Making API Requests

Topic Management APIs

Log Set Management APIs

Index APIs

Topic Partition APIs

Machine Group APIs

Collection Configuration APIs

Log APIs

Metric APIs

Alarm Policy APIs

Data Processing APIs

Kafka Protocol Consumption APIs

CKafka Shipping Task APIs

Kafka Data Subscription APIs

COS Shipping Task APIs

SCF Delivery Task APIs

Scheduled SQL Analysis APIs

COS Data Import Task APIs

Data Types

Error Codes

FAQs

Health Check

Collection

Log Search

Others

CLS Service Level Agreement

CLS Policy

Data Processing And Security Agreement

Glossary

Log

PDF

Focus Mode

Font Size

Last updated: 2024-01-20 16:31:37

Log
Logs are record data generated during the running of an application system, such as user operation logs, API access logs, and system error logs. Logs are usually stored in text format on the host where the application system resides. A log corresponding to a system running record may contain one line of text (single-line log) or multiple lines of text (multi-line log).
Logs can be uploaded the CLS via LogListener or other methods such as APIs or SDKs.
Example of a single-line log:
59.x.x.x - - [06/Aug/2019:12:12:19 +0800] "GET /nginx-logo.png HTTP/1.1" 200 368 "http://119.x.x.x/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.142 Safari/537.36" "-"
Example of a multi-line log:
  java.net.SocketTimeoutException:Receive timed out
    at j.n.PlainDatagramSocketImpl.receive0(Native Method)[na:1.8.0_151]
    at j.n.AbstractPlainDatagramSocketImpl.receive(AbstractPlainDatagramSocketImpl.java:143)[^]
    at j.n.DatagramSocket.receive(DatagramSocket.java:812)[^]
    at o.s.n.SntpClient.requestTime(SntpClient.java:213)[classes/]
    at o.s.n.SntpClient$1.call(^:145)[^]
    at ^.call(^:134)[^]
    at o.s.f.SyncRetryExecutor.call(SyncRetryExecutor.java:124)[^]
    at o.s.f.RetryPolicy.call(RetryPolicy.java:105)[^]
    at o.s.f.SyncRetryExecutor.call(SyncRetryExecutor.java:59)[^]
    at o.s.n.SntpClient.requestTimeHA(SntpClient.java:134)[^]
    at ^.requestTimeHA(^:122)[^]
    at o.s.n.SntpClientTest.test2h(SntpClientTest.java:89)[test-classes/]
    at s.r.NativeMethodAccessorImpl.invoke0(Native Method)[na:1.8.0_151]
The main components of a log are as follows:
Component
Description
Example
__TIMESTAMP__
Log time, in the format of a UNIX timestamp in milliseconds
1640005601188
__FILENAME__
Log source file
/data/log/nginx/access.log
__SOURCE__
Log source IP
10.0.1.2
Log body
Log body content, in key:value format (key is the field name, and value is the field value.)
If the log extraction mode is full text in a single line or full text in multi lines (the entire raw log is reported without splitting), the entire log is stored in the __CONTENT__ field.
If the log extraction mode is any other mode (such as splitting with a separator), each part of the raw log corresponds to a key:value pair.
Full text in a single line or full text in multi lines:
10.20.20.10;[2018-07-16 13:12:57];GET /online/sample HTTP/1.1;200
Other modes:
IP: 10.20.20.10 
request: GET /online/sample HTTP/1.1
status: 200
time: [2018-07-16 13:12:57]
Metadata
Simple description or categorization of logs. For example, the cluster or container of a TKE log is stored in the key:value format, where key starts with __TAG__.
__TAG__.clusterId:1skzv59c
Log group
A log group (LogGroup) is a collection of multiple logs. In the process of log upload, to increase data read/write efficiency, multiple logs can be packaged into one log group and then sent to CLS.
Logs in the same log group have the same basic information (__TIMESTAMP__, __FILENAME__, __SOURCE__, metadata, etc.).

Help and Support

Was this page helpful?

You can also Contact sales or Submit a Ticket for help.

Help us improve! Rate your documentation experience in 5 mins.

Feedback

tencent cloud

Cloud Log Service

Log

Log

Log group

Help and Support

Component	Description	Example
__TIMESTAMP__	Log time, in the format of a UNIX timestamp in milliseconds	1640005601188
__FILENAME__	Log source file	/data/log/nginx/access.log
__SOURCE__	Log source IP	10.0.1.2
Log body	Log body content, in `key:value` format (`key` is the field name, and `value` is the field value.) If the log extraction mode is full text in a single line or full text in multi lines (the entire raw log is reported without splitting), the entire log is stored in the __CONTENT__ field. If the log extraction mode is any other mode (such as splitting with a separator), each part of the raw log corresponds to a `key:value` pair.	Full text in a single line or full text in multi lines: 10.20.20.10;[2018-07-16 13:12:57];GET /online/sample HTTP/1.1;200 Other modes: IP: 10.20.20.10 request: GET /online/sample HTTP/1.1 status: 200 time: [2018-07-16 13:12:57]
Metadata	Simple description or categorization of logs. For example, the cluster or container of a TKE log is stored in the `key:value` format, where `key` starts with __TAG__.	__TAG__.clusterId:1skzv59c