Closed emelski closed 2 years ago
facing the same issue
Thanks for the ping, @zhfahan77. We have not forgotten this and may even post some questions here to solicit feedback/opinions.
@zhfahan77 can you provide some more detail about your use case?
@emelski @zhfahan77 have we lost traction on this issue? It's pretty old and should be closed out if it's not going to be fleshed out.
I no longer need this functionality so I'm happy to close it.
Currently,
logger-node
requires that the log level specified for a log message belongs to a pre-defined set of known log levels. In my use case I'm aggregating logs from several sources, so the log levels are not known in advance. Sincelogger-node
passes the log level to LogDNA servers explicitly (that is, the level is specified in the JSON payload aslevel: 'THE_LEVEL'
), LogDNA does not actually require that the log level belong to a predefined set -- this requirement appears to be imposed only bylogger-node
. It would be nice if this additional constraint could be disabled.