Hacker News Reader

IMO it is not as widespread because it isn't a good practice. Health monitoring, metrics and logging are orthogonal and really should be handled separately. Monitoring makes sure everything is working properly, metrics is about understanding how it is being used, and logging is about peering inside what is happening. Conflating them hinders their application and makes them less useful.

View on HN

I like the seperation of concerns, do you have an example of conflating these that leads to issues?

When a customer complains that something's not right, and you check your logs, and the logs have been spewing millions of alarming messages for hours that you wish you had seen before the customer noticed issues, that's when you wish the programmer who wrote the log lines had used the health monitoring framework instead of the logging framework.

> health monitoring framework instead of the logging framework.

What is the difference?

Can you just extract metrics from logs via ES. Logstash even has a prebuilt JAVASTACKTRACEPART for java exceptions.

That user/dev error, not a fault of the system or a problem in handling it all with the same.

Metrics can always be generated from logs, especially structured payloads.

Reply on news.ycombinator.com