Monitoring and Operations

After connecting multiple ZSphere environments, you can centrally review VM resource usage and alarms in ZCenter, identify resources that need attention and their environments, and take the appropriate action. Monitoring data and alarm records help you understand resource operation. Before changing a resource configuration, confirm the environment to which the target resource belongs.

The monitoring and alarms section explains how to query monitoring data, use optimization suggestions, view alarms, and configure alarm conditions, notifications, and synchronization. The daily operations section covers reports, tags, scripts, and operation records.

Monitoring and Alarms

In ZCenter, you can query VM monitoring data for a selected time range or use optimization suggestions to find VMs that meet specified resource usage conditions. When reviewing an alarm, first identify its source: Resource Alarms displays records generated by ZCenter alarm rules and provides actions for handling them; Platform Alarms displays alarms synchronized from connected ZSphere environments. Check the management node to identify the environment associated with a record.

For existing alarms, open the corresponding records to review their trigger conditions, resources, and occurrence times. To monitor additional resources or metrics, configure alarm rules and add monitoring objects. To send alarms by email or SMS, also prepare message templates, notification servers, and recipients' contact information. Synchronization settings for monitoring data and alarms from connected environments are maintained in Alarm Synchronization.

View VM Monitoring

Query VM resource usage for a specified time range, compare CPU, memory, disk, and network metrics, and export the results as needed.

Before you begin, ensure that the target ZSphere environment has been added and is connected, and that your account has permission to view VM monitoring.

Query Monitoring Data

  1. In ZCenter, choose Platform O&M > System Alarms > VM Monitoring.
  2. Select ZStack ZSphere from Type. To filter by tag, set Tag.
  3. Set the Resource scope. Choose All Resources, or choose Specific Resources and click Select to add the VMs to query. When specifying resources, check the management node to which each VM belongs.
  4. Set Time Range and click Query.

The list displays monitoring results for the selected time range. After changing the resources or time range, click Query again.

Read and Export Query Results

Review average and maximum utilization alongside each VM's CPU, memory, and disk configuration, as well as disk read/write and network traffic metrics. Average values show overall usage during the selected period, while maximum values help identify peaks within that period.

These values are statistics for the selected time range. A - means that no value is displayed for that metric; it should not be treated as zero usage.

To retain the query results, click Export.

View and Configure Optimization Suggestions

Use existing rules to find VMs that need attention, or define time ranges and resource usage conditions suited to your workloads.

Optimization suggestions list VMs that meet a rule's time range and metric conditions, helping administrators evaluate resource configurations. Rules for high-load, low-load, and idle VMs focus on different usage patterns, so review the rule conditions before interpreting the results. Optimization suggestions do not change VM configurations or reclaim resources.

View Existing Rules and Results

  1. Choose Platform O&M > System Alarms > Optimization Suggestions and review the rules in Rule Settings.
  2. Click the target rule name and review its time range, monitoring metrics, comparison conditions, and thresholds.
  3. In the results list, use Management Node, Type, and VM information to locate resources in the target ZSphere environment, and review their configurations and usage.

To retain the results, click Export. A rule can include resources from different environments, so do not identify a target resource by its VM name alone.

Configure Rules for Your Workloads

If existing rules do not meet your needs, administrators with the required permissions can create a custom rule:

  1. Click Create Rule in the rule list.
  2. In the Create Custom Rule window, enter a Name and an optional Description.
  3. Under Management Node, select the ZSphere environments to analyze and set Time Range.
  4. Configure Optimization Metrics as needed. Conditions can include CPU, memory, and disk utilization, as well as ingress or egress bandwidth. Select comparison conditions and enter thresholds based on the high-load or low-usage patterns you want to identify.
  5. Confirm and save the configuration. Return to the rule list and open the rule to view resources that meet its conditions.

To adjust the conditions, select the rule's Edit action, change the management nodes, time range, or metric conditions, and save.

Evaluate Changes Against Workload Needs

Meeting a rule's conditions does not necessarily mean a VM needs adjustment. Consider the workload's operating periods and resource requirements before deciding whether to change its configuration.

View and Handle Resource Alarms

Find resource alarms in a target environment, review trigger conditions and recommended actions, and record how alarms are handled or notify other users.

Resource Alarms displays alarm records generated by ZCenter alarm rules. For alarms synchronized from connected ZSphere environments, see View Platform Alarms from Connected Environments.

