![]() ![]() The following sections describe these scenarios in more detail. There might be others that are less common or are specific to your environment. This document focuses on these scenarios as the most common situations for performing monitoring. This list is not intended to be comprehensive. Tracing operations and debugging software releases.Tracking issues that occur, from initial report through to analysis of possible causes, rectification, consequent software updates, and deployment.Monitoring the day-to-day usage of the system and spotting trends that might lead to problems if they're not addressed. ![]() Tracking the operations that are performed for auditing or regulatory purposes.Protecting the privacy and security of the system, users, and their data.Guaranteeing that the system meets any service-level agreements (SLAs) established with customers.Maintaining performance to ensure that the throughput of the system does not degrade unexpectedly as the volume of work increases.Tracking the availability of the system and its component elements.Ensuring that the system remains healthy.Common scenarios for collecting monitoring data include: Monitoring is a crucial part of maintaining quality-of-service targets. You can use monitoring to gain an insight into how well a system is functioning. You can use this information as a diagnostic aid to detect and correct issues, and also to help spot potential problems and prevent them from occurring. In a production environment, it's important to be able to track the way in which users use your system, trace resource utilization, and generally monitor the health and performance of your system. Distributed applications and services running in the cloud are, by their nature, complex pieces of software that comprise many moving parts. ![]()
0 Comments
Leave a Reply. |