POST Log Forwarder Batch
Adds a log forwarding destination.
{
"forwarders": [
{
"acceptCert": false,
"name": "test1",
"host": "10.10.10.10",
"port": 9000,
"protocol": "cfapi",
"sslEnabled": false,
"workerCount": 8,
"diskCacheSize": 104857600,
"tags": {},
"filter": "",
"forwardComplementaryFields": true
},
{
"acceptCert": false,
"name": "test2",
"host": "10.10.10.10",
"port": 1514,
"protocol": "syslog",
"sslEnabled": true,
"workerCount": 12,
"diskCacheSize": 104857600,
"tags": {},
"filter": "",
"transportProtocol": "tcp",
"forwardComplementaryFields": false
}
]
}
Successfully added log forwarder configuration.
Partial success - not all configurations are added successfully
{
"multiStatus": [
{
"configName": "test 1",
"status": 409,
"info": "Forwarder with specified name already exists."
},
{
"configName": "test 2",
"status": 201
},
{
"configName": "test 3",
"status": 400,
"info": "more than 10 configs are not supported"
},
{
"configName": "test 4",
"status": 400,
"info": "more than 10 configs are not supported"
}
]
}
The request failed because the request body either did not contain valid JSON, or did not match the required JSON format.
{
"errorMessage": "Invalid request body.",
"errorCode": "JSON_FORMAT_ERROR",
"errorDetails": {
"reason": "..."
}
}
A message describing the error.
A code representing the type of error.
Dynamic error details, where the field name can vary depending on the request field and error code.
The request was refused because it lacks valid authentication
credentials. This can happen if the Authorization header
was missing, or if it contained an invalid session ID.
Obtain a new session ID and retry the request,
or make an unauthenticated request without the Authorization header.
"Invalid session ID"
The request was refused because the session ID has
expired. Obtain a new session ID from /api/v1/sessions.
"Login Timeout"
curl -X POST -H 'Authorization: <value>' -H 'Content-Type: application/json' -d '[{}]' https://{api_host}/api/v1/log-forwarder/batch