In normal development, we are likely to use 'console.log' for message logging, yet it’s simple, we are unfortunately not able to persist the messages in production mode. And you may look for some third party libraries to meet this demand, actually we can easily achieve it via 'Console' object, so why don’t implement one by ourselves?

Today I will show you a simple logger program with 'Console' object, and imitate a real logger library.

As we mentioned above, we often use 'console.log' for printing message on terminal, in fact, the 'console' is a module in Node.js, we can import explicitly with require('module'), but unnecessary, because it's also a build-in global variable, that's why we can use it directly.

Since the global console instance configured to write to 'process.stdout' and 'process.stderr', the two forms below will behave the same:

// to stdout
console.log('hello'); // to stderr
console.warn('warn');
console.error('error'); // they are equivalent to: // create our own console
let myConsole = new console.Console(process.stdout, process.stderr); // to stdout
myConsole.log('hello'); // to stderr
myConsole.warn('warn');
myConsole.error('error');

What if we change process.stdout and process.stderr to other streams? The file streams, for an instance:

// index.js

let fs = require('fs');

let options = {
flags: 'a', // append mode
encoding: 'utf8', // utf8 encoding
}; let stdout = fs.createWriteStream('./stdout.log', options);
let stderr = fs.createWriteStream('./stderr.log', options); let logger = new console.Console(stdout, stderr); // to stdout.log file
logger.log('hello'); // to stderr.log file
logger.warn('warn');
logger.error('error');

Run the code it will create two files: 'stdout.log' and 'stderr.log', and write messages into them:

And then, we can improve it slightly by adding datetime prefix to the message, which make it more like a real log library:

// index.js

let fs = require('fs');

// add a format prototype function
Date.prototype.format = function (format) {
if (!format) {
format = 'yyyy-MM-dd HH:mm:ss';
} // pad with 0
let padNum = function (value, digits) {
return Array(digits - value.toString().length + 1).join('0') + value;
}; let cfg = {
yyyy: this.getFullYear(), // year
MM: padNum(this.getMonth() + 1, 2), // month
dd: padNum(this.getDate(), 2), // day
HH: padNum(this.getHours(), 2), // hour
mm: padNum(this.getMinutes(), 2), // minute
ss: padNum(this.getSeconds(), 2), // second
fff: padNum(this.getMilliseconds(), 3), // millisecond
}; return format.replace(/([a-z])(\1)*/ig, function (m) {
return cfg[m];
});
} let options = {
flags: 'a', // append mode
encoding: 'utf8', // utf8 encoding
}; let stdout = fs.createWriteStream('./stdout.log', options);
let stderr = fs.createWriteStream('./stderr.log', options); let logger = new console.Console(stdout, stderr); for (let i = 0; i < 100; i++) {
let time = new Date().format('yyyy-MM-dd HH:mm:ss.fff'); logger.log(`[${time}] - log message ${i}`);
logger.error(`[${time}] - err message ${i}`);
}

Run the code again, and take a look at the file contents:

Looks pretty, isn't it? Now we should think about a question, how to log message into new files according to some rules? By doing so, we can easily locate the exact logs. Yeah, that's the so-called 'rolling' policy.

We will be rolling the logs by time here.

'node-schedule' is great module for this feature, it's a flexible and easy-to-use job scheduler for Node.js, and we can create our policy based on it.

The following program is bound to print the message at the beginning of every minute:

let schedule = require('node-schedule');

// invoke the function at each time which second is 0
schedule.scheduleJob({second: 0}, function() {
console.log('rolling');
});

And accordingly, 'minute: 0' config will run the function code at the beginning of each hour, 'hour: 0' config will run it at the beginning of each day.

Going back to our logger program, now all we need to do is create a new 'logger' instance for new stream files and replace the old one, let's change the code for adding a schedule:

let fs = require('fs');
let schedule = require('node-schedule'); // add a format prototype function
Date.prototype.format = function (format) {
if (!format) {
format = 'yyyy-MM-dd HH:mm:ss';
} // pad with 0
let padNum = function (value, digits) {
return Array(digits - value.toString().length + 1).join('0') + value;
}; let cfg = {
yyyy: this.getFullYear(), // year
MM: padNum(this.getMonth() + 1, 2), // month
dd: padNum(this.getDate(), 2), // day
HH: padNum(this.getHours(), 2), // hour
mm: padNum(this.getMinutes(), 2), // minute
ss: padNum(this.getSeconds(), 2), // second
fff: padNum(this.getMilliseconds(), 3), // millisecond
}; return format.replace(/([a-z])(\1)*/ig, function (m) {
return cfg[m];
});
}; function getLogger() {
let options = {
flags: 'a', // append mode
encoding: 'utf8', // utf8 encoding
}; // name the file according to the date
let time = new Date().format('yyyy-MM-dd'); let stdout = fs.createWriteStream(`./stdout-${time}.log`, options);
let stderr = fs.createWriteStream(`./stderr-${time}.log`, options); return new console.Console(stdout, stderr);
} let logger = getLogger(); // alter the logger instance at the beginning of each day
schedule.scheduleJob({hour: 0}, function() {
logger = getLogger();
}); // logging test
setInterval(function () {
for (let i = 0; i < 100; i++) {
let time = new Date().format('yyyy-MM-dd HH:mm:ss.fff'); logger.log(`[${time}] - log message ${i}`);
logger.error(`[${time}] - err message ${i}`);
}
}, 1000);