Find and View Alarms

  1. Choose Platform O&M > System Alarms > Resource Alarms.
  2. Filter by management node to select the target ZSphere environment, and set filters such as time, alarm severity, processing status, and resource type as needed.
  3. Expand the target alarm record and review the rule name, resource, trigger condition, alarm time, and current status. Confirm the resource that requires attention and its environment.
  4. Review Alarm Details and Recommended Actions, and consider the resource's actual status to determine what to do next.

The page also provides alarm statistics and distributions to help you understand the alarm situation. To retain the records, use Export.

Record How Alarms Are Handled

With the required permissions, you can perform the following actions on alarms that have not been marked as processed or ignored:

ActionInstructions
Mark as ProcessedAfter completing your investigation or response, click Mark as Processed and confirm in the dialog box.
IgnoreIf the record does not require further attention, click Ignore and confirm in the dialog box.
Notify UsersTo request assistance, click Notify Users, select Notification Recipients, and confirm.

Marking an alarm as processed or ignored records how it has been handled; it does not repair the resource or change the alarm's trigger conditions. Check the resource status and monitoring data to determine whether normal operation has resumed.

To notify users by email or SMS, also check the email and SMS notification settings and the recipients' contact information.

View Platform Alarms from Connected Environments

Centrally view alarms synchronized from connected ZSphere environments, identify their sources, and continue investigating in the corresponding environments.

Records in Platform Alarms come from connected environments, providing a centralized view of alarms across those environments. They are displayed separately from Resource Alarms generated by ZCenter alarm rules, with different sources and entry points.

View Alarms and Identify Their Sources

  1. Choose Platform O&M > System Alarms > Platform Alarms.
  2. Use All Management Nodes to filter for the target ZSphere environment. Use All Resource Types to narrow the results as needed.
  3. Review the alarm severity, rule name, resource, and alarm time in the list, and expand a record that needs attention.
  4. In the details, check Triggering Cloud Platform and Management Node, and review the metric conditions to identify the alarm's environment and resource.

Continue Investigating in the Source Environment

After identifying the source, open the corresponding ZSphere management interface and continue investigating with the resource's current status and monitoring data. For access instructions, see Passwordless Redirect to ZSphere.

Configure Alarm Rules

Set monitoring metrics, trigger conditions, and alarm severity for VMs, and add the objects to monitor.

An alarm rule defines when to generate resource alarms, while monitoring objects specify the VMs to which the rule applies. After creating a rule, add monitoring objects on its details page. Before configuring a rule, ensure that the target ZSphere environment and its VMs have been added, and that your account has the required permissions to operate on alarm rules and monitoring objects.

Create an Alarm Rule

  1. Choose Platform O&M > System Alarms > Alarm Rules and click Create Alarm Rule.
  2. Enter a Name and an optional Description, and select Virtual Machine from Resource Type.
  3. Select a Monitoring Metric, set the comparison condition, threshold, and duration in Alarm Rule, and select Alarm Severity. For example, when monitoring CPU utilization, set the threshold and duration according to the workload.
  4. Under Message Templates, select the templates to use when an alarm is triggered, and configure Send Alarm Recovery Notifications as needed. To prepare templates, see Manage Message Templates.
  5. Enter Recommended Actions as needed to provide investigation or response guidance for people reviewing the alarm. This content appears under Recommended Actions in alarm messages.
  6. Click Confirm Creation.

Add Monitoring Objects

  1. Click the rule name in the alarm rule list to open its details page, and select the Monitoring Objects tab.
  2. Click Add Monitoring Objects and select the ZSphere VMs to monitor. Check their management nodes to avoid selecting resources with the same names in other environments.
  3. Confirm and save your selection, then return to the Monitoring Objects tab to check the associations.

Maintain Rules and View Alarms

On the rule's Overview tab, review its metric conditions, alarm severity, and message templates. To make changes, click Update Alarm Rule, edit the relevant settings, and save. To check the monitored resources, switch to the Monitoring Objects tab.

To remove associated VMs, select the target objects on the Monitoring Objects tab, click Remove Monitoring Objects, and confirm. To remove a rule you no longer use, select Delete in the alarm rule list or on its details page, check the rule name, and confirm.

