Keeping track of what is going on takes time. There are plenty of monitoring tools that help you out. Good monitoring tools help you discover problems before customers are even bothered by them. Staying ahead of the curve.
You can monitor not only the health and performance, but also whether exceptions occur in your code. But also more low level monitors exist that beep you when disk is running low.
Below some links
Enjoyed this? Follow me on Mastodon or add the RSS, euh ATOM feed to your feed reader.
Prometheus is a statistics collecting tool that originated from SoundCloud. Designed to be used in high performance environments, it is build to be blazingly fast. Hence, the client typically is expected to be blazingly fast as well, gathering and presenting data within nanoseconds. For Ruby on Rails applications however this has lead to an unresolved issue with the Prometheus ruby-client when the same application is forked (typical for Puma, Passenger and other popular ruby-servers). The Prometheus client collects data within its own fork before serving it to the exporter endpoint. This can or cannot be a problem. When you measuring response times, running averages from a random fork may be good enough. However, when you're also counting data over time you're having separate counters in …
Dit artikel van murblog van Maarten Brouwers (murb) is in licentie gegeven volgens een Creative Commons Naamsvermelding 3.0 Nederland licentie .