{"id":7190,"date":"2023-11-13T21:07:26","date_gmt":"2023-11-13T20:07:26","guid":{"rendered":"http:\/\/blog.bart.sk\/en\/?p=7190"},"modified":"2024-01-25T12:39:50","modified_gmt":"2024-01-25T11:39:50","slug":"monitoring-applications-nutshell-part-2-need-grafana-alerting","status":"publish","type":"post","link":"https:\/\/blog.bart.sk\/en\/monitoring-applications-nutshell-part-2-need-grafana-alerting\/","title":{"rendered":"Monitoring Applications in a Nutshell – Part 2: Why Do We Need Grafana Alerting?"},"content":{"rendered":"

In the first part of the series of articles entitled <\/b>Monitoring applications in a nutshell<\/b><\/a>, you learned about a presentation tool that displays and analyzes the data necessary for monitoring our web application. In this sequel, we’ll detail how we automate tracking to minimize predictable errors and prevent possible app crashes.<\/b><\/p>\n

The aim of our monitoring is to:<\/span><\/p>\n

    \n
  1. Centralize both server and client workload records<\/b> – We use <\/span>Prometheus <\/b>and <\/span>Cloudwatch<\/b> tools to manage this<\/span> data.<\/span><\/li>\n
  2. Monitor the obtained records in detail<\/b> – Grafana allows us to visualize them based on the data from the first target.<\/span><\/li>\n
  3. Ensure the possibility of process automation <\/b>– <\/span>Alerting<\/b> is one of the tools for automating simple monitoring<\/span>.<\/b><\/li>\n<\/ol>\n

    What is Grafana alerting and how to set it up?<\/b>\u00a0<\/span><\/h2>\n

    In the<\/span> previous article<\/span><\/a>, we defined the most important aspects of performance, load, process, memory and disk monitoring. Data from these monitorings are available on the basis of the aforementioned Prometheus, which together with Cloudwatch is key for alerting.<\/span><\/p>\n

    In short:\u00a0<\/span><\/p>\n