Modifies a Logtail configuration file.
Description
If the configurations of a machine group are updated, the Logtail configuration file is applied to the machine group.
Request syntax
PUT /configs/configName HTTP/1.1
Authorization: LOG yourAccessKeyId:yourSignature
Content-Type:application/json
Date: GMT Date
Host: Projectname.Endpoint
x-log-apiversion: 0.6.0
x-log-signaturemethod: hmac-sha1
{
"configName": "testcategory1",
"inputType": "file",
"inputDetail": {
"logType": "common_reg_log",
"logPath": "/var/log/httpd/",
"filePattern": "access.log",
"localStorage": true,
"timeFormat": "%Y/%m/%d %H:%M:%S",
"logBeginRegex": ".*",
"regex": "(\w+)(\s+)",
"key" :["key1", "key2"],
"filterKey":["key1"],
"filterRegex":["regex1"],
"topicFormat": "none"
},
"outputType": "LogService",
"outputDetail":
{
"logstoreName": "perfcounter"
}
}
The value of the Host parameter consists of a project name and an endpoint. You must specify a project name for the Host parameter.
Request parameters
- Request headers
The UpdateConfig operation does not have operation-specific request headers. For information about the common request headers of Log Service API operations, see Common request headers.
- Request parameters
For information about the request parameters and examples of Logtail configuration files in various modes, see Logtail configuration files.
Response parameters
- Response headers
The UpdateConfig operation does not have operation-specific response headers. For information about the common response headers of Log Service API operations, see Common response headers.
- Response elements
If the request succeeds, the HTTP status code 200 is returned. If the request is successful, no other elements are returned.
Examples
- Sample requests
PUT /configs/logtail-config-sample Header : { "Content-Length": 737, "Host": "ali-test-project.cn-hangzhou-devcommon-intranet.sls.aliyuncs.com", "x-log-bodyrawsize": 737, "Content-MD5": "431263EB105D584A5555762A81E869C0", "x-log-signaturemethod": "hmac-sha1", "Date": "Mon, 09 Nov 2015 09:14:32 GMT", "x-log-apiversion": "0.6.0", "User-Agent": "log-python-sdk-v-0.6.0", "Content-Type": "application/json", "Authorization": "LOG yourAccessKeyId:yourSignature" } Body : { "outputDetail": { "logstoreName": "sls-test-logstore" }, "inputType": "file", "inputDetail": { "regex": "([\\d\\.] +) \\S+ \\S+ \\[(\\S+) \\S+\\] \"(\\w+) ([^\"]*)\" ([\\d\\.]+) (\\d+) (\\d+) (\\d+|-) \"([^\"]*)\" \"([^\"]*)\".*", "filterKey": [], "logPath": "/var/log/nginx/", "logBeginRegex": "\\d+\\.\\d+\\.\\d+\\.\\d+ - .*", "logType": "common_reg_log", "topicFormat": "none", "localStorage": true, "key": [ "ip", "time", "method", "url", "request_time", "request_length", "status", "length", "ref_url", "browser" ], "filePattern": "access*.log", "timeFormat": "%d/%b/%Y:%H:%M:%S", "filterRegex": [] }, "outputType": "LogService", "configName": "logtail-config-sample" }
- Sample responses
HTTP/1.1 200 OK Header : { "date": "Mon, 09 Nov 2015 09:14:32 GMT", "connection": "close", "x-log-requestid": "564063F899248CAA2300B778", "content-length": "0", "server": "nginx/1.6.1" }
Error codes
HTTP status code | Error code | Error message | Description |
---|---|---|---|
404 | ConfigNotExist | Config configName does not exist. | The error message returned because the specified Logtail configuration file does not exist. |
400 | InvalidParameter | Invalid config resource json. | The error message returned because a parameter value is invalid. |
400 | BadRequest | Config resource configname does not match with request. | The error message returned because the specified resource name does not match the resource name in the request. |
500 | InternalServerError | Internal server error. | The error message returned because an internal server error has occurred. |
For more information about the error codes, see Common error codes.