3 ms·
This is going to sound dumb, but I started dumping all my logs into mysql so that I wouldn't also need to run an elastic search cluster. I then query by the err
by voiper1 10y ago
This is going to sound dumb, but I started dumping all my logs into mysql so that I wouldn't also need to run an elastic search cluster.
I then query by the error level, latency, status code to find items of interest.
And everything is stored by some sort of request ID so that I can correlate multi-entry logs.
It's not pretty -- there's no real-time alerts, but I'm not paying dollars per gb to AWS and I have no clue what google will end up charging... and I'm already running mysql. So there is that...
- packetized 10y agoI'm guessing your log write volume is relatively low.
- deleted 10y ago[deleted]
- bni 10y agoCongrats for choosing the solution with the least moving parts and rejecting premature optimization and over-engineering.
- brightball 10y agoIt's a good solution depending on write volume. Watching the pricing on these logging services is always fairly shocking to me. I've done a similar thing with Mongo in the past with their capped collections.