kidwellj/findcommonground.uk
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

Kramdown syntax driving me nuts

Browse source
This commit is contained in:
Holger Reinhardt 2016-02-03 14:53:23 +01:00
parent cb0e2d76c0
commit d8931a832e
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
_posts/2016-01-18-fluentd-log-parsing.md
View file

@ -26,7 +26,7 @@ The simplest approach is to just parse all messages using the common denominator
In the case of a typical log file a configuration can be something like this (but not necessarily): In the case of a typical log file a configuration can be something like this (but not necessarily):
~~~ xml ~~~ xml
<source> <source>
type tail type tail
path /var/log/test.log path /var/log/test.log
@ -38,7 +38,7 @@ In the case of a typical log file a configuration can be something like this (bu
#a timestamp in front of it, the rest is just stored in the field 'message' #a timestamp in front of it, the rest is just stored in the field 'message'
format1 /(?<time>\d{4}-\d{1,2}-\d{1,2} \d{1,2}:\d{1,2}:\d{1,2},\d{3}) (?<message>(.|\s)*)/ format1 /(?<time>\d{4}-\d{1,2}-\d{1,2} \d{1,2}:\d{1,2}:\d{1,2},\d{3}) (?<message>(.|\s)*)/
</source> </source>
~~~ ~~~
You will notice we still do a bit of parsing, the minimal level would be to just have a multiline format to split the log contents into separate messages and then to push the contents on. You will notice we still do a bit of parsing, the minimal level would be to just have a multiline format to split the log contents into separate messages and then to push the contents on.