Coerce LogEvents to data.frames, data.tables,
or tibbles.
# S3 method for LogEvent
as.data.frame(
x,
row.names = NULL,
optional = FALSE,
stringsAsFactors = FALSE,
...,
box_if = function(.) !(is.atomic(.) && identical(length(.), 1L)),
cols_expand = NULL
)
as.data.table.LogEvent(
x,
...,
box_if = function(.) !(is.atomic(.) && identical(length(.), 1L)),
cols_expand = "msg"
)
as_tibble.LogEvent(
x,
...,
box_if = function(.) !(is.atomic(.) && identical(length(.), 1L)),
cols_expand = "msg"
)any R object.
NULL or a character vector giving the row
names for the data frame. Missing values are not allowed.
currently ignored and only included for compatibility.
logical scalar: should character vectors be
converted to factors? Defaults to FALSE (as opposed to
base::as.data.frame()) and is only included for compatibility.
passed on to data.frame()
a function that returns TRUE or FALSE to determine
which values are to be boxed (i.e. placed as single elements in a list
column). See example
character vector. Columns to not box (even if
box_if() returns TRUE). Vectors in these columns will result in multiple
rows in the result (rather than a single list-column row). This defaults to
"msg" for vectorized logging over the log message.
lg <- get_logger("test")
lg$info("lorem ipsum")
#> INFO [20:04:36.138] lorem ipsum
as.data.frame(lg$last_event)
#> level timestamp logger caller msg
#> 1 400 2023-03-04 20:04:36 test eval lorem ipsum
lg$info("LogEvents can store any custom log values", df = iris)
#> INFO [20:04:36.146] LogEvents can store any custom log values {df: <data.frame 150x5>}
as.data.frame(lg$last_event)
#> level timestamp logger caller
#> 1 400 2023-03-04 20:04:36 test eval
#> msg df
#> 1 LogEvents can store any custom log values c(5.1, 4....
head(as.data.frame(lg$last_event)$df[[1]])
#> Sepal.Length Sepal.Width Petal.Length Petal.Width Species
#> 1 5.1 3.5 1.4 0.2 setosa
#> 2 4.9 3.0 1.4 0.2 setosa
#> 3 4.7 3.2 1.3 0.2 setosa
#> 4 4.6 3.1 1.5 0.2 setosa
#> 5 5.0 3.6 1.4 0.2 setosa
#> 6 5.4 3.9 1.7 0.4 setosa
# how boxing works
# by default non-scalars are boxed
lg$info("letters", letters = letters)
#> INFO [20:04:36.159] letters {letters: (a, b, c, d, e, f, g, h, i, j, k, l, m, n, o, p, q, r, s, t, u, v, w, x, y, z)}
as.data.frame(lg$last_event)
#> level timestamp logger caller msg letters
#> 1 400 2023-03-04 20:04:36 test eval letters a, b, c,....
# this behaviour can be modified by supplying a custom boxing function
as.data.frame(lg$last_event, box_if = function(.) FALSE)
#> level timestamp logger caller msg letters
#> 1 400 2023-03-04 20:04:36 test eval letters a
#> 2 400 2023-03-04 20:04:36 test eval letters b
#> 3 400 2023-03-04 20:04:36 test eval letters c
#> 4 400 2023-03-04 20:04:36 test eval letters d
#> 5 400 2023-03-04 20:04:36 test eval letters e
#> 6 400 2023-03-04 20:04:36 test eval letters f
#> 7 400 2023-03-04 20:04:36 test eval letters g
#> 8 400 2023-03-04 20:04:36 test eval letters h
#> 9 400 2023-03-04 20:04:36 test eval letters i
#> 10 400 2023-03-04 20:04:36 test eval letters j
#> 11 400 2023-03-04 20:04:36 test eval letters k
#> 12 400 2023-03-04 20:04:36 test eval letters l
#> 13 400 2023-03-04 20:04:36 test eval letters m
#> 14 400 2023-03-04 20:04:36 test eval letters n
#> 15 400 2023-03-04 20:04:36 test eval letters o
#> 16 400 2023-03-04 20:04:36 test eval letters p
#> 17 400 2023-03-04 20:04:36 test eval letters q
#> 18 400 2023-03-04 20:04:36 test eval letters r
#> 19 400 2023-03-04 20:04:36 test eval letters s
#> 20 400 2023-03-04 20:04:36 test eval letters t
#> 21 400 2023-03-04 20:04:36 test eval letters u
#> 22 400 2023-03-04 20:04:36 test eval letters v
#> 23 400 2023-03-04 20:04:36 test eval letters w
#> 24 400 2023-03-04 20:04:36 test eval letters x
#> 25 400 2023-03-04 20:04:36 test eval letters y
#> 26 400 2023-03-04 20:04:36 test eval letters z
as.data.frame(lg$last_event, cols_expand = "letters")
#> level timestamp logger caller msg letters
#> 1 400 2023-03-04 20:04:36 test eval letters a
#> 2 400 2023-03-04 20:04:36 test eval letters b
#> 3 400 2023-03-04 20:04:36 test eval letters c
#> 4 400 2023-03-04 20:04:36 test eval letters d
#> 5 400 2023-03-04 20:04:36 test eval letters e
#> 6 400 2023-03-04 20:04:36 test eval letters f
#> 7 400 2023-03-04 20:04:36 test eval letters g
#> 8 400 2023-03-04 20:04:36 test eval letters h
#> 9 400 2023-03-04 20:04:36 test eval letters i
#> 10 400 2023-03-04 20:04:36 test eval letters j
#> 11 400 2023-03-04 20:04:36 test eval letters k
#> 12 400 2023-03-04 20:04:36 test eval letters l
#> 13 400 2023-03-04 20:04:36 test eval letters m
#> 14 400 2023-03-04 20:04:36 test eval letters n
#> 15 400 2023-03-04 20:04:36 test eval letters o
#> 16 400 2023-03-04 20:04:36 test eval letters p
#> 17 400 2023-03-04 20:04:36 test eval letters q
#> 18 400 2023-03-04 20:04:36 test eval letters r
#> 19 400 2023-03-04 20:04:36 test eval letters s
#> 20 400 2023-03-04 20:04:36 test eval letters t
#> 21 400 2023-03-04 20:04:36 test eval letters u
#> 22 400 2023-03-04 20:04:36 test eval letters v
#> 23 400 2023-03-04 20:04:36 test eval letters w
#> 24 400 2023-03-04 20:04:36 test eval letters x
#> 25 400 2023-03-04 20:04:36 test eval letters y
#> 26 400 2023-03-04 20:04:36 test eval letters z
# The `msg` argument of a log event is always vectorized
lg$info(c("a vectorized", "log message"))
#> INFO [20:04:36.176] a vectorized
#> INFO [20:04:36.176] log message
as.data.frame(lg$last_event)
#> level timestamp logger caller msg.c..a.vectorized....log.message..
#> 1 400 2023-03-.... test eval a vectorized
#> 2 400 2023-03-.... test eval log message
#> msg.c..a.vectorized....log.message...1
#> 1 a vectorized
#> 2 log message
lg$config(NULL)
#> <Logger> [info] test
#>
#> inherited appenders:
#> console: <AppenderConsole> [all] -> console