Update leveled.schema
To set log level
This commit is contained in:
parent
31badfd601
commit
10f250e4be
1 changed files with 10 additions and 0 deletions
|
@ -41,6 +41,7 @@
|
|||
{datatype, atom}
|
||||
]}.
|
||||
|
||||
|
||||
%% @doc Compression point
|
||||
%% The point at which compression is applied to the Journal (the Ledger is
|
||||
%% always compressed). Use on_receipt or on_compact. on_compact is suitable
|
||||
|
@ -51,6 +52,15 @@
|
|||
{datatype, atom}
|
||||
]}.
|
||||
|
||||
%% @doc Log level
|
||||
%% Can be debug, info, warn, error or critical
|
||||
%% Set the minimum log level to be used within leveled. Leveled will log many
|
||||
%% lines to allow for stats to be etracted by those using log indexers such as
|
||||
%% Splunk
|
||||
{mapping, "leveled.log_level", "leveled.log_level", [
|
||||
{default, info},
|
||||
{datatype, atom}
|
||||
]}.
|
||||
|
||||
%% @doc The approximate size (in bytes) when a Journal file should be rolled.
|
||||
%% Normally keep this as around the size of o(100K) objects. Default is 500MB
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue