logagent-js
Advanced tools
Comparing version 1.1.17 to 1.1.19
@@ -102,3 +102,3 @@ /* | ||
} else { | ||
this.sources[sourceName].reader = new MultiLine(null, parser) | ||
this.sources[sourceName].reader = new MultiLine(/^\S+/, parser) | ||
return this.sources[sourceName].reader | ||
@@ -105,0 +105,0 @@ } |
{ | ||
"name": "logagent-js", | ||
"version": "1.1.17", | ||
"version": "1.1.19", | ||
"description": "Smart log parser written in Node", | ||
@@ -5,0 +5,0 @@ "main": "lib/index.js", |
@@ -32,4 +32,13 @@ # logagent-js | ||
- JSON lines are parsed, and scanned for @timestamp and time fields (logstash and bunyan format) | ||
- default patterns for: | ||
- MongoDB, | ||
- default patterns for many applications (see below) | ||
- Heroku logs | ||
To test patterns or convert logs from text to JSON use the command line tool 'logagent'. | ||
It reads from stdin and outputs line delimited JSON (or pretty JSON or YAML) to the console. | ||
In addtion it can forward the parsed objects directly to [Logsene](http://sematext.com/logsene). | ||
# Pattern definitions | ||
The default pattern definition file include already patterns for: | ||
- MongoDB, | ||
- MySQL, | ||
@@ -49,10 +58,3 @@ - Nginx, | ||
- various Linux/Mac OS X system log files | ||
- Heroku logs | ||
To test patterns or convert logs from text to JSON use the command line tool 'logagent'. | ||
It reads from stdin and outputs line delimited JSON (or pretty JSON or YAML) to the console. | ||
In addtion it can forward the parsed objects directly to [Logsene](http://sematext.com/logsene). | ||
# Pattern definitions file | ||
The file format is based on [JS-YAML](https://nodeca.github.io/js-yaml/), in short: | ||
@@ -59,0 +61,0 @@ |
Sorry, the diff of this file is not supported yet
58766
283