submitted 2 weeks ago by [email protected] to c/[email protected]
top 50 comments
sorted by: hot top controversial new old
[-] [email protected] 16 points 2 weeks ago

The middle thing is not what normies do, it is what enterprises do, because they have other needs than just knowing 'error where?'

[-] [email protected] 3 points 2 weeks ago

Do folks still use logstash here? Filebeat and ES gets you pretty far. I've never been deep in ops land though.

[-] [email protected] 5 points 2 weeks ago

Please excuse my ignorance, but what is grep, what are the do's and dont's of logging and why are people here talking about having an entire team maintain some pipeline just to handle logs?

[-] [email protected] 9 points 2 weeks ago

It's a command line tool which filters for all lines containing the query. So something like

cat log.txt | grep Error5

Would output only lines containing Error5

[-] [email protected] 1 points 2 weeks ago

or if its a complex error cat log.txt|grep keyword1|grep keyword 2 and so on.

[-] [email protected] 9 points 2 weeks ago

You can just do

grep Error5 log.txt
[-] [email protected] 12 points 2 weeks ago

In the back of my mind I know this is there, but the cat | grep pattern is just muscle memory at this point

[-] [email protected] 2 points 2 weeks ago

for me as well.

[-] [email protected] 3 points 2 weeks ago

Just remember that if you aren't actually concatenating files, cat is always unnecessary.

[-] [email protected] 3 points 2 weeks ago

I've been 'told off' so many times by the internet for my cat and grep combos that I still do it, then I remove the cat, it still works, and I feel better. shrug

[-] [email protected] 19 points 2 weeks ago

...or as I've come to call it grep+linux

[-] [email protected] 14 points 2 weeks ago

As someone who used to troubleshoot an extremely complex system for my day job, I can say I've worked my way across the entire bell curve.

[-] [email protected] 17 points 2 weeks ago

What the fuck is center even talking about? Is that shit a thing people do?

[-] [email protected] 13 points 2 weeks ago* (last edited 2 weeks ago)

Yeah, ofc it is.

I'm working in a system that generates 750 MILLION non-debug log messages a day (And this isn't even as many as others).

Good luck grepping that, or making heads or tails of what you need.

We put a lot of work into making the process of digging through logs easier. The absolute minimum we can do it dump it into elastic so it's available in Kibana.

Similarly, in a K8 env you need to get logs off of your pods, ASAP, because pods are transient, disposable. There is no guarantee that a particular pod will live long enough to have introspectable logs on that particular instance (of course there is some log aggregation available in your environment that you could grep. But they actually usefulness of it is questionable especially if you don't know what you need to grep for).

These are dozens, hundreds, more problems that crop up as you scale the number of systems and people working on those systems.

[-] [email protected] 3 points 2 weeks ago

This write-up can be the next KRAZAM skit

[-] [email protected] 12 points 2 weeks ago

A good chunk of it is relating to the elastic search stack, yeah it's a thing people do.

[-] [email protected] 4 points 2 weeks ago

My life got so much better after we abandoned elasticsearch at work

[-] [email protected] 16 points 2 weeks ago

Why grep log files when I can instead force corporate to pay a fuck ton of money for a Splunk license.

[-] [email protected] 3 points 2 weeks ago

It's such an insane amount of money

[-] [email protected] 0 points 2 weeks ago
load more comments
view more: next ›
this post was submitted on 24 May 2024
383 points (98.0% liked)

Programmer Humor

31029 readers
351 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)


founded 4 years ago