It's done, we will get two new log files at 00:00 of each day, and all messages will be writen into them.

Now, a simple logger program is completed, and it can be published as a library after proper encapsulation.

Node: 通过Console打印日志 (Log Message via Console)的更多相关文章

  1. python打印日志log

    整理一个python打印日志的配置文件,是我喜欢的格式. # coding:utf-8 # 2019/11/7 09:19 # huihui # ref: import logging LOG_FOR ...

  2. 打印日志 Log

    Log.v(tag,msg);所有内容 Log.d(tag,msg);debug Log.i(tag,msg);一般信息 Log.w(tag,msg);警告信息 Log.e(tag,msg);错误信息

  3. Android学习----打印日志Log

    Log.v(tag,msg);所有内容 Log.d(tag,msg);debug Log.i(tag,msg);一般信息 Log.w(tag,msg);警告信息 Log.e(tag,msg);错误信息 ...

  4. 大数据项目中js中代码和java中代码(解决Tomcat打印日志中文乱码)

    Idea2018中集成Tomcat9导致OutPut乱码找到tomcat的安装目录,打开logging.properties文件,增加一行代码,覆盖默认设置,将日志编码格式修改为GBK.java.ut ...

  5. Node.js系列文章:利用console输出日志文件

    通常我们在写Node.js程序时,都习惯使用console.log打印日志信息,但这也仅限于控制台输出,有时候我们需要将信息输出到日志文件中,实际上利用console也可以达到这个目的的,今天就来简单 ...

  6. Log打印日志遇到的问题

    Log日志打印出现空指针问题 AndroidRuntime(372): Caused by: java.lang.NullPointerException: println needs a messa ...

  7. 使用log4j2打印Log,log4j不能打印日志信息,log4j2不能打印日志信息,log4j和logj2,idea控制台信息乱码(文末)

    说来惭愧,今天就写了个"hello world",了解了一下log4j的日志. 本来是想在控制台打印个log信息,也是遇到坎坷重重,开始也没去了解log4j就来使用,log4j配置 ...

  8. Ubuntu系统配置日志/var/log/message

    ubuntu系统默认不生成/var/log/messages文件,有时候想查看相关日志就很不方便,于是我们可以设置使系统生成此文件. 1.先安装 apt-get install rsyslog2.用v ...

  9. rsyslog 不打印日志到/var/log/messages

    *.info;mail.none;authpriv.none;cron.none;local3.none /var/log/messages 表示 所有来源的info级别都记录到/var/log/me ...

随机推荐

  1. SpringMVC request 得到文件路径

    1.java中的路径 File directory = new File("abc"); // 对于getCanonicalPath()函数,“."就表示当前的文件夹,而 ...

  2. mysql中字符串的隐藏字符处理

    三步解决mysql字符串的隐藏字符: 1. 隐藏字符导致字符串长度边长,用mysql 自带的 Hex函数让隐藏字符显示真身, 2. 可以拿到隐藏字符的16进制码,然后用windows自带的计算器转化成 ...

  3. sql 在查询到的语句基础上添加行号

    正常查询语句: SELECT TagName FROM ps_status a WHERE a.TagName LIKE "DTmk_zybf%1bxxjcqh.PV" 查询结果: ...

  4. IDEA @override处标红

    报错问题如下 这个是没有导入父类,无法重写父类的方法 创建项目的时候没有使用jdk1.6以上的版本.将版本更正就好了

  5. Spring Boot整合UEditor不修改源码

    1.创建Springboot项目,目录结构如下(在resources中static/ueditor/jsp/config.json) 2.pom文件引入 <dependency> < ...

  6. C# 将DataTable数据写入到txt文件中

    见代码: /// <summary> /// 将DataTable里面的内容写入txt文件 /// </summary> /// <param name="dt ...

  7. DNS与ARP协议

    DNS(domain name system) DNS的作用:将域名(如baidu.com)转换为IP地址 DNS的本质是:分层的DNS服务器实现的分布式数据库: 根DNS服务器 - com DNS服 ...

  8. 【Linux】修改root密码

    sudo passwd root 然后提示输入两次新密码就可以了

  9. find和grep的使用

    1.find命令的使用 在Linux中可以使用find命令在指定的目录下查找文件.任何位于参数之前的字符串都将被视为欲查找的目录名,当使用该命令时,不设置任何参数,则find命令将在当前目录下查找子目 ...

  10. 构建C1000K的服务器(1) – 基础

    转自: http://www.ideawu.net/blog/archives/740.html 著名的 C10K 问题提出的时候, 正是 2001 年, 到如今 12 年后的 2013 年, C10 ...