In the previous section, you saw how to generate and analyze application logs for your ASP.NET Core 2.0 web applications, which will help you better understand unexpected behavior and application bugs. This will help IT Operations after an event has occurred to trace the different steps until the root cause of a problem has been found.
However, it will not help them to constantly monitor and supervise applications, since using logging mechanisms for this case will result in bad performances and negative overall application impacts. Logging is not the right solution for continuous monitoring!
The goal of monitoring is to analyze and supervise a large number of application metrics in real time, and to automatically detect application anomalies. The metrics need to have a very low message footprint for this to work efficiently.
The most commonly known monitoring frameworks for ASP.NET Core 2.0 are listed here:
- EventSource with ETW, which is very fast, and...