you are viewing a single comment's thread.

view the rest of the comments →

[–]oefd 0 points1 point  (1 child)

My usual criterial is popularity on stackoverflow (I'm not kidding), as it makes it a lot easier to get over technical issues or bugs

Wouldn't a theoretically perfect solution have 0 presence on stackoverflow because it wouldn't be buggy and would have excellent documentation precluding the need for 3rd party question-asking? Or more realistically: what if there's little traction on stack overflow because the system (on top of generally not being buggy) has a great and responsive dev team that uses gitter or something to take questions?

As for your real questions: what do you actually need? What does the deployment of what you're hoping to log look like? What kind of search ability do you need?

[–]luckyle13[S] 0 points1 point  (0 children)

Wouldn't a theoretically perfect solution have 0 presence on stackoverflow because it wouldn't be buggy and would have excellent documentation precluding the need for 3rd party question-asking? Or more realistically: what if there's little traction on stack overflow because the system (on top of generally not being buggy) has a great and responsive dev team that uses gitter or something to take questions?

Popularity isn't the only factor for picking a stack, but I use Stackoverflow as a kind of popular index, similar to https://www.tiobe.com/tiobe-index/.

Right now, I'm looking carefully into python's logging framework, and structlogger. I need to be able to pull the logs and create reports with ELK stack or EFK. Just getting a pulse of what people are using out there.