From bdb9f2bb625e4624cf430214ebfed42e17573fde Mon Sep 17 00:00:00 2001 From: Ruben Deyhle Date: Mon, 27 Aug 2018 20:36:37 +0200 Subject: [PATCH] Mention possibility to set log level for profiling (#1407) * Mention possibility to set log level for profiling I found out that it is indeed possible to set the log level for profiling logs by supplying an object with a `level` property. This should be mentioned in the docs. * Update README.md --- README.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 126537419..e1ff3fabf 100644 --- a/README.md +++ b/README.md @@ -821,9 +821,12 @@ on: }, 1000); ``` -All profile messages are set to 'info' level by default and both message and -metadata are optional. There are no plans in the Roadmap to make this -configurable, but we are open to suggestions through new issues! +All profile messages are set to 'info' level by default, and both message and +metadata are optional. For individual profile messages, you can override the default log level by supplying a metadata object with a `level` property: + +```js +logger.profile('test', { level: 'debug' }); +``` ## Querying Logs