View and handle the resulting alarms in Resource Alarms. For instructions, see View and Handle Resource Alarms. To receive notifications by email or SMS, also complete the email and SMS notification configuration.

Manage Message Templates

View or create alarm message templates, defining email or SMS content for use in alarm rules.

Message templates define the format and content of alarm notifications, while notification server settings provide the service information required to send email or SMS messages. When preparing alarm notifications, first check whether a suitable template already exists. Create or edit a template when you need to include information such as the alarm source, resource, or trigger condition.

View Existing Templates

Choose Platform O&M > System Alarms > Message Templates and click a template name to review its notification method and content. Consider whether the template suits alarm trigger or recovery notifications before selecting it in an alarm rule.

Create a Message Template

With the required permissions, create a template as follows:

  1. On the message templates page, click Create Message Template, enter a Name, and optionally enter a Description.
  2. Select a Notification Method and provide the corresponding information:
    • Email: Enter a Template Name.
    • SMS: Enter an SMS Signature and Template Code.
  3. Enter Template Content. To include actual alarm information in the message, use the available parameters listed on the page, preserving each parameter's complete syntax.
  4. Review the content and click Confirm Creation.

Common parameters include:

ParameterMeaning
${cloudAccountName}Management node, identifying the environment associated with the alarm.
${name}Alarm rule name.
${level}Alarm severity.
${alarmObject}Alarm object.
${alarmDate}Alarm time.
${metricAndCondition}Monitoring metric and threshold.

For example, include Management Node: ${cloudAccountName}; Alarm Object: ${alarmObject}; Trigger Condition: ${metricAndCondition} in the template content to help recipients identify the alarm source and trigger condition.

Use and Maintain Templates

After creating a template, select it in Alarm Rules. To send email or SMS messages, also configure the notification servers and prepare the recipients' contact information.

To change a template, select Edit from its actions menu, update the content, and save. Use Delete to remove templates you no longer use.

Configure Email and SMS Notifications

Configure notification servers to send alarm emails or SMS messages, and check message templates and recipients' contact information.

Alarm notifications use notification servers, message templates, and recipients' contact information together. Before configuring notifications, prepare the email server connection details or SMS service credentials, and ensure that your account has permission to manage notification settings.

Configure an Email Server

  1. Choose System Configuration > Platform Settings > Notification Settings and open the Email Servers tab.
  2. Click Create Email Server.
  3. Enter a Name and Description, and select SMTP for Email Server Type.
  4. Enter Email Server, Email Server Port, Username, and Password. These details must match the email service configuration.
  5. Choose whether to enable Set as Default, click Confirm Creation, and return to the list to check the configuration.

Configure an SMS Server

  1. On the Notification Settings page, open the SMS tab and click Create SMS Server.
  2. Select SMS Service for Type, and enter a Name and Description.
  3. Enter the AccessKey ID and AccessKey Secret provided by the SMS service.
  4. Choose whether to enable Set as Default, click Confirm Creation, and return to the list to check the configuration.

SMS alarm templates also require the corresponding SMS signature and template code. For instructions, see Manage Message Templates.

Check the Information Required for Alarm Notifications

After saving the server configuration, check the following:

  • The alarm rule uses message templates that match the notification method.
  • The recipients' email addresses or mobile phone numbers are correct.
  • When notifying users manually, the intended recipients are selected in the resource alarm's Notify Users window.

After saving the configuration, have recipients check whether notifications arrive. If a notification is not received, check the server configuration, message templates, and recipient contact information.

Configure Alarm Synchronization

Review the monitoring alarm synchronization task and configure synchronization parameters for ZSphere monitoring data and platform alarms separately.

Monitoring alarm synchronization periodically synchronizes monitoring and alarm data from connected environments. Synchronization settings and alarm trigger conditions are maintained separately. To adjust data synchronization, use Alarm Synchronization. Set the metrics, thresholds, and duration for VM resource alarms in Alarm Rules.

View the Synchronization Task

  1. Choose System Configuration > Platform Settings > Alarm Synchronization.
  2. Check the State of the Monitoring Alarm Synchronization task to determine whether it is running or paused.
  3. Click the task name to open its details page. Select Monitoring Management for monitoring data synchronization settings, or Cloud Infrastructure Alarms for synchronization settings for alarms from connected environments.
  4. Locate the ZStack ZSphere row and review its time interval, concurrency, start time, and end time.

Adjust Synchronization Settings

With the required permissions, you can adjust synchronization parameters on each tab separately:

  1. On the task details page, switch to Monitoring Management or Cloud Infrastructure Alarms, depending on which settings you want to change.
  2. Select Set Time Interval for the ZStack ZSphere row.
  3. Set Time Interval to 5 minutes, 15 minutes, 30 minutes, or 1 hour. Set Concurrency as needed to an integer from 1 to 10.
  4. Confirm and save, then return to the corresponding tab to check the parameters.

To control whether the task runs, return to the Alarm Synchronization list, select Start or Stop for the Monitoring Alarm Synchronization task, and check its state.

Check Synchronized Data

When reviewing monitoring data or platform alarms, check the task state and synchronization start and end times to understand synchronization activity. If expected data is missing, first verify the selected environment and query time range, then check the source environment's connection.

To check a source environment, see Manage Connected Environments. View monitoring data in VM Monitoring and alarms from connected environments in Platform Alarms.

Daily Operations

In ZCenter, use reports to organize resource and performance information from connected ZSphere environments, and resource tags to classify and find resources. You can also maintain scripts and VM naming rules for operations and resource provisioning. Resource tags label resources, while system tags and version tags describe the operating systems that scripts support. These tags are maintained separately.

Most features in this chapter are available under Platform O&M > System O&M. To check execution results, use script execution records to track script tasks and their results for each VM, operation logs to review platform operations and background tasks, and messages to view notifications received by the current user.

View and Export Reports

Select a resource, performance, or capacity report to query ZSphere data and export it as needed.

Reports help you gather resource configuration, performance, and capacity information in one place. Perform the following operations in ZCenter with an account that has permission to view the corresponding reports.

Choose a Report

Select a report based on the information you need:

ReportPurpose
VM ReportGather VM configuration information, including names, IP addresses, CPUs, memory, and storage.
VM Performance ReportView average and maximum VM CPU, memory, and disk utilization, as well as disk read and write rates.
Host Performance ReportView host CPU and memory configurations, and average and maximum utilization.
Compute Cluster Resource Capacity ReportView cluster CPU, memory, and disk capacity, including allocated and unallocated levels.

Average and maximum values in performance reports show overall usage and peaks during the selected period. Allocation levels in capacity reports describe resource allocation and do not indicate real-time utilization.

Query a Report

  1. Choose Platform O&M > System O&M, and open the required report under Report Management.
  2. Select ZStack ZSphere from the Management Node drop-down list. This selection filters report data by platform type.
  3. Set the Time range and view the results. Use resource names and configurations to identify the records you need.

Blank values or N/A in a report do not indicate zero usage.

Export a Report

  1. Check the report type, platform type, and time range, and hover over Export to open the export menu.
  2. Select Current Page or All as needed, and save the exported file. All exports all results within the current query.

Manage Resource Tags

Create resource tags, attach them to or detach them from ZSphere resources, and view the associated resources.

Resource tags label resources by business purpose or other categories, making them easier to find and group. This chapter covers resource tags created in ZCenter. The current account must have the required permissions to manage tags and operate on the target resources.

Create a Tag

  1. Choose Platform O&M > System O&M > Tags, and click Create Tag.
  2. Enter a Name, select a Color, and check the preview.
  3. Confirm and save, then check the new tag in the resource tag list.

If a suitable tag already exists, use it directly to tag resources.

Attach or Detach Tags

The following example uses a ZSphere VM. Before proceeding, check the resource's management node to identify its environment.

  1. Find the target VM, open its action menu, and select Attach Tag.
  2. In the tag selection dialog, select the required tags, verify the target resource, and confirm.
  3. Return to the resource list or details page and check the displayed tags.

To remove an association, select a VM that has tags, choose Detach Tag, select the tags to detach, and confirm. Detaching removes the association between the selected resource and the tags. To maintain the tags themselves, return to the resource tag list.

View Associated Resources and Maintain Tags

  1. Click a tag name in the resource tag list to open its details.
  2. Select the Resource Binding tab, and choose a Resource Type to view the associated resources.
  3. To inspect a resource further, open its details and check its environment.

To change a tag's name or color, select Edit in the tag list or details page. To remove a tag that is no longer needed, select Delete, check the name and displayed information, and confirm. Deleting a tag automatically detaches it from all associated resources.

Manage System Tags Used by Scripts

Maintain operating system and version categories so that the corresponding system tags and version tags are available when configuring scripts.

When creating a script, select the applicable System Tag and Version Tag. A system tag identifies an operating system family, such as CentOS, while a version tag identifies a version within that family. These tags are maintained separately from resource tags used to label business resources.

Perform the following operations in ZCenter with an account that has the required permissions to view or maintain system tags.

View Existing Systems and Versions

  1. Choose Platform O&M > System O&M > System Tag, and view existing system tags and their Operating System values.
  2. Click a system tag name to open its details, and select the System Tag tab to view its version tags.

Add a System and Version

  1. Click Create System Data in the system tag list.
  2. Select the Operating System, and enter the System Tag and Version Tag to identify the system and version supported by the script.
  3. Click Submit, then return to the list and check the result.

To add a version to an existing system, open the system's details and click Add on the System Tag tab. Enter the Version Tag and confirm.

Maintain Existing Tags

To change a system tag, select its Edit action in the system tag list. To change a version name, select Edit for the target version on the system details page's System Tag tab, update the Version Tag, and save.

To remove a system or version that is no longer maintained, select its Delete action, check the selected item and displayed information, and confirm. After making changes, check that the system and version selections in the relevant scripts are still correct.

Manage the Script Repository

Find existing scripts, create and maintain custom scripts, and prepare their commands, supported system versions, and execution parameters.

The script repository stores reusable scripts in one place. When preparing a script, specify the operating systems and versions it supports, its command type, interpreter path, and parameters. Perform the following operations in ZCenter with an account that has the required permissions to view or maintain the script repository.

View Existing Scripts

  1. Choose Platform O&M > System O&M > Script Repository, and open the Custom Script or Built-in Script tab as needed.
  2. Review the script names, command types, interpreter paths, and installation package default paths to find a suitable script.
  3. Click a script name to view its supported systems and versions, command, and custom parameters, and check whether it meets your needs.

To write or maintain your own scripts, use the Custom Script tab.

Create a Custom Script

Prepare the script content and the interpreter path, working directory, and parameters required by the target system. If the required system or version is not available, first see Manage System Tags Used by Scripts.

  1. Click Create Script on the Custom Script tab, and enter a Name and Description.
  2. Select the applicable System Tag and Version Tag. If you change the system tag, select the corresponding version again.
  3. Configure the script using the following descriptions.
    SettingDescription
    Command TypeSelect Shell, PowerShell, Python, or CMD according to the script.
    CommandEnter script content that matches the selected command type.
    Custom ParameterAdd parameter names, values, and descriptions as needed so that users can identify each parameter's purpose.
    Interpreter Absolute PathEnter the absolute path of the interpreter on the target system. The interpreter must match the command type.
    Installation Package Default PathEnter the working directory used by the script process.
  4. Check the configuration, click Confirm, and return to the list to check the new script.

Maintain and Select Scripts

To modify a custom script, select Edit in the list or details page, check the supported systems, command, and parameters, and save. To remove a custom script that is no longer needed, select Delete, check the name and displayed information, and confirm.

When preparing scripts for a ZSphere service catalog, select the allowed Script Set in the catalog's Script Configuration step. Whether this step appears depends on the script associations of the selected images. Check the scripts and parameters against the target image and operating system.

View Script Execution Records

Find existing script tasks and view their executors, execution times, and results for each VM.

Execution records track existing script tasks. To view a script's content and supported systems, use the Script Repository. Perform the following operations in ZCenter with an account that has permission to view script execution records.

Find an Execution Task

  1. Choose Platform O&M > System O&M > Execution Record.
  2. Find the required record by task name, operating system, executor, and execution time, and check its Execution Status.
  3. Click the record name to open its details. On the Overview tab, check the script name, operating system, executor, and execution date.

View Results for Each VM

  1. Select the Execution Result tab in the task details, and find the VM to inspect.
  2. Check the VM's Action Result, click View Details, and review the start time, completion time, and execution output.
  3. To inspect the VM itself, click its name to open the resource details, and check its ZSphere environment and current status.

If a task includes multiple VMs, check each VM's result. Use the execution output and the target resource's actual state to determine whether the operation achieved its intended result.

