4 ms·

>> How do you ship logs? UDP? TCP? TLS? > Yes ;) ok, missed it, checked again. UDP, TCP - yes. TLS - not yet? I checked tutorial, nothing there. Since most [

>> How do you ship logs? UDP? TCP? TLS? > Yes ;) ok, missed it, checked again. UDP, TCP - yes. TLS - not yet? I checked tutorial, nothing there. Since most [semi]serious projects have a least some servers, I suggest to add a separate example, smth like: 1. We have 5 servers. And we collect logs to server 6. 2. These are settings you need to use for 5 servers. 3. And these are settings you need to use for the collector [IP:Port:TCPwithTLS]. > Dendrite scrapes your existing logs Does Dendrite tail? Can Dendrite consume/scrape some existing/old log files? BTW, what was your actual max throughput? Did you use some internal queue in the design, like rsyslog is doing? > Dendrite isn't trying to be Logstash. I'd like dendrite to be the agent you use with logstash, greylog, papertrail, or whatever. I am confused here a bit. So Dendrite is like StatsD on steroids?

fizx 13y ago
> ok, missed it, checked again. UDP, TCP - yes. TLS - not yet? tcp + tls is a one-liner I haven't added > Does Dendrite tail? Can Dendrite consume/scrape some existing/old log files? Yes, dendrite tails/follows, with optional backfilling. > Did you use some internal queue in the design, like rsyslog is doing? Since you're using existing logs, all we do is maintain a pointer into the logs on disk. When we start consuming more transient data (e.g. perhaps we poll jmx for you), we'll have to add the queue. > I am confused here a bit. So Dendrite is like StatsD on steroids? Dendrite is "tail -f *.log | convert_to_json.pl | nc" on steroids.