Skip to main content
POST
/
logs
Create a new log
curl --request POST \
  --url https://api.eu.bronto.io/logs \
  --header 'Content-Type: application/json' \
  --header 'X-BRONTO-API-KEY: <api-key>' \
  --data '
{
  "log": "http",
  "logset": "demo"
}
'
{
  "logset": "demo",
  "log": "firewall",
  "log_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "is_system_generated": false,
  "tags": {
    "region": "eu",
    "environment": "production"
  },
  "drop_events": 0,
  "level": "trace"
}

Authorizations

​
X-BRONTO-API-KEY
string
header
required

Body

application/json
​
log
string
required

The name of the log

Required string length: 1 - 255
Example:

"http"

​
logset
string

The name of the log set

Maximum string length: 255
Example:

"demo"

Response

Log created successfully

​
logset
string
required

The name of the log set

Example:

"demo"

​
log
string
required

The name of the log

Example:

"firewall"

​
log_id
string<uuid>
required

The unique identifier of the log

​
is_system_generated
boolean

Whether the log is generated by the system

Example:

false

​
tags
object

A map of key value pairs associated with this log

Example:
{
  "region": "eu",
  "environment": "production"
}
​
drop_events
number
default:0

This is the percentage of new incoming data for this log that will be rejected (where 0.0 is no data rejection and 1.0 is all data rejection). Rejected data is not recoverable and will not be indexed or monitored.

Required range: 0 <= x <= 1
​
level
enum<string>
default:trace

This is the log level at which incoming events will be accepted. For example if info is set then debug and trace events will be rejected. Events with no level will be allowed irrespective of the level set. Rejected data is not recoverable and will not be indexed or monitored.

Available options:
trace,
debug,
info,
warning,
error,
severe,
critical,
fatal,
notice,
alert,
emergency