Every developer for themselves because the devops guy.
Ask HN: How do you manage logs for your backend services?
31–40 of 142 posts
Re: Ask HN: How do you manage logs for your backend services?
#32If it's small, text files that you rotate per day and delete after 1-3 month(s).
If it's big, Graylog is great.
If it's too big, /dev/null, best logs gathering since 1971.
Re: Ask HN: How do you manage logs for your backend services?
#33LogDNA is best and it's cheap enough you don't have to worry about it.
Re: Ask HN: How do you manage logs for your backend services?
#34We use https://www.humio.com/ and we love it
Re: Ask HN: How do you manage logs for your backend services?
#35Nobody mentioning Splunk? Too obvious or am I not understanding the ask?
I’ve heard from different people that is trapware. You getting it, investing time and building process around it. And when you starting to get valuable amount of data your bill grow to the deep space. The same time they said that it is good, but very expensive.
Re: Ask HN: How do you manage logs for your backend services?
#36fluentd is great. You can setup forwarding nodes, that relay logs to one or mutiple masters that then persists into whatever layer(s) you want. Tolerance and failover baked in. Tons of connectors and best of all docker logs driver is built ships with docker so almost zero setup to get your container logs to fluentd. Also works nicely with kubernetes too!
I haven't used it in maybe 3 years or so, so some of this could be misremembered a bit, but I didn't have a great experience with fluentd. Trying to do much customization was kind of painful, the config file structure is kind of confusing and the docs were sparse and differ depending on the plugin you're using, and there's no validation of the config so if you have any of the arguments slightly wrong it'll fail silen…
Despite their advice not to write a lot of Ruby code, the fluentd plugins are Ruby code, so I ended up just writing one big custom plugin with all the rewrite/routing logic in it. It was very simple to do, and so much easier to read than the convoluted fluentd config files you end up with to do anything mildly complicated with filtering.
Re: Ask HN: How do you manage logs for your backend services?
#37I used Papertrail at my last job, search function works well, and it was easy to use.
Seconding Papertrail. I don't love it but it works and it's cheap enough and I don't need to love every tool I use.
I do constantly wonder if there's a logging/searching solution small and lightweight enough to fit on the cheapest DO droplet. $7/gb/mo on Papertrail vs $5/mo with a 25GB SSD? That'd be a no-brainer, but ELK and Graylog won't run with that low of hardware.
Re: Ask HN: How do you manage logs for your backend services?
#38Nobody mentioning Splunk? Too obvious or am I not understanding the ask?
I’ve heard from different people that is trapware. You getting it, investing time and building process around it. And when you starting to get valuable amount of data your bill grow to the deep space. The same time they said that it is good, but very expensive.
Splunk is great but very expensive, like you mentioned. They're actively getting disrupted by Sentinel and Backstory and Elastic though, so either pricing will change or the recommendation will change.
Re: Ask HN: How do you manage logs for your backend services?
#39We used Sumologic for a long time and still do. You can query your logs in an SQL-way (you can do joins for instance) and last I checked they have a free tier.
Re: Ask HN: How do you manage logs for your backend services?
#40I used logdna in a previous company. This is a really nice hosted, cheap logging service (like papertrail)