Introduction to MCT (Monitoring Console Tool) ¶
MCT (Monitoring Console Tool) is a centralized configuration but globally distributed Synthetic Check system used for monitoring Webex services. It is designed to provide a global view of the system's health and performance, with the ability to configure and monitor multiple instances across different locations. The tool collects data from various sources and provides real-time visibility into the system's healthy status.
The MCT architecture comprises two layers. The central layer is primarily responsible for target configuration, task distribution, and result persistence and visualization. It includes Web Service, API Service etc. On the other hand, the distribution layer takes the responsibility of task execution and the return of results. It includes Dispatcher, Agents, and Monitors. This robust structure ensures an efficient and effective monitoring process.
flowchart TB
Central-Cluster --> Worker-Cluster-A
Central-Cluster --> Worker-Cluster-B
Central-Cluster --> Worker-Cluster-C
Use Cases ¶
flowchart LR
Definition --> Registration --> Monitored --> Decommission
Monitored --> Notification --> Monitored
Definition ¶
The Definition phase is where the monitoring journey begins. In this phase, users define the scope and parameters of the synthetic checks they want to conduct. This involves specifying the target application or service, determining the user interactions to be simulated, and configuring the expected behavior and performance thresholds. For complicated scenarios based monitoring behavior, requester maybe needs to contact with an MCT developer to discuss a proper monitoring solution.
Means there should be a monitor map including a check type and location
Registration ¶
Once the checks are defined, they need to be registered within MCT. During this phase, users set up the necessary checks with proper configurations, and suitable intervals. MCT provides a user-friendly interface and yaml file repository to streamline the process of registering checks, enabling users to create dynamic and accurate simulations of user interactions.
In Manual mode, it will apply on ad-hoc scenarios, and also in manual adjustment after setup.
Besides the definition of observation target, users of MCT also need to provide Service Impact Rule to call out failures with proper policies and notifications receivers.
Monitored ¶
The Monitored phase involves the actual execution of synthetic checks. MCT orchestrates the scheduled simulations across different locations and environments. The tool records response times, interactions, and outcomes, generating detailed reports that highlight deviations from expected behavior. These reports offer insights into performance trends, allowing organizations to pinpoint and address potential issues promptly.
Notification ¶
In the Notification phase, MCT ensures that relevant stakeholders are informed of any deviations from expected performance. The tool can be configured to send alerts, notifications, or reports to designated recipients via various communication channels. This proactive approach empowers organizations to respond swiftly to emerging issues, thereby minimizing the impact on end-users.
Decommission ¶
This is the phase for service owners to remove retired monitoring targets from MCT. That will reduce the noise from useless services, and also save energy to run the services.