From 87cbc5e005407c3c1207b5810e129b2564788e9d Mon Sep 17 00:00:00 2001 From: Eduard Kyvenko Date: Thu, 29 Aug 2019 08:29:40 +0200 Subject: [PATCH] Removed the bunyan as a suggested logger --- sections/errorhandling/usematurelogger.brazilian-portuguese.md | 2 +- sections/errorhandling/usematurelogger.chinese.md | 2 +- sections/errorhandling/usematurelogger.korean.md | 2 +- sections/errorhandling/usematurelogger.md | 3 +-- 4 files changed, 4 insertions(+), 5 deletions(-) diff --git a/sections/errorhandling/usematurelogger.brazilian-portuguese.md b/sections/errorhandling/usematurelogger.brazilian-portuguese.md index a1b27717..aaee5081 100644 --- a/sections/errorhandling/usematurelogger.brazilian-portuguese.md +++ b/sections/errorhandling/usematurelogger.brazilian-portuguese.md @@ -2,7 +2,7 @@ ### Explicação em um Parágrafo -Todos nós amamos console.log, mas obviamente, um logger respeitável e persistente como [Winston][winston], [bunyan][bunyan] (altamente popular) ou [pino][pino] (o novato que está focado no desempenho) é obrigatório para projetos sérios. Um conjunto de práticas e ferramentas ajudará a entender os erros muito mais rapidamente - (1) logar freqüentemente usando diferentes níveis (depuração, informação, erro), (2) ao registrar, fornecer informações contextuais como objetos JSON, ver exemplo abaixo, (3) observe e filtre os logs usando uma API de consulta de log (incorporada na maioria dos registradores) ou um software de visualização de logs, (4) Expor e selecionar a declaração de log para a equipe de operação usando ferramentas de inteligência operacional como o Splunk. +Todos nós amamos console.log, mas obviamente, um logger respeitável e persistente como [Winston][winston] (altamente popular) ou [pino][pino] (o novato que está focado no desempenho) é obrigatório para projetos sérios. Um conjunto de práticas e ferramentas ajudará a entender os erros muito mais rapidamente - (1) logar freqüentemente usando diferentes níveis (depuração, informação, erro), (2) ao registrar, fornecer informações contextuais como objetos JSON, ver exemplo abaixo, (3) observe e filtre os logs usando uma API de consulta de log (incorporada na maioria dos registradores) ou um software de visualização de logs, (4) Expor e selecionar a declaração de log para a equipe de operação usando ferramentas de inteligência operacional como o Splunk. [winston]: https://www.npmjs.com/package/winston [bunyan]: https://www.npmjs.com/package/bunyan diff --git a/sections/errorhandling/usematurelogger.chinese.md b/sections/errorhandling/usematurelogger.chinese.md index 210037a7..97aaa295 100644 --- a/sections/errorhandling/usematurelogger.chinese.md +++ b/sections/errorhandling/usematurelogger.chinese.md @@ -2,7 +2,7 @@ ### 一段解释 -我们都特别喜欢（loovve）console.log，但显而易见地，对于严肃的项目, 有信誉和持久的Logger是必需的，比如[Winston][winston], [Bunyan][bunyan] (非常流行) or [Pino][pino](专注于性能的新库)。一套实践和工具将有助于更快速地解释错误 – (1)使用不同的级别（debug, info, error）频繁地log；(2)在记录日志时, 以 JSON 对象的方式提供上下文信息, 请参见下面的示例；(3)使用日志查询API(在大多数logger中内置)或日志查看程序软件监视和筛选日志；(4)使用操作智能工具(如 Splunk)为操作团队公开和管理日志语句。 +我们都特别喜欢（loovve）console.log，但显而易见地，对于严肃的项目, 有信誉和持久的Logger是必需的，比如[Winston][winston] (非常流行) or [Pino][pino](专注于性能的新库)。一套实践和工具将有助于更快速地解释错误 – (1)使用不同的级别（debug, info, error）频繁地log；(2)在记录日志时, 以 JSON 对象的方式提供上下文信息, 请参见下面的示例；(3)使用日志查询API(在大多数logger中内置)或日志查看程序软件监视和筛选日志；(4)使用操作智能工具(如 Splunk)为操作团队公开和管理日志语句。 [winston]: https://www.npmjs.com/package/winston [bunyan]: https://www.npmjs.com/package/bunyan diff --git a/sections/errorhandling/usematurelogger.korean.md b/sections/errorhandling/usematurelogger.korean.md index 5651cf9f..0f1fb4ee 100644 --- a/sections/errorhandling/usematurelogger.korean.md +++ b/sections/errorhandling/usematurelogger.korean.md @@ -2,7 +2,7 @@ ### One Paragraph Explainer -We all love console.log but obviously, a reputable and persistent logger like [Winston][winston], [Bunyan][bunyan] (highly popular) or [Pino][pino] (the new kid in town which is focused on performance) is mandatory for serious projects. A set of practices and tools will help to reason about errors much quicker – (1) log frequently using different levels (debug, info, error), (2) when logging, provide contextual information as JSON objects, see example below. (3) watch and filter logs using a log querying API (built-in in most loggers) or a log viewer software +We all love console.log but obviously, a reputable and persistent logger like [Winston][winston] (highly popular) or [Pino][pino] (the new kid in town which is focused on performance) is mandatory for serious projects. A set of practices and tools will help to reason about errors much quicker – (1) log frequently using different levels (debug, info, error), (2) when logging, provide contextual information as JSON objects, see example below. (3) watch and filter logs using a log querying API (built-in in most loggers) or a log viewer software (4) Expose and curate log statement for the operation team using operational intelligence tools like Splunk [winston]: https://www.npmjs.com/package/winston diff --git a/sections/errorhandling/usematurelogger.md b/sections/errorhandling/usematurelogger.md index 2d14d9ea..4069d04d 100644 --- a/sections/errorhandling/usematurelogger.md +++ b/sections/errorhandling/usematurelogger.md @@ -2,10 +2,9 @@ ### One Paragraph Explainer -We all love console.log but obviously, a reputable and persistent logger like [Winston][winston], [Bunyan][bunyan] (highly popular) or [Pino][pino] (the new kid in town which is focused on performance) is mandatory for serious projects. A set of practices and tools will help to reason about errors much quicker – (1) log frequently using different levels (debug, info, error), (2) when logging, provide contextual information as JSON objects, see example below. (3) Watch and filter logs using a log querying API (built-in in most loggers) or a log viewer software. (4) Expose and curate log statement for the operation team using operational intelligence tools like Splunk. +We all love console.log but obviously, a reputable and persistent logger like [Winston][winston] (highly popular) or [Pino][pino] (the new kid in town which is focused on performance) is mandatory for serious projects. A set of practices and tools will help to reason about errors much quicker – (1) log frequently using different levels (debug, info, error), (2) when logging, provide contextual information as JSON objects, see example below. (3) Watch and filter logs using a log querying API (built-in in most loggers) or a log viewer software. (4) Expose and curate log statement for the operation team using operational intelligence tools like Splunk. [winston]: https://www.npmjs.com/package/winston -[bunyan]: https://www.npmjs.com/package/bunyan [pino]: https://www.npmjs.com/package/pino ### Code Example – Winston Logger in action