3 ms·
Having just started to go down the 'log everything centrally' route (to keep track of when third party services are down, what actions User 1234 performed the d
by pbowyer 11y ago
Having just started to go down the 'log everything centrally' route (to keep track of when third party services are down, what actions User 1234 performed the day they reported an issue, and which transactional emails seem to have disappeared), can you explain how I'd change this from logging to metrics & monitoring?
One driver has been the lack of information I've had for debugging production issues (e.g. user X not able to log in against authentication provider Y) and so storing extra info is needed (vs the standard web server logs)
- pbowyer 11y agoThinking further, I guess I'm conflating logging for devops and logging for analytics and logging for audit trails. Not sure how to separate it out without data duplication (the boundaries aren't clear cut?) and for a small system it prob doesn't matter - I'm nowhere near Netflix, PayPal et al for scale.
- jedberg 11y agoA good rule of thumb is that if you can send all your logs to one place and tail -f is still a reasonable way to consume them, just send them all to one place.