Building a Centralized Logging Infrastructure
1–9 of 9 posts
Re: Building a Centralized Logging Infrastructure
#2"joecool" and "gentlemanjerry" lol
Good article. My teams frequently had problems with logstash. It's harder to do logging than you'd think.
Re: Building a Centralized Logging Infrastructure
#3"joecool" and "gentlemanjerry" lol Good article. My teams frequently had problems with logstash. It's harder to do logging than you'd think.
Logstash is terrible, i've had so many problems with it.
Re: Building a Centralized Logging Infrastructure
#4Re: Building a Centralized Logging Infrastructure
#5For small deployments, you might be surprised how far you can get with just systemd/journalctl. It even has built in aggregation over a network.
Re: Building a Centralized Logging Infrastructure
#6Splunk?
Re: Building a Centralized Logging Infrastructure
#7Earlier quoted context omitted.
Logstash is terrible, i've had so many problems with it.
what do you prefer?
at aptible - we prefer fluentd. one of our engs talks about the reasons why in the article above, but the tldr is fluentd is extensible like logstash, but far better performance
Re: Building a Centralized Logging Infrastructure
#8Earlier quoted context omitted.
Logstash is terrible, i've had so many problems with it.
what do you prefer?
With logstash I had cases where it was taking more resources than the application that generated the damn logs.
These days i prefer fluentd, but in some cases I let my apps insert directly into ElasticSearch.
Re: Building a Centralized Logging Infrastructure
#9Splunk?
If you're a trillionaire then sure, absolutely :D Splunk is a great tool but oh boy is it ever expensive!