Torch Log Service
Torch Log Service
Torch Log Service
Document
Product News
Product Overview
Product Billing
User Guide
TLS Agent
AgentLoop
Resource management
Host group
Data collection
LogCollector collection
Introduction to LogCollector
Installation and upgrade
Collect host logs
Collect container logs
LogCollector plugins
Manage LogCollector
general reference
Data import
Cloud product log collection
TOS log collection
DBW log collection
VPN Log collection
VKE log collection
CLB log collection
CloudTrail log collection
CFW log collection
NTA log collection
ALB log collection
APMPlus log collection
veFaaS log collection
VPC log collection
veImageX log collection
TrafficRoute DNS log collection
DDoS log collection
WAF log collection
DCDN log collection
Multi-cloud security platform log collection
APIG log collection
Machine learning task log collection
CR log collection
Volcano Ark application lab log collection
FileNAS log collection
LLM Application Firewall Service log collection
vePFS log collection
Cloud security center log collection
EFS log collection
Data storage
Query and analysis
Configure log indexes
Query log
Analyze logs
Query and analyze logs using third-party tools
Associate external data source for log query
SQL function
SQL syntax
Visualization
Query and analysis charts
Summaries of query and analysis charts
Create dashboard
Use dashboard
Add dashboard filters and variables
Use other systems to analyze logs
Log application
Log applications for product observability
Log applications for large models observability
Coding Agent log app
ModelProvider log app
No-coding Agent log app
Log applications for basic service monitoring
Data processing
Data transformation
Syntax and functions
Global operation function
expression function
Data processing best practices
general reference
Data write processor
Data consumer processor
Data consumption and shipping
Ship logs to TOS
Ship logs to Kafka
Ship logs to Splunk
Alarm
Alarm policy
Alarm notification content
Alarm notification content template
alarm notification channel
Tracing service
Monitor Log Service
API reference
Project management API
Topic management API
Shard management API
Index management API
Log management API
Host group management API
Collection configuration management API
Data import API
Data processor API
Data transformation API
Data backflow API
SQL analysis API
Alarm management API
Consumer group management API
Kafka protocol consumption API
Tag management API
Trace storage API
Account management API
SDK reference
Go SDK
Java SDK
Python SDK
iOS SDK
C++ SDK
CLI reference
Best practices
Data collection
Query and analysis
permission management
Consumption and delivery
Visualization
Alarm
FAQs
Billing and cost FAQ
Data collection FAQ
Data storage FAQ
Index configuration FAQ
Query and analysis FAQ
Scheduled SQL tasks FAQ
Alarm FAQ
- Documentation
Torch Log ServiceUser GuideData processingData transformationSyntax and functionsGlobal operation functionField check function
Copy page
Download PDFGlobal operation function
Field check function
Copy pageDownload PDFField check function
This topic describes the syntax and format of field validation functions, as well as relevant scenario examples.
f_has function
Checks whether the specified field exists.
Function syntax/format
f_has(field)
The parameters are described below:
Parameters | Parameter type | Required | Default value | Value range | Description |
Parameters | Parameter type | Required | Default value | Value range | Description |
field | String | Yes | / | / | Checks whether a field name exists. |
Function examples
- Scenario: Checks whether the msg field exists in logs. If it exists, a new field status is added.
- Processing rules:
- c_if(f_has("msg"), f_set("status", "200"))
- Log example
- {"log-level":"INFO","msg":"hello"}
- Processing result:
- {"log-level":"INFO","msg":"hello","status":"200"}
f_not_has function
Determine whether the specified field does not exist.
Function syntax/format
f_not_has(field)
The parameters are described below:
Parameters | Parameter type | Required | Default value | Value range | Description |
Parameters | Parameter type | Required | Default value | Value range | Description |
field | String | Yes | / | / | Check whether the field name does not exist. |
Function examples
- Scenario: Checks whether the log-level field exists in the log. If not, a new field status is added.
- Processing rules:
- c_if(f_not_has("log-level"), f_set("status", "400"))
- Log example
- [{"log-level":"DEBUG","msg":"hello"},{"msg":"world"}]
- Processing result:
- [{"log-level":"DEBUG","msg":"hello"},{"msg":"world","status":"400"}]
Last updated: 2026.05.13 18:00:38
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
