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 ServiceAPI referenceData processor APIModifyProcessor
Copy page
Download PDFData processor API
ModifyProcessor
Copy pageDownload PDFModifyProcessor
Use the ModifyProcessor API to update the name, description, DSL content, and other settings for a data processor.
Request instructions
- Request method: PUT
- Request URL: https://{tls-endpoint}/ModifyProcessor
Request parameters
The following table lists unique request parameters for this API and certain common parameters. For more information, see Common parameters.
Body
Parameters | Type | Required | Example value | Description |
Parameters | Type | Required | Example value | Description |
DSLContent | String | NOT | f_rename("path", "newpath") | Processor's DSL content. Defines specific logic or configuration for the processor. Length must be between 1 and 4,000 characters. |
Description | String | NOT | This is a data processor | Description for the data processor. Briefly explain the purpose or function of the data processor. Length must be between 1 and 255 characters. |
FailStrategy | String | NOT | keep_raw | Configure how to handle invalid log data
|
ProcessorId | String | Yes | 9e91e9e5-2063-4182-8eff-b7371500**** | Data processor ID. |
ProcessorName | String | NOT | log_processor_1 | Name of the data processor. Used to uniquely identify a data processor. Length must be between 1 and 63 characters. |
Response parameters
Sample request
PUT https://{tls-endpoint}/ModifyProcessor HTTP/1.1
Content-Type: application/json
{
"DSLContent": "f_rename("path", "newpath")",
"Description": "This is a data processor",
"FailStrategy": "keep_raw",
"ProcessorId": "9e91e9e5-2063-4182-8eff-b7371500****",
"ProcessorName": "log_processor_1"
}
Sample response
Content-Type: application/json; charset=utf-8
{}
Error Code
Last updated: 2026.05.07 11:17:18
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
