Overview
Cloud Development provides developers with robust log search and management capabilities, helping them perform application debugging, issue troubleshooting, and performance monitoring more efficiently.
Observability Capabilities
CloudBase log monitoring consists of three parts, covering the full chain of "search logs → view metrics → receive alerts":
| Capability | Description | Documentation |
|---|---|---|
| Logs | Search and view runtime logs by resource type and time range | Log Management |
| Monitoring | Resource-level invocation statistics and performance metrics | Operations Monitoring |
| Alerting | Configure alert policies based on monitoring metrics | Metric Alerts |
All of the above capabilities are also available through the CloudBase CLI, which fits batch queries and automation scenarios: Log Search, Monitoring Metrics, and Platform Alerts.
Core Advantages
- Diverse Search Methods: Supports full-text search, key-value search, fuzzy keyword search
- Rich Query Syntax: Provides various query syntaxes to meet different scenario requirements
- Real-time Log Monitoring: Monitor application runtime status in real time and quickly locate issues
Features
🔍 Intelligent Log Search
Provides multiple flexible log search methods to meet the needs of different scenarios:
| Search Method | Applicable Scenarios | Features |
|---|---|---|
| Full-text search | Quickly locate key information | Supports keyword full-text search |
| Key-value search | Precisely locate structured data | Supports key:value format queries |
| Fuzzy Matching | Use when keywords are uncertain | Intelligent fuzzy matching algorithm |
| Advanced Syntax | Complex query requirements | Supports combining multiple query syntaxes |
Please refer to Log Search for detailed search methods.
Technical Principles
To improve search efficiency and accuracy, the Cloud Development log service employs intelligent tokenization mechanisms and case-sensitive matching to precisely pinpoint log information entered by users.
Token Delimiters
The raw log text will be split into multiple keywords based on token delimiters. The default delimiters for Cloud Development are !@#%^&*()_="', <>/?|\;:\n\t\r[]{}. Take the following log content as an example:
10002345987;write;ERROR;code=400;topic does not exist;
In the above log content, the two default token delimiters ; and = will split the log content into 6 words: 10002345987, write, ERROR, code, 400, topic does not exist. In precise search, users only need to enter any one of the words to retrieve this log entry.
- Because the requestId in Log Default System Fields contains hyphens, the hyphen (-) is not included in the default token delimiters.
- For user logs tokenized by delimiters, each tokenized segment must not exceed 32KB.
Case Sensitivity
Cloud Development log search is case-sensitive by default. For example, in the log content example above, the log has been split into 6 words: 10002345987, write, ERROR, code, 400, topic does not exist. To precisely search for logs containing the keyword ERROR, enter ERROR in the console.
If you enter error or Error in the console, you cannot retrieve logs containing ERROR.