Trying to transform a strange data format

I've got some data that comes in with a somewhat unusual format.  It's a set of fixed fields, followed by a variable length set of keys, followed by a set of values.  It looks something like this (but with more fields):

col1, col2, col3, description(key1; key2; ...;keyn), val1, val2, ..., valn

I'm trying to transform this into something more like:

a=col1, b=col2, c=col3, key1=val1, key2=val2, ..., keyn=valn

AskedAugust 24, 2015 - 11:11pm

short messages truncated to 64 chars

Hello there!

I am using nxlog for tailing specific files (im_file) and output them via GELF_TCP to Graylog which goes good except 1 thing > short_messages get truncated to 64 chars which, if I understand right, is related to this directive (or I might be wrong):

AskedAugust 24, 2015 - 7:02pm

Problem with UNC Path and Domain User

I have a client who wants to use Loggly with NXLOG using UNC Paths to shared servers instead of absolute paths but has hit a road block.

Instead of using something like this: C:\files\logs\mylog.txt

He wants to do something like this: \\computername\windowsshare\c$\mylog.txt

When he has the nxlog service set to Local System and points to an absolute path to a local file it works fine.

AskedAugust 22, 2015 - 12:33am

Universal schedule block that rotates all logs?


I have several routes, outputs, and inputs and would like to have a schedule block that effects all logs. Is this possible? My current implementation is to put the schedule block in each Output. It works, but I was seeing if there was a way to clean it up and get it into one scheduler.

Thank you!

AskedAugust 20, 2015 - 5:06pm