Hi Chris,
It's hard to guess what you are *ing up without the config but it appears
that the enclosing [] might be an issue.
If the JSON payload is all you need then the following could work with
om_tcp:
Exec if $raw_event =~ /\[({.+})\]$/ $raw_event = $1;
Regards,
Botond
On Mon, 4 Aug 2014 13:52:58 -0400
Didjit Charlebois <didji...@gmail.com> wrote:
> Because I'm confused. :-)
>
> Ok, so I got rid of the multiline. Still having issues.
>
> What would be the proper im_out module for NX and input for logstash?
> Originally I thought I could do TCP out from NXLog (no conversion) and
> "PLAIN" input for Loggstash with "JSON" format. Still fails to parse..
> Wondering if its a Character Set issues.
>
> I see a lot of backslashes in the logstash debug, NXDebug is clean of these
> backslashes.
>
>
> [{\\\"start\\\":\\\"2014-08-05T00:00:00.000+0000\\\",\\\"end\\\":\\\"2014-08-05T00:30:00.000+0000\\\",\\\"id\\\":\\\"f264a0e6-cb72-403f-8888-fdfbefcab283\\\",\\\"fullDay\\\":false}]}}]\\r\\n",
>
> Any ideas?
>
> Thank you,
>
> Chris
------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls.
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________
nxlog-ce-users mailing list
nxlog-ce-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nxlog-ce-users