Configure VM Naming Conventions

Prepare reusable VM naming rules, configure machine names and hostnames separately, and select the rules in the service catalogs that need them.

Naming conventions let you maintain name generation rules in one place. A machine name identifies a VM on the platform, while a hostname identifies it within the guest operating system. Configure each separately using built-in macros or by adding custom text to the selected macros.

Perform the following operations in ZCenter with an account that has the required permissions to view or maintain naming conventions. After creating a rule, select it in the relevant service catalog configuration.

View Existing Rules and Built-in Macros

  1. Choose Platform O&M > System O&M > VM Naming Convention.
  2. On the Naming Rule tab, review existing rules, including their machine name policies, machine names, hostname policies, and hostnames. Click a rule name to view its detailed configuration.
  3. To view available macros, switch to the Built-in Macro tab and review their names, macro values, and remarks.

Create a Naming Rule

  1. Click Create Naming Convention on the Naming Rule tab, and enter a rule Name.
  2. Configure Machine Name Policy: select Built-in Macro or Custom Extension, then select a Machine Name Macro Value. For macros that require parameters, set the random string length or number of IP address segments as prompted.
  3. Check the generated Machine Name. If you use Custom Extension, keep the selected macro intact and add the required text before or after it. Set a Machine Name Suffix and Machine Name Remark as needed.
  4. Configure Hostname Policy and Hostname Macro Value, check the Hostname, and enter a Hostname Remark as needed. Choose from the macros available in the hostname list.
  5. Check both name configurations, click Confirm Creation, and return to the list to check the new rule.

Select a Rule in a Service Catalog

When configuring images for a ZSphere service catalog, check each image's Associated Script value. If any selected image has this value set to Yes, the wizard includes the Script Configuration step.

In this step, set Rule Configuration to Select Rule, then select the required Naming Rule for the service catalog. Selecting Set Manually does not use a naming rule.

Maintain Existing Rules

To modify a rule, select Edit in the list or details page, check the policies, macro values, and custom text for both the machine name and hostname, and save. Verify the configuration after saving. To remove a rule that is no longer needed, select Delete, check the rule name and displayed information, and confirm.

View Operation Logs and Background Task Logs

Query platform operations and background tasks, check their target resources, operators, times, and results, and export logs as needed.

After operating on connected ZSphere resources in ZCenter, use logs to track execution. The current account must have permission to view the corresponding logs.

Choose a Log Type

Choose Platform O&M > System O&M > Operation Logs, and select a tab based on what you need to check:

TabPurpose
Platform Operation LogsCheck which operation was performed, the resource involved, who initiated it, the login IP address, start and completion times, and the operation result.
Backend Job LogTrack background task status, operators, and start and end times, and view task details.

Logs track the execution process. To check a resource's final state or configuration, also verify it in the resource list or details page.

Find and View Records

  1. Open the required tab, and set the query time range.
  2. Find records by operation time and operator, and filter by Operation Result as needed. On the Platform Operation Logs tab, you can also search by resource name or operation description.
  3. Click the target record's Operation Description to view operation or task details and check execution.
  4. If an operation fails, read the failure information in the details, then check the target resource's environment, connection status, and specified configuration.

For resources with the same name, use the operation time, operator, and resource details to confirm the target.

Export Logs

  1. Select the time range to export on the required log tab.
  2. Click Export. In the Export Logs dialog, check the Time Range and CSV export format.
  3. Confirm the export and save the file.

Before exporting, check that the time range in the dialog covers the operations you need to retain.

View Message Notifications

View messages received by the current user, review the relevant information, and maintain their read status.

The message list displays notifications received by the current user. Use the subject, type, and submission time to find items that need attention. Types such as Ticket Message and Alarm Message distinguish notification content. Handle the related business activities on their corresponding pages.

Find and Read Messages

  1. Choose Platform O&M > System O&M > Message.
  2. Set the time range as needed, and use the read and unread filters under Subject to find records. Check the message type and submission time to identify the target message.
  3. Expand a message to read its details. Expanding an unread message marks it as read.

Mark Messages on the Current Page as Read

After checking the messages on the current page, click Mark Current Page as Read to mark its unread messages as read. This action applies only to the current page and does not mark unread messages on other pages.

A read status indicates that the message has been read. It does not mean that the related request, alarm, or other matter has been handled.