package js_of_ocaml-lwt
Install
dune-project
Dependency
Authors
Maintainers
Sources
sha256=158dafe7271ac79157981d1c3f5f177ec78a0099c38f861ae14e7ac06bd29c3a
sha512=d83f0988aa1089fa01a0a693d7e6a832018c5a8ce707f44685809769377ef7ef59ce48229b1612966bd9166b610d66ddff8f2606f6c3f09c49f601b74842fde1
doc/js_of_ocaml-lwt.logger/Lwt_log_js/index.html
Module Lwt_log_js
include module type of Lwt_log_core
with type level = Lwt_log_core.level
and type logger = Lwt_log_core.logger
and type section = Lwt_log_core.section
and type template = Lwt_log_core.template
and module Section = Lwt_log_core.Section
This module provides functions to deal with logging. It support:
- logging to multiple destination at the same time
- filtering logs per destination
Types
type level = Lwt_log_core.level = | Debug(*Debugging message. They can be automatically removed by the syntax extension.
*)| Info(*Informational message. Suitable to be displayed when the program is in verbose mode.
*)| Notice| Warning(*Something strange happend
*)| Error(*An error message, which should not means the end of the program.
*)| Fatal(*A fatal error happened, in most cases the program will end after a fatal error.
*)
Type of log levels. A level determines the importance of a message
type logger = Lwt_log_core.loggerType of a logger. A logger is responsible for dispatching messages and storing them somewhere.
type section = Lwt_log_core.sectionEach logging message has a section. Sections can be used to structure your logs. For example you can choose different loggers according to the section.
Each section carries a level, and messages with a lower log level than than the section level will be dropped.
Section levels are initialised using the contents of the LWT_LOG environment variable, which must contain one or more rules of the form pattern -> level separated by ";". Where pattern is a string that may contain *.
For example, if LWT_LOG contains:
access -> warning;
foo[*] -> errorthen the level of the section "access" is Warning and the level of any section matching "foo[*]" is Error.
If the pattern is omited in a rule then the pattern "*" is used instead, so LWT_LOG may just contain "debug" for instance.
By default, the following rule apply : "* -> notice"
val string_of_level : level -> stringval level_of_string : string -> level optionReset the rules set when parsing the LWT_LOG environment variable using this string.
load_rules parses the rules string and validates the rules before loading them. If fail_on_error is true, invalid rules will cause this function to raise Failure and leave existing rules unchanged. If fail_on_error is false (this is the default), it tries to load as many rules as possible and ignore invalid ones. If the rules string itself cannot be parsed, existing rules are always left unchanged.
Example:
Lwt_log_core.load_rules ~fail_on_error:true "* -> nosuchlevel" (* Raises Failure *)
Lwt_log_core.load_rules "* -> info"val add_rule : string -> level -> unitadd_rule pattern level adds a rule for sections logging levels. The rule is added before all other rules. It takes effect immediately and affects all sections for which the level has not been set explicitly with Section.set_level. pattern may contains *. For example:
Lwt_log_core.add_rule "lwt*" Lwt_log_core.Infoval append_rule : string -> level -> unitappend_rule pattern level adds the given rule after all other rules. For example to set the default fallback rule:
Lwt_log_core.append_rule "*" Lwt_log_core.InfoLogging functions
The following functions are the same as log except that their name determines which level is used.
For example info msg is the same as log ~level:Info msg.
module Section = Lwt_log_core.SectionSections
Log templates
type template = Lwt_log_core.templateA template is for generating log messages.
It is a string which may contains variables of the form $(var), where var is one of:
messagewhich will be replaced by the message emitedlevelwhich will be replaced by a string representation of the levelsectionwhich will be replaced by the name of the message's sectionloc-filewhich will be replaced by the file name of the calling logging functionloc-linewhich will be replaced by the line number of the calling logging functionloc-columnwhich will be replaced by the column number of the calling logging function
For example:
"$(name): $(message)""$(name): $(loc-file): $(loc-line): $(loc-column): $(message)"
val render :
buffer:Buffer.t ->
template:template ->
section:section ->
level:level ->
message:string ->
unitrender ~buffer ~template ~section ~level ~message instantiate all variables of template, and store the result in buffer. The location is obtained from threads local storage.
val location_key : (string * int * int) Lwt.keyThe key for storing current location.
Loggers
val make :
output:(section -> level -> string list -> unit Lwt.t) ->
close:(unit -> unit Lwt.t) ->
loggermake ~output ~close creates a new logger.
The default logger. It is used as default when no one is specified. If Lwt_core is linked (in the package lwt.unix) the default logger sends all messages to standard error. Otherwise the default logger is null.
broadcast loggers is a logger which send messages to all the given loggers.
Note: closing a broadcast logger does not close its components.
dispatch f is a logger which dispatch logging instructions to different logger according to their level and/or section.
Here is an example:
let access_logger = Lwt_log.file "access.log"
and error_logger = Lwt_log.file "error.log" in
Lwt_log_core.dispatch
(fun section level ->
match Lwt_log_core.Section.name section, level with
| "access", _ -> access_logger
| _, Lwt_log_core.Error -> error_logger)Predefined loggers
val null : loggerLogger which drops everything
Lwt logger for js_of_ocaml
Predefined logger
val console : Lwt_log_core.loggerLogger that use the javascript console object.
Logging functions
val log :
?inspect:'v ->
?exn:exn ->
?section:section ->
?location:(string * int * int) ->
?logger:logger ->
level:level ->
string ->
unit Lwt.tlog ?section ?logger ~level message logs a message.
section defaults to Section.main. If logger is not specified, then the default one is used instead (see default).
If exn is provided, then its string representation (= Printexc.to_string exn) will be append to the message, and if possible the backtrace will also be logged.
If inspect is provided, it will be append to the message.
location contains the location of the logging directive, it is of the form (file_name, line, column).
val log_f :
?inspect:'v ->
?exn:exn ->
?section:section ->
?location:(string * int * int) ->
?logger:logger ->
level:level ->
('a, unit, string, unit Lwt.t) format4 ->
'alog_f is the same as log except that it takes a format string
val ign_log :
?inspect:'v ->
?exn:exn ->
?section:section ->
?location:(string * int * int) ->
?logger:logger ->
level:level ->
string ->
unitSame as log but ignore the resulting thread.
val ign_log_f :
?inspect:'v ->
?exn:exn ->
?section:section ->
?location:(string * int * int) ->
?logger:logger ->
level:level ->
('a, unit, string, unit) format4 ->
'aSame as log_f but ignore the resulting thread.
The following functions are the same as log except that their name determines which level is used.
For example info msg is the same as log ~level:Info msg.