umgeher/leveled
0
Fork 0
Code Issues Pull requests Releases Activity Actions

Update leveled.schema

Browse source 
To set log level
This commit is contained in:
Martin Sumner 2019-02-13 14:36:45 +00:00
parent 31badfd601
commit 10f250e4be
1 changed files with 10 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

10
priv/leveled.schema
View file

@ -41,6 +41,7 @@
{datatype, atom} {datatype, atom}
]}. ]}.
%% @doc Compression point %% @doc Compression point
%% The point at which compression is applied to the Journal (the Ledger is %% 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 %% always compressed). Use on_receipt or on_compact. on_compact is suitable
@ -51,6 +52,15 @@
{datatype, atom} {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. %% @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 %% Normally keep this as around the size of o(100K) objects. Default is 500MB