Service monitoring
It is crucial to consistently monitor your applications and services as it enables you to proactively identify potential issues and recover quickly, minimising downtime and preventing issues from escalating to outages. This also improves user experience and reliability of your applications and services.
Types of monitoring and when to use
There are many types of monitoring that StackOps Elastic supports and this section aims to help you get a high-level understanding of each type of monitoring and when you should use them.
| Monitoring type | Description | When to use |
|---|---|---|
| Synthetic monitoring | Simulates user interactions to proactively identify performance issues before end users notice them. | Assess global availability across regions for critical user workflows. |
| Application Performance Monitoring (APM) | Continuously monitor and manage application performance to quickly detect and address performance issues that may affect business results. | Find performance bottlenecks within critical systems to ensure optimal user experience. |
| Universal profiling | Continuously and comprehensively profile every line of code in your system (including kernel functions and third-party libraries). | Deep dive into your system to identify performance bottlenecks and find inefficient code paths, without code instrumentation. |
| Real User Monitoring (RUM) | Tracks and analyses how real users interact with your system to identify performance issues, providing an actual view of user perception. | Understand how actual users experience your system and measure the real-world impact of changes to your system. |
