4 ms·
You can use whatever system you want (syslog can drop the logs in a single box, no need for horrible tail-based concoctions), as long as you mantain it and it's
by chronid 9y ago
You can use whatever system you want (syslog can drop the logs in a single box, no need for horrible tail-based concoctions), as long as you mantain it and it's not Ops responsibility to fix your AWK scripts that look for events in logs from 3 different services for the same request and the same customer (and/or respond to the alerts those script generate at 2am after Bob forgot to update it to parse correctly a new log message - we have our own fires to fight already).
I'm not saying one should go straight to ELK. There are other ways, but at the end of the day you are going to implement a similar stack, guaranteed, and you are going to regret using freeform logging instead of a sensible structured format.
- flukus 9y agoIt sounds like Ops want all the control but to do none of the work? Maintaining scripts like this is there job.
- chronid 9y agoI'm sorry: it's your application, your alerts, your responsibility. Not Ops.
- flukus 9y agoIf it's my responsibility then I need access to the systems, otherwise I can't perform excercise that responsibility. How does alert creation and maintenance not fall under ops? They sound like the sort of ops people that devops teams were created to replace.