CreateLogtailPipelineConfig - Simple Log Service

Creates a Logtail pipeline configuration.

Operation description

The UK (London) region is supported. Supported regions are constantly updated.

There is currently no authorization information disclosed in the API.

POST /pipelineconfigs HTTP/1.1

Parameter	Type	Required	Description	Example
project	string	Yes	The name of the project.	test-project
body	object	No	The content of the Logtail pipeline configuration.
configName	string	Yes	The name of the configuration.	test-config
logSample	string	No	The sample log.	2022-06-14 11:13:29.796 \| DEBUG \| __main__:<module>:1 - hello world
global	object	No	The global configuration.
inputs	array<object>	Yes	The data source plug-ins.
	object	No	The data source plug-in.	{ "Type": "input_file", "FilePaths": ["/var/log/*.log"] }
processors	array<object>	No	The processing plug-ins.
	object	No	The processing plug-in.	{ "Type": "processor_parse_json_native", "SourceKey": "content" }
aggregators	array<object>	No	The aggregation plug-ins.
	object	No	The aggregation plug-in.
flushers	array<object>	Yes	The data output plug-ins.
	object	No	The data output plug-in.	{ "Type": "flusher_sls", "Logstore": "test" }

Parameter	Type	Description	Example
headers	object
Server	string	The name of the server.	nginx
Content-Type	string	The content type of the response body.	application/json
Content-Length	string	The content length of the response body.	0
Connection	string	Indicates whether the connection is persistent. Valid values: close and keep-alive. close: The connection is non-persistent. A new TCP connection is established for each HTTP request. keep-alive: The connection is persistent. After a TCP connection is established, the connection remains open, and no more time or bandwidth is consumed to establish new connections.	close
Date	string	The time when the response was returned.	Sun, 27 May 2018 08:25:04 GMT
x-log-requestid	string	The request ID.	5B0A6B60BB6EE39764D458B5

Sample success responses

JSONformat

{}

For a list of error codes, visit the Service error codes.