Issue description
Initial phase:
reference : here
A logging plugin that works and does its job : )
Supported Protocol: SYSLOG-UDP
schema:
local schema = {
type = "object",
properties = {
customer_token = {type = "string"},
severity = {
type = "string",
default = "INFO",
enum = {"DEBUG", "INFO", "NOTICE", "WARNING", "ERR", "CRIT", "ALERT", "EMEGR",
"debug", "info", "notice", "warning", "err", "crit", "alert", "emegr"},
description = "base severity log level",
},
include_req_body = {type = "boolean", default = false},
include_resp_body = {type = "boolean", default = false},
include_resp_body_expr = {
type = "array",
minItems = 1,
items = {
type = "array"
}
},
tags = {
type = "array",
minItems = 1,
items = {
type = "string"
}
},
prefer_name = {type = "boolean", default = true}
},
required = {"customer_token"}
}
Metadata schema
local defaults = {
host = "logs-01.loggly.com",
port = 514,
protocol = "syslog",
timeout = 5000
}
local metadata_schema = {
type = "object",
properties = {
host = {
type = "string",
default = defaults.host
},
port = {
type = "integer",
default = defaults.port
},
protocol = {
type = "string",
default = defaults.protocol,
-- more methods coming soon
enum = {"syslog"}
},
timeout = {
type = "integer",
minimum = 1,
default= defaults.timeout
},
log_format = {
type = "object",
}
}
}
Phase-2
- Supported Protocol: HTTP[S]
- Support Changing Log Severity level based on HTTP response code.
This issue is for the tracking purpose of the plugin development. If you have any useful insight, feel free to let us know : )
Issue description
Initial phase:
reference : here
A logging plugin that works and does its job : )
Supported Protocol: SYSLOG-UDP
schema:
Metadata schema
Phase-2
This issue is for the tracking purpose of the plugin development. If you have any useful insight, feel free to let us know : )