What *nix commands ca be used to send log-events to rTail Server ?

[chilcano]

Hello Kilian,
I can't see any log-events in browser when using multitail instead of tail to send to rTail Server.

Seems that multitail adds hidden chars to log-events that rTail Server can't read.
I am using this command:

$ multitail -l "ping 8.8.4.4" | rtail --id ping1 --host 192.168.99.100 --port 9191 --no-parse-date

In the rTail Server (browser) I can't see anything.
Any idea?.

Regards.

[kilianc]

Hey @chilcano thanks for contributing, in general everything that outputs something can be piped into rtail, run this test:

$ yourcommand > test.txt

what you see in the file should go in rtail as well.

I don't know the details of implementation and usage for multitail but for example with grep I often need to turn buffering off.

try DEBUG=rtail:* rtail-server to check if messages are coming in.

Let me know if this helps.

[chilcano]

I have verified that multitail can't be piped to rTail because multitail adds special chars before every line. That's the reason that rTail Server doesn't receive any log-event.
I've used netcat to check it.

$ multitail -l "ping 8.8.4.4" | netcat -vu 192.168.99.100 --port 9192

In other server the netcat is listening on 9192 UDP port. This netcat shown the log-events but before clean the screen and update the Terminal title, etc.

Regards.

[kilianc]

@chilcano rtail-server splits by newline, it's very stupid regarding what gets in. it should grab every new line. If multitail doesn't use newlines that's ok.

I would have agreed if the output on rtail client was messy because of the extra ANSI chars but not seeing anything at all is not correct.

Another test:

$ multitail -l "ping 8.8.4.4" > test.log
$ cat test.log | rtail

does it work ?

[chilcano]

It didn't work.

Thanks.

[kilianc]

Interesting, I'll leave this open and check it out myself, I am curious now :)