NXLOG JSON Output to FluentD

[Kyle]

Has anyone had any success in outputting JSON format via NXLOG to FluentD successfully?

It really seems to be hit or miss for me and most of the time in the NXLOG I will get an error: ERROR HTTP response status is not OK: 400 Bad Request

My ultimate goal is to natively export JSON format to FluentD. If there are other more stable agents that someone could recommend that work and will allow tailing files and sending that via JSON as well, would really appreciate the information.

If anyone has a working config or can point me in the right direction, would greatly appreciate it.

Thank you,

Kyle

[Kiyoto Tamura]

Hi Kyle

What's your input on Windows? If it is Fluentd's protocol over TCP (as in, using fluent-logger), then you might want to look at github.com/fluent/fluentd-forwarder

If not, still let me know what it is, and we can think of a workaround.

--
You received this message because you are subscribed to the Google Groups "Fluentd Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fluentd+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Check out Fluentd, the open source data collector to unify log management.

[Kyle Kniffin]

On the Windows Servers my input is the Built-in eventlog and some DHCP/IIS Log Files.

I tried using something similar to the following config at the URL but that is where it only works hit/miss. Mainly I get the ERROR HTTP response status is not OK: 400

http://qiita.com/inokappa/items/b17e18e275a7c60a3222

--
You received this message because you are subscribed to a topic in the Google Groups "Fluentd Google Group" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/fluentd/3LRxDYqHNi8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to fluentd+u...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Thanks,

Kyle Kniffin
ky...@kniffins.com

[Kiyoto Tamura]

Kyle-

I see. You can also try running the Windows branch of Fluentd itself: https://github.com/fluent/fluentd/tree/windows

Beware that the Windows branch is highly experimental, and it tends to lag several months in terms of merging changes from the master.

[Kyle Kniffin]

Is there any options of getting nxlog to work with Fluentd over JSON properly as in the link I sent in my last email?

NXLog seems to be the most widely used for transporting windows logs.

[Mr. Fiber]

This is not my nxlog configuration but

one Fluentd user uses NXLOG and in_http with following configuration.

https://gist.github.com/kan6004/8fc90bec059515e081bf

[Sebastian Krohn]

On Thursday, November 27, 2014 1:46:17 AM UTC+1, repeatedly wrote:

This is not my nxlog configuration but

one Fluentd user uses NXLOG and in_http with following configuration.

https://gist.github.com/kan6004/8fc90bec059515e081bf

 

I based my config on that but ran into the same issues as Kyle. I got it to work after adding more substitutions to do some crude url encoding:

https://gist.github.com/dramaturg/e07064b67a474e67a2d6

The fluentd side of things is a normal in_http:

<source>

  type http

  port 8888

</source>

Cheers,

   Sebastian

[Kyle Kniffin]

Thanks, I will try that out.

[Kyle Kniffin]

Sebastian,

What version of fluentd are you running? Still getting http 400 bad request when using your config as well.