Observability

Observability aggregates resource, metric, log, alert, and health data from connected components. It helps users view running status from global, component, and resource perspectives, and supports operations analysis and report generation.

Before using observability capabilities, connect infrastructure components through Cloud Federation and enable resource, metric, or log collection as needed. After access and collection are configured, users can view data at different levels through Home, Platform Health, dashboards or custom dashboards, views, reports, Assets, Infrastructure, Metrics Explorer, Log Explorer, collection configuration, and alerts and notifications.

If a page does not show expected data, first check whether the corresponding component is connected, whether collection is enabled, and whether the latest collection or synchronization is normal.

Observability Data Visibility

Observability data is automatically filtered by the current signed-in identity, management view, and resource permissions. Switching pages, query conditions, or management views does not expand the data scope available to the current account.

Identity	Data Available	Content Not Shown
Platform administrator	Cross-component observability data within the administrator's permitted scope in Global Management.	Data for regions, components, or resources for which the administrator has no permission.
Tenant administrator	Observability data and tenant-scoped reports for the tenant and its associated resources.	Other tenants' data, platform-level infrastructure data, and underlying collection configurations.
Standard tenant user	Metrics and alarms for resources the user is authorized to access.	Other resources, tenant-scoped reports, platform-level configurations, and underlying collection paths.

Core Concepts

Before using Observability, learn the following concepts about data sources, analysis views, and collection configurations:

Concept	Description
Data Source	A component or environment that is connected through Cloud Federation and has collection enabled. Resource, metric, and log data on observability pages depends on the connection scope and collection configuration.
Dashboard	A visualization page that displays resource health, capacity, performance, and asset status. Users can use preset dashboards or create custom dashboards by combining frequently used views.
View	A reusable chart or data display unit for viewing resources and metrics from a specific perspective.
Report Template	A template that defines report content and generation method. It can be used to generate operations reports on demand or on a schedule.
Generation Record	A historical record generated after report generation. It is used to view generation results and download generated report files.
Metric	Numeric data that describes resource running status, such as CPU, memory, capacity, network, or service status.
Log	Runtime, operation, or audit text records from connected components. Logs are used for troubleshooting, anomaly diagnosis, and operation traceability.
Asset	A resource object synchronized to ZCF, such as a physical host, VM instance, container resource, or storage resource.
Platform Health	A health summary of ZCF key platform services, health domains, component details, and external dependencies. It is used to identify control plane, data path, and capacity risks.
Health Domain	A grouping view for platform health checks. It groups check items by core services, monitoring collection, alert evaluation, notification chain, capacity risk, and basic dependencies to help users identify the impact area of an issue.
Alarm Center	The entry for viewing alarm messages and managing alarm rules, notification channels, notification policies, and message templates.
Collection Configuration	A configuration that controls the collection scope of resource, metric, and log data. After collection is configured correctly, related data becomes available for queries, dashboards, and reports.

Access Observability Pages

After switching to Global Management in the upper-right corner of the main menu, use the following pages for ZCF Observability tasks. Different pages serve different operations tasks: Home is used for quick checks, Dashboards & Reports is used for detailed analysis, and Operations is used to view platform health, query metrics and logs, manage collection configurations, and handle alerts.

Page	Purpose
Home	View resource scale, health status, capacity usage, and performance status of connected components. This page is suitable for daily checks and overall environment review.
Dashboards & Reports	View global or component-level dashboards, create and maintain custom dashboards, views, and report templates, and generate reports on demand or on a schedule.
Operations	View platform health, including key services, health domains, component details, and external dependencies. Query metrics and logs to analyze performance trends, resource exceptions, and key logs. View assets and infrastructure to understand resource inventories, resource structures, and capacity distribution of connected components. Manage resource, metric, and log collection configurations, and track risks, configure rules, and manage notifications in Alarm Center.

Note: Observability data depends on component connection and collection configuration. If a page has no data, check whether the related component is connected through Cloud Federation and whether resource, metric, or log collection is enabled.

Configure Data Collection

Resource, metric, and log data are the basis of observability analysis. Enable the required collection items when connecting components through Cloud Federation. After access is complete, use the collection pages to check collection status, synchronization results, and collection configurations, and adjust collection policies when data is missing or the collection scope changes.

Configure Resource Collection

Before configuring resource collection, make sure the following conditions are met:

The target component is connected to ZCF from the Platform Access list or area under Cloud Federation > Platform Management, and connection verification is complete. Resource collection was selected during access, or resource collection has been enabled later in platform configuration.
The current account has the required Cloud Federation and resource collection permissions.

Resource Collection is used to maintain the resource synchronization scope of connected components and view resource synchronization status. After resource collection is normal, Assets, Infrastructure, Dashboards, and Reports can display the corresponding resource data.

In the upper-right corner of the main menu, switch to Global Management.
Go to Operations > Unified Assets > Resource Collection.
Confirm whether resource collection is enabled for the target component.

If the page indicates that a connected component has not enabled resource collection, go to Cloud Federation > Platform Management, open the target component access or configuration page from the Platform Access list or area, and select resource collection.

Select the target component from the platform list and view resource collection status.

Operation	Description
View synchronization status	View resource count, synchronization status, latest synchronization time, and synchronization frequency for a connected platform.
View results by resource type	Check synchronization results by resource type to determine whether specific resource data has been collected correctly.

Adjust resource collection configuration as needed.

Operation	Description
Select Resources to Collect	Select the resource types to synchronize to ZCF. Related pages display data only for selected resources.
Set Synchronization Frequency	Set the automatic synchronization interval for resource data. A higher frequency keeps data fresher but increases collection pressure.
Synchronize Resources Manually	Manually trigger resource synchronization when resource data needs to be refreshed immediately.
Stop Resource Collection	Stop resource synchronization for the target component. After collection is stopped, related pages no longer update resource data for that component.

Note: After adjusting resource collection configuration, go to Assets, Infrastructure, Dashboards, or Reports to confirm whether resource data meets expectations.

Configure Metric Collection

Before configuring metric collection, make sure the following conditions are met:

The target component is connected to ZCF from the Platform Access list or area under Cloud Federation > Platform Management, and connection verification is complete. Metric collection was selected during access, or collection has been added later on the Metric Collection Management page.
The target component supports metric collection, and the current account has the required Cloud Federation and metric collection permissions.

Metric Collection Management is used to view and maintain metric collection status for connected components. After metric collection is normal, Metrics Summary, Metrics Explorer, Dashboards, and Reports can display corresponding metric data.

In the upper-right corner of the main menu, switch to Global Management.
Go to Operations > Monitoring Center > Metric Collection Management.

If metric collection is not enabled for the target component, add a collection configuration.

If metric collection was not selected when the component was connected, you can enable it on this page by adding collection.

Operation	Description
Select Platform	Select the connected component whose metrics need to be collected. If no component is available, go to Cloud Federation > Platform Management first, and use the page entry in the Platform Access list or area.
Add Collection	Enable metric collection for the selected component so that its metric data can be used in Metrics Explorer, Dashboards, and Reports.

View metric collection status.

Operation	Description
Collection Status	Confirm whether metric collection is normal for the target component.
Update Time	Confirm the latest update time of collection information to determine whether metric data is continuously updated.
Delete Collection	Stop collecting metrics from the target component. After collection is stopped, related pages no longer update metric data for that component.

Note: If dashboards or Metrics Explorer lack metric data, first confirm that metric collection status is normal, and then check the target component connection status.

Configure Log Collection

Before configuring log collection, make sure the following conditions are met:

The target component is connected to ZCF from the Platform Access list or area under Cloud Federation > Platform Management, and connection verification is complete. Log collection was selected during access, or collection has been added later on the Log Collection Management page.
The target component supports log collection, and the current account has the required Cloud Federation and log collection permissions.
If the target component requires audit or log output to be enabled first, complete the configuration according to the component requirements.

Log Collection Management is used to view and maintain log collection status and collection targets for connected components. After log collection is normal, Log Summary, Log Explorer, and Live Tail can display corresponding log data.

In the upper-right corner of the main menu, switch to Global Management.
Go to Operations > Log Center > Log Collection Management.

If log collection is not enabled for the target component, add a collection configuration.

If log collection was not selected when the component was connected, you can enable it on this page by adding collection.

Operation	Description
Select Platform	Select the connected component whose logs need to be collected. If no component is available, go to Cloud Federation > Platform Management first, and use the page entry in the Platform Access list or area.
Collection Target	Select the log types to collect. If there are no special requirements, keep the default selection on the page.

View or adjust log collection status.

Operation	Description
Collection Status	Confirm whether log collection is normal for the target component.
Modify Collection Target	Adjust log types in an existing collection configuration to meet new troubleshooting or audit analysis needs.
Delete Collection	Stop collecting log data from the target component. After collection is stopped, related pages no longer update log data for that component.

Note: If Log Summary, Log Explorer, or Live Tail lacks data, first confirm that log collection status and collection targets are correct, and then check the target component connection status.

Review Runtime Overview

Use the Home, Dashboard, Assets, and Infrastructure pages to view resource scale, health status, capacity usage, performance trends, and resource distribution across the connected environment. This workflow is useful for routine checks, environment overview, and resource status confirmation.

View the Global Overview

Home shows the resource and operations overview of ZCF. It helps users understand resource scale, health status, capacity usage, and performance status of connected components on one page. After ZNS is connected, Home can show an overview of VPC and other network service resources. For detailed ZSphere virtualization data, use virtualization dashboards, views, and reports.

Area	Description
Global Core Status	Displays resource overview, health overview, and capacity usage to help users understand the overall status of the current environment.
Cloud Platform · Basic Resources	Displays the scale and distribution of cloud platform resources, such as VM instances, physical hosts, networks, and capacity-related resources.
Network Services	After ZNS is connected, displays the status of VPC and other network service resources to help users understand network resource status from Home.
Container · Orchestration	Displays the status of Kubernetes clusters, nodes, workloads, and pods to help users understand container environment status.
Storage · Distributed	Displays the status and health of storage servers, disks, and related storage resources to help users understand storage availability.
Performance Insights · Resource Consumption Rankings	Displays performance-related rankings to help users quickly locate resource objects that need attention.

Log in to ZCF.
In the upper-right corner of the main menu, switch to Global Management.
In the main menu, click Home.
View global core status, resource overview, health overview, capacity usage, network service resource status, and performance rankings.

Note: Home data depends on component access and collection status. If a resource area is empty, check whether the corresponding component is connected through Cloud Federation and whether resource, monitoring, or log collection is enabled. Detailed resources, capacity, performance, and inventory data of the ZSphere virtualization platform are available in virtualization dashboards, views, and reports.

View Platform Health

The Platform Health page shows the running status of key ZCF services, health domains, component details, and external dependencies. Use this page for routine inspection, pre-upgrade checks, and fault isolation. A health domain summarizes check results by area, such as monitoring collection, alert evaluation, notification delivery, capacity risks, and basic dependencies.

In the upper-right corner of the main menu, switch to Global Management.
Go to Operations > Monitoring Center > Platform Health.

Review the platform health status.

Item	Description
Overall Platform Status	Shows the current health result, the last update time, and the number of exceptions.
Health Domain Overview	Shows health results by check area, including core services, monitoring collection, alert evaluation, notification delivery, capacity risks, and basic dependencies.
Component Details and External Dependencies	Shows component instances, service details, external dependency status, and the affected scope.
Exceptions and Pending Items	Shows unhealthy, degraded, or pending items that require attention.

Open an abnormal health item to view the check result, affected object, and recommended action.
Continue troubleshooting from the related metric query, log query, Alarm Center, or resource details page as needed.

Note: Platform health focuses on ZCF platform services and key service chains. For business resource metrics and logs, use monitoring queries, log queries, dashboards, or resource details.

View Dashboards

Dashboards show resource health, capacity, performance, and asset status from a global or component perspective. You can view preset dashboards or open custom dashboards for frequently used inspection and analysis perspectives. After ZSphere is connected and collection is enabled, virtualization data such as availability, capacity, performance, and asset inventory is available from the Virtualization dashboard.

Dashboard	Use Case
Operations Overview	View the overall status of connected components. Use it for daily checks and cross-component status review.
Cloud Dashboard	View overview, availability, capacity, performance, and asset inventory for cloud resources.
Virtualization Dashboard	View availability, capacity, performance, and asset inventory for virtualization platform resources, including ZSphere resources.
Container Dashboard	View overview, availability, capacity, performance, control plane, and asset inventory for Kubernetes-related resources.
Storage Dashboard	View overview, availability, capacity, performance, and asset inventory for storage resources.
AI Inference Dashboard	Within the corresponding cloud platform, view inference service status, request volume, request failure rate, inference performance, and KV Cache utilization. Use it to monitor inference service quality and resource pressure.
Custom Dashboard	View user-defined combinations of views. Use custom dashboards to save common perspectives by business, resource type, or team responsibility.

In the upper-right corner of the main menu, switch to Global Management.
Go to Dashboards & Reports > Dashboards.
Select the operations overview, or select the cloud dashboard, virtualization dashboard, container dashboard, storage dashboard, or AI Inference Dashboard from Specialized Dashboards. You can also open a custom dashboard.
Review overview, availability, capacity, performance, and asset inventory information on the selected dashboard.

Note: Dashboard data depends on resource, metric, and log collection. If the Virtualization dashboard has no data, or the page indicates that the current product is not deployed or collection is not enabled, check whether ZSphere is connected through ZCF Cloud Federation and whether the required resource or metric collection is enabled.

View Assets

Assets is used to view and search resources across components. It is suitable for resource inventory, locating abnormal objects, and drilling down from Home, dashboards, or alarm messages. Users can locate specific objects by resource type, and then view resource details and related metrics.

Item	Description
Select Resource Type	Switch between resource types such as host, VM instance, and pod.
Search Resources	Search resources by field and value.
Lists and Relationships	View resource lists by supported grouping methods, and view related metrics or resource relationships in resource details.
View Resource Details	View resource details and related monitoring information.

In the upper-right corner of the main menu, switch to Global Management.
Go to Operations > Unified Assets > Assets.
Select the resource type to view.
Search resources by field and value, or view the resource list by supported grouping methods.
Open resource details to view resource information, related metrics, or resource relationships provided by the page.

Note: If the target resource is not displayed, confirm that the corresponding component is connected and resource collection is complete. If resource status or metrics are abnormal, continue troubleshooting in Metrics Explorer, Log Explorer, or Alarm Center.

View Infrastructure

Infrastructure shows base resource structure and capacity distribution from global, Cloud Federation, cloud, storage, and container perspectives.

Item	Description
Global Overview	View total asset count and resource counts for cloud, storage, and container resources.
Capacity Distribution	View CPU, memory, storage, and other capacity usage across connected platforms.
Network Resource Summary	View summaries of L3 networks, L2 networks, IP addresses, security groups, load balancers, and other network resources.

In the upper-right corner of the main menu, switch to Global Management.
Go to Operations > Unified Assets > Infrastructure.
Switch among tabs such as Overview, Cloud Federation, Cloud, Storage, and Container (K8S).
View resource count, capacity distribution, resource status, or network resource summary.

Build Analysis Views and Reports

Use built-in or custom views to preserve common analysis dimensions, and organize views into report templates for on-demand or scheduled report generation. This workflow is useful for periodic checks, capacity analysis, performance review, and asset inventory output.

View and Maintain Views

Views are reusable chart views for resource or metric analysis. Built-in views are grouped by cloud, virtualization, container, and storage. You can also maintain custom views for later checks, report output, or troubleshooting.

In the upper-right corner of the main menu, switch to Global Management.
Go to Dashboards & Reports > Views.

On the Overview tab, view built-in views. On the Management tab, maintain custom views.

Operation	Description
View Built-in Views	View common views for availability, assets, performance, and capacity.
Switch Platform Type	Switch the view scope by platform type, such as cloud, virtualization, container, or storage.
Search or Filter Views	Find views by name or applicable platform type.
Clone or Maintain Views	Clone built-in views, or edit, clone, and delete custom views.

Note: Built-in views are typically used for viewing and cloning. Custom views can be edited, cloned, or deleted. Virtualization views can be used to build custom dashboards or report templates.

Create a Custom View

Create a custom view when built-in views do not cover a specific resource or metric analysis requirement. After a custom view is created, you can reuse it from the view list or add it to a report template.

In the upper-right corner of the main menu, switch to Global Management.
Go to Dashboards & Reports > Views.
On the Management tab, click Create View.

Configure custom view parameters as prompted.

Parameter	Description
Name	The display name of the custom view in the view list and report templates. Use a name that identifies the analysis object or purpose.
Description	The purpose of the view. Use it to identify the routine check, analysis, or reporting scenario for the view.
View Type	The display and analysis type of the view. Available parameters may vary by view type. Follow the fields displayed on the page.
Business Category	The category that the view belongs to. It is used for filtering in the view list, report templates, and later maintenance.
Applicable Platform Type	The platform scope of the view, such as cloud, container, or storage. Available data depends on connected components and collection status.
Resource Type	The resource object type to analyze. Supported fields, metrics, and filters may vary by resource type.
View Configuration	Display fields, metrics, filters, or chart settings that define what the view shows.

In Preview and Confirm, review the display and save the view.

Note: Custom views are useful for recurring analysis dimensions. Before creating a view, make sure that the required resource or metric data has been collected. Otherwise, the preview and later reports might have no data.

Save a Metric Query as a View

For metric queries that you need to revisit, save the query conditions and display settings as a view. The saved view can be reused from the view list or added to a report template.

In the upper-right corner of the main menu, switch to Global Management.
Go to Operations > Monitoring Center > Metrics Explorer.

Set metric query conditions as prompted.

Parameter	Description
Platform	The platform or component scope for metric queries. Available options depend on connected components and metric collection status.
Resource Scope	The resource object or resource group to analyze. It limits the data scope of the metric query.
Metric	One or more metrics to view. Supported metrics may vary by platform and resource type.
Aggregation Method	The aggregation or calculation method for metric data. It controls how trend data is calculated.
Chart Style	The display style of the query result. Use it to view metric data by trend, comparison, or distribution.
Time Range	The time range for the metric query. After the query is saved as a view, you can reuse the query conditions for later analysis.

Run the query and verify that the result meets your expectation.
Save the current query as a view as prompted.
Go to Dashboards & Reports > Views and verify that the view is generated.

Create a Custom Dashboard

A custom dashboard combines frequently used views on one page. Use custom dashboards to create reusable observation perspectives by business, resource type, or team responsibility.

In the upper-right corner of the main menu, switch to Global Management.
Go to Dashboards & Reports > Dashboards, and switch to the Manage tab.
Click Create Dashboard, and enter a dashboard name and description.

In the Add View panel, select the views to display and add them to the canvas.

Selection Point	Description
View Type	Select views based on goals such as inspection, resource analysis, capacity analysis, or alert tracking.
Resource Scope	Select a global, component, region, or resource type scope as needed to avoid mixing unrelated data in one dashboard.
Time Range	Select an appropriate time range for trend views to observe recent changes or historical trends.

Drag views to adjust their positions and sizes as needed.

Place key status, exception statistics, or capacity risks near the top of the page. Arrange trend, ranking, and detail views in the order used for troubleshooting.
Save the dashboard, and return to the dashboard list to confirm that the custom dashboard has been created.

Maintain the custom dashboard as needed.

Operation	Description
Edit Dashboard	Adjust the dashboard name, description, view content, or layout.
Clone Dashboard	Create a copy from an existing dashboard, and then adjust it for a similar observation perspective.
Import or Export Dashboard	Use a JSON file to migrate or reuse dashboard configurations.
Delete Dashboard	Delete a custom dashboard that is no longer needed.

Note: Data in a custom dashboard depends on the data sources and collection status of the selected views. If a view has no data, check the corresponding component connection and collection configuration.

Create a Report Template

A report template combines multiple views into an operations report that can be generated on demand or on a schedule. Platform administrators can create personal custom templates from views they can access for capacity analysis, performance review, asset inventory, or availability checks.

Confirm that your account is a platform administrator, then switch to Global Management in the upper-right corner of the main menu.
Go to Dashboards & Reports > Reports.
On the Report Template tab, click Create Report Template.

Configure report template parameters as prompted.

Parameter	Description
Template Name	The display name of the report template in the template list and generation records. Use a name that identifies the report purpose.
Description	The purpose of the report template. Use it to distinguish templates for capacity analysis, performance review, asset inventory, or availability checks.
Available Views	The accessible views to include in the report, including built-in views and created custom views.
View Category	The category used to filter available views, such as capacity, performance, assets, and availability.
Report Content	The selected views and their display order, which determine the main content structure of the generated report. A template can contain up to 100 views.

Review the view order and content in the report content area, and save the template as prompted.

Note: A saved custom template can be viewed, edited, deleted, and scheduled only by its creator. It cannot be shared, published, or transferred to another user. If Create Report Template is not displayed, confirm that your account has platform administrator permissions.

View and Maintain Report Templates

Report Template defines report content and generation methods. All users can view available built-in templates. Platform administrators can also clone built-in templates or templates they created to create custom templates.

In the upper-right corner of the main menu, switch to Global Management.
Go to Dashboards & Reports > Reports.

On the Report Template tab, view, search, or clone report templates.

Operation	Description
View Templates	View report templates for capacity, performance, asset inventory, availability, and other scenarios, and confirm the template scope and report content.
Clone Template	Platform administrators can clone a built-in template or a template they created to create a custom template and adjust the report scope based on existing content.
Search Templates	Search report templates by template name.

Note: Custom report templates can be viewed, edited, deleted, and scheduled only by their creators. Built-in templates cannot be edited or deleted. Create, edit, and delete controls are not displayed to users without the required permissions.

Generate and Download Reports

Reports can be generated from report templates on demand or on a schedule. View generation history on the Generation Record tab and download generated report files.

In the upper-right corner of the main menu, switch to Global Management.
Go to Dashboards & Reports > Reports.
On the Report Template tab, select a template.

Generate a report immediately, or configure a schedule for the template.

Operation	Description
Generate Immediately	Generate a report from a template immediately. Use this for ad hoc checks or analysis output.
Configure Scheduled Generation	Configure a schedule for a report template. Use this for periodic capacity, performance, asset inventory, or availability reports.
View Generation Records	View report generation history, execution status, and generation results.
Download Reports	Download generated report files. Available formats depend on what the page provides.

On the Generation Record tab, view the generation result and download the report file.

Note: A generated report is a static snapshot. Generate the report again to view the latest status.

Troubleshoot Metrics and Logs

Use Metrics Summary and Log Summary to understand data volume, source distribution, and trends, and then use Metrics Explorer or Log Explorer to locate issues by metric, field, level, and time range. This workflow is useful for performance analysis, abnormal log investigation, and real-time log diagnosis.

View Metrics Summary

Before viewing metrics summary, make sure the target component is connected to ZCF and metric collection is enabled.

Metrics Summary shows whether metric data is entering ZCF normally. Use this page to confirm the metric ingestion scale and source distribution before opening Metrics Explorer for further analysis.

Item	Description
Collection Overview	View connected platform count, online status, metric count, and total metric data volume.
Source Distribution	View metric count and data ratio by connected platform to determine whether data volume is as expected.
Integrated Platforms	View connected monitoring platforms and their data volume to locate platforms with missing metric data.

In the upper-right corner of the main menu, switch to Global Management.
Go to Operations > Monitoring Center > Metrics Summary.
View the collection overview and confirm whether metric data is continuously entering ZCF.
View source distribution and the connected component list to determine whether the data volume of each component is as expected.

Note: If a component has no metric data, check the component connection status, metric collection configuration, and collection status first. If only some metrics are abnormal, continue troubleshooting in Metrics Explorer.

Query Metrics

Before querying metrics, make sure the target component is connected to ZCF and metric collection is enabled. The platforms, resources, and metrics that can be queried depend on component connection status, metric collection status, and current user permissions.

Metrics Explorer queries metric trends by platform, resource, and metric conditions. It is suitable for further locating affected objects after performance fluctuations, capacity pressure, or resource exceptions are found. Frequently used queries can be saved as views for later analysis.

In the upper-right corner of the main menu, switch to Global Management.
Go to Operations > Monitoring Center > Metrics Explorer.

Set metric query conditions as prompted.

Configuration item	Description
Query Scope	Select the platform, component, or resource scope to define the metric data source.
Resource Object	Select a specific resource or resource group to view the status of one object or compare metric changes across multiple objects.
Metric	Select the metric to view. The page provides available metrics based on the query scope and shows metric units or status meanings.
Time Range	Select a query time range to view metric changes within the specified period.
Display Method	Select a statistics method and chart style as needed to compare trends, peaks, and abnormal points.

Run the query and view metric trends and abnormal points.
To continue troubleshooting, adjust the query scope, time range, or metrics, and run the query again.

Note: If the target metric cannot be queried, check whether the target component is connected, and confirm that metric collection configuration, collection status, and current user permissions are normal. To reuse the current query conditions, save the metrics query as a view.

View Log Summary

Before viewing log summary, make sure the target component is connected to ZCF and log collection is enabled.

Log Summary shows the overall status of log collection and ingestion. Users can use log volume, event count, source ranking, log trends, and level distribution to quickly determine whether logs are continuously entering ZCF and which sources require attention.

Item	Description
Time Range	Switch the statistics time range and observe whether log volume, event count, and source ranking change over time.
Log Overview	View total data volume, log entries, ingestion rate, and active data sources to confirm whether logs are continuously entering ZCF.
Source Ranking	View components or data sources with high log volume to locate sources of log spikes or abnormal collection scale.
Level Distribution	View the proportions of ERROR, WARN, INFO, and other log levels to identify scopes with concentrated error or warning logs.

In the upper-right corner of the main menu, switch to Global Management.
Go to Operations > Log Center > Log Summary.
Select a time range and view the log overview and log volume trend.
View source ranking and level distribution to determine whether there are log spikes, collection interruptions, or concentrated error logs.

Note: If a log source or level is abnormal, open Log Explorer and continue retrieving log details by time range, source, and level.

Query Logs

Before querying logs, make sure the target component is connected to ZCF and log collection is enabled. The available sources and fields depend on log collection status, log parsing results, and current user permissions.

Log Explorer retrieves and analyzes historical logs. Users can narrow the scope by time, source, level, keyword, or structured field to locate abnormal time ranges, log sources, and key log content.

In the upper-right corner of the main menu, switch to Global Management.
Go to Operations > Log Center > Log Explorer.

Set log query conditions as prompted.

Configuration item	Description
Query Scope	Select the component, log source, and time range to define the log data scope.
Log Level	Filter logs by ERROR, WARN, INFO, or other levels to prioritize exceptions or warnings.
Keyword	Enter an error code, resource name, service name, or another keyword to retrieve related records from log content.
Field Filter	Narrow results by parsed fields such as platform, host, service, or instance.
Log Details	View the time, level, source, content, and extended fields of a single log entry to confirm exception context.

Run the query and view log distribution and log details.
Based on the query results, continue adjusting the time range, source, or filters to narrow the troubleshooting scope.

Note: If log query results are empty, check whether the target component is connected, and confirm that log collection configuration, collection status, query time range, and current user permissions are normal.

Diagnose Logs with Live Tail

Before using Live Tail, make sure the target component is connected to ZCF, log collection is normal, and logs are being generated at the current time.

Live Tail is used to view the latest logs that are continuously written. It is suitable for observing immediate output while reproducing an issue, performing an operations task, or verifying collection status. Compared with log query, Live Tail is better for seeing log changes that are happening now.

In the upper-right corner of the main menu, switch to Global Management.
Go to Operations > Log Center > Log Explorer.
Switch to the Live Tail tab.

Select the component, log source, or log level to observe.

Configuration item	Description
Component or Source	Select the log source to observe to avoid too much irrelevant live output.
Log Level	View only key levels such as ERROR and WARN as needed to capture exceptions during reproduction.
Keyword	Enter a resource name, task ID, error code, or service name to focus on logs related to the current operation.

Review the live log output and use the timestamp, level, and key fields to locate issues.
To review historical context, return to Log Explorer and query logs in the corresponding time range by using the same conditions.

Note: If Live Tail does not return logs, first confirm that the target component is connected, and check whether log collection configuration, collection status, and current user permissions are normal.

Manage Alarms and Notifications

Alarms and notifications turn metric anomalies, event risks, and resource issues into a trackable workflow. Users can confirm data sources and collection status first, define risk detection conditions with alarm rules, send important alarms to the right teams through message templates, notification channels, and notification policies, and view and handle risks in alarm messages.

Configuration Workflow

Confirm that the target component is connected and that resource, metric, log, or event alarm data sources are enabled as needed.
Create an alarm rule to define trigger rules, alarm severity, and alarm scope for metric risks.
Create a message template to define the content format of external notifications.
Create a notification channel for DingTalk, WeCom, Feishu, Slack, Microsoft Teams, Telegram, email, Webhook, or SMS delivery.
Create a notification policy to match alarms that require external notification and bind notification channels.
Create silence policies or inhibition rules as needed to reduce repeated notifications during maintenance windows or related failures.
View and handle alarm messages, including alarm status, notification delivery results, and follow-up actions.

Note: Event alarm integration brings event alarms from connected platforms into ZCF Alarm Center. After integration is complete, event alarms can use the same notification channels, notification policies, silence policies, and inhibition rules as resource alarms.

Core Concepts

Concept	Description
Alarm Message	A risk record generated after an alarm rule or event integration is triggered. It is used to view the affected object, severity, trigger time, and handling status.
Alarm Rule	A rule that defines trigger logic, severity, and scope for metric or resource risks, and generates alarm messages when matched.
Notification Channel	An external destination for alarm delivery, such as DingTalk, WeCom, Feishu, Slack, Microsoft Teams, Telegram, email, Webhook, or SMS.
Notification Policy	A rule that matches alarms by severity, source, resource type, or other attributes and decides whether to send them to external channels.
Message Template	A template that defines the content and format of an external notification. Notification channels reference message templates.
Silence Policy	Temporarily pauses external notifications for matching alarms during a specified time range, such as planned maintenance. Alarm messages remain available in Alarm Center.
Inhibition Rule	When a source alarm is active, pauses external notifications for matching target alarms to reduce duplicate notifications caused by the same issue.
Event Alarm Integration	A configuration that brings event alarms reported by connected platforms into ZCF for unified viewing and notification.
Alarm Configuration Consistency	The match state between event alarm integration settings saved in ZCF and the corresponding settings on a connected platform. ZCF periodically checks managed configurations, and platform administrators can also synchronize them manually. When synchronization detects a difference, ZCF applies the settings it saved to the target platform and verifies the result.

Enable Event Alarm Integration

Before enabling event alarm integration, make sure the target platform is connected to ZCF through Cloud Federation, the connection is normal, and the current administrator has the required Cloud Federation and Alarm Center permissions.

After you connect a platform through Cloud Federation, you can enable event alarm integration on the Event Alarm Integration page. Once enabled, event alarms reported by the platform enter ZCF Alarm Center. You can view these alarms in Alarm Messages and use notification policies to send important alarms to external channels.

In the upper-right corner of the main menu, switch to Global Management.
Go to Operations > Alarm Center > Event Alarm Integration.
Find the target platform, click Enable, and follow the prompts to turn on event alarm integration.

Check the event alarm integration status of the platform.

Item	Description
Event Alarm Hosting	Shows whether event alarm integration is enabled for the platform and managed by ZCF.
Configuration Status	Shows whether event alarm integration settings match the settings saved in ZCF. ZCF periodically checks managed configurations. When an issue is found, platform administrators can synchronize the configuration manually.
Last Synchronization	Shows the time and result of the latest configuration synchronization.
Latest Event Alarm	Shows the latest time that an event alarm was received.
Parsing Failures and Unknown Events	Shows event parsing or recognition exceptions.
Diagnostic Details	Provides connection, synchronization, callback, and log check results.

To check and handle alarm configuration immediately, see Check and Synchronize Alarm Configuration.
Manual synchronization checks the current settings first. When it detects a difference, it applies the settings saved in ZCF to the target platform and verifies the result.
Go to Operations > Alarm Center > Alarm Messages to view event alarms or event records.
If the integration status is normal but no alarm messages are displayed, confirm whether events have been generated on the component side, and then check the latest event alarm time, parsing failures, and unknown events.
To send event alarms externally, configure notification policies in Operations > Alarm Center > Notification Settings.
After event alarms enter Alarm Center, they can use the same notification channels and policies as resource alarms.

Note: The current release supports event alarm integration for connected Cloud and ZSphere platforms. For resource alarms triggered by metric thresholds, manage alarm rules.

Check and Synchronize Alarm Configuration

Before checking and synchronizing alarm configuration, make sure the target Cloud or ZSphere platform is connected to ZCF through Cloud Federation and event alarm integration is enabled. Only platform administrators can view configuration status and run synchronization manually.

Alarm configuration synchronization checks whether the event alarm integration settings saved in ZCF still match the settings on a connected platform. This helps avoid configuration drift that could affect event alarm ingestion or notification delivery. ZCF periodically checks managed configurations, and administrators can also synchronize them manually. Synchronization checks the current settings first. When it detects a difference, it applies the settings saved in ZCF to the target platform and verifies the result.

In the upper-right corner of the main menu, switch to Global Management.
Go to Operations > Alarm Center > Event Alarm Integration.
Find the target Cloud or ZSphere platform, and review its configuration status and latest synchronization result.
A normal status confirms that the current settings are consistent. A drifted, unverified, or failed status requires further action. The page does not display sensitive information such as callback credentials.
To handle the configuration status immediately, click Synchronize and wait for synchronization to finish.
Synchronization checks the current settings. When it detects a difference, it updates the target platform with the current event alarm integration settings saved in ZCF and then verifies the result. If synchronization fails, use the latest error shown on the page to check platform connectivity and access credentials.

Note: The current release supports checking and synchronizing event alarm callback settings for Cloud and ZSphere only. Other configuration types are not supported.

Create an Alarm Rule

Before creating an alarm rule, make sure the target component is connected to ZCF and the required resource or metric collection is enabled.

Alarm rules define how ZCF identifies resource or metric risks. Users can configure trigger rules, alarm severity, and alarm scope by platform type, resource type, and alarm item. After a rule is triggered, ZCF generates an alarm message.

In the upper-right corner of the main menu, switch to Global Management.
Go to Operations > Alarm Center > Alarm Rules.
Click Create Rule.

Configure the alarm rule.

Parameter	Description
Name and Description	Use a name that clearly identifies the resource type, metric, and risk scenario.
Platform Type	Select the platform type to which the rule applies. The platform type determines the available resource types and alarm items.
Resource Type	Select the resource type to monitor. Available alarm items vary by resource type.
Alarm Item	Select the metric or check item that the rule monitors.
Alarm Trigger Rule	Configure the comparison operator, threshold, and duration used to decide when an alarm is generated.
Alarm Severity	Select the severity. The severity affects alarm filtering and notification policy matching.
Alarm Scope	Select the resource scope to which the rule applies. Narrow the scope when only specific resources need to be monitored.

Save the rule and enable it as needed.
After the rule is triggered, go to Operations > Alarm Center > Alarm Messages to view the generated alarm.

Note: An alarm rule only defines how a risk is detected. To send triggered alarms to external channels, configure notification channels and notification policies.

Create a Message Template

Before creating a custom message template, confirm the content format required by the target channel. For example, chatbot channels often use Markdown, email may use HTML or plain text, and Webhook channels may use JSON.

Message templates define the content format of external alarm notifications. System templates cover common notification scenarios. Create a custom template only when different notification channels, teams, or services require different notification content, formats, or fields.

Go to Operations > Alarm Center > Message Templates.

If you are not in the Global Management view, switch to Global Management in the upper-right corner of the main menu first.
View the system templates and custom templates.

Do not modify system templates directly. To adjust the content, clone a system template first and then modify the copy.
Confirm whether a custom template is required.

For common scenarios, use a system template directly. Create a custom template only when different notification channels, teams, or services require different notification content, formats, or fields.

Create a custom template.

Complete the template parameters as follows:

Parameter	Description
Template Name	Identify the usage scenario, such as on-duty group alarms, critical alarm emails, or Webhook callbacks.
Description	Describe the template scope to help multiple administrators maintain templates.
Content Format	Select Markdown, HTML, JSON, or plain text based on the receiver requirements. Chatbot channels usually use Markdown, and Webhook channels usually use JSON.
Load Preset Template	Load a system preset for the selected content format as the starting point. Use this option when creating a template for the first time or when you want to reuse the system variable structure, and then adjust the content in the source editor.
Template Content	Write the notification body. You can insert variables such as alarm name, severity, resource, status, trigger time, summary, and handling suggestions.
Variable Reference	View supported variables and their meanings to avoid referencing fields that do not exist and generating empty notification content.
Preview	Before saving, preview the rendered template to confirm that key information is complete and the format meets receiver requirements.

Save the message template.
Go to Operations > Alarm Center > Notification Settings and select the template in a notification channel.
A notification channel references a message template. A notification policy decides which alarms are sent to the channel, and the template decides how those alarms appear in the channel.
Test the notification channel to confirm that the template content can be sent and displayed correctly.

Note: To delete a template that is referenced by a notification channel, change the referenced template in the channel first. After changing a template, test the channels that use it.

Configure the Email Server

Obtain the SMTP server address, port, encryption method, and authentication information, and prepare an email address that can receive test messages. An administrator account is required.

The email server configuration is a system-level SMTP sending configuration shared by all email channels.

On the main menu, click Operations. In the left navigation pane, expand System Management and click Email Server.
Optionally select a common provider under Quick Fill, or keep Custom selected and enter the SMTP configuration manually.
When a common provider is selected, the page fills in its SMTP server, port, and encryption method. Complete the authentication and sender information based on the actual mailbox account.

Enter the SMTP configuration.

Field	Description
SMTP Server	Enter the SMTP server address.
Port	Enter a port number from 1 through 65535.
Encryption	Select None, SSL/TLS, or STARTTLS, consistent with the email provider configuration.
Authentication	Select no authentication or username/password authentication. For username/password authentication, enter the SMTP username and password or app password.
From Address	Enter the sender email address.
From Name	Optionally enter the sender name displayed to recipients. If left empty, the page default is used.

Note: For an existing username/password configuration, leave the password field blank to keep the current password.

Click Save Configuration.
In the Test Connection area, enter a test recipient email address, click Send Test Email, confirm that the page reports a successful test, and verify that the test email arrives in the recipient inbox.
If the test fails, use the page error to check the server, port, security protocol, login details, and network connectivity.

Note: The saved SMTP configuration is shared by all email channels.

Create a Notification Channel

ZCF supports DingTalk, WeCom, Feishu, Slack, Microsoft Teams, Telegram, email, Webhook, and SMS notification channels. Before creating a channel, prepare the information required by the channel type you plan to use:

Make sure ZCF can access the target notification system or receiving endpoint.
For DingTalk, WeCom, Feishu, Slack, or Microsoft Teams, obtain the Webhook URL provided by the target group or workflow and prepare any security key or verification information required by that platform.
For Telegram, prepare the Bot Token and target chat information, and make sure the bot has joined the target group or has permission to send messages.
For email, configure and test the mail server first, and prepare recipient, CC, or BCC email addresses.
For Webhook, prepare the receiver URL, request method, and authentication headers.
For SMS, prepare the provider credentials, SMS signature, template or API URL, and confirm that the SMS quota is sufficient.
If custom notification content is required, create a message template first. You can also use a system template.

Notification channels define external destinations for alarm delivery. Alarms are displayed in Operations > Alarm Center > Alarm Messages by default. To send alarms to an external channel, create a channel first, and then reference the channel in a notification policy.

In the upper-right corner of the main menu, switch to Global Management.
Go to Operations > Alarm Center > Notification Settings.
On the Notification Channels tab, create a notification channel.

Select a channel type and complete the required parameters.

Channel Type	Parameters	How to Fill
All Channels	Channel name, description, message template	Use a channel name that identifies the recipient team or notification scenario. The message template controls the notification format. Use a system template or create a custom template on the Message Templates tab.
DingTalk	Webhook URL, security settings, @ mentions	Enter the Webhook URL of the DingTalk group chatbot. If security settings are enabled for the chatbot, also enter the keyword, signing secret, or IP allowlist information as required. To mention all members of the group, enable `@all` as prompted on the page.
WeCom	Webhook URL, security settings, @ mentions	Enter the Webhook URL of the WeCom group chatbot. For targeted mentions, enter the member User IDs.
Feishu, Slack, and Microsoft Teams	Webhook URL, security settings, or workflow configuration	Enter the Webhook URL provided by the target group or workflow. Complete the security verification required by the corresponding platform. Slack supports `@here` and `@channel` mentions as prompted. Microsoft Teams receives messages through a Workflows Webhook.
Telegram	Bot Token, target chat, message format	Enter the Bot Token and target chat information. Make sure the bot has joined the target group or channel and can send messages. A successful test indicates that the message was submitted to the target chat. Confirm the received result in Telegram.
Email	Recipients, CC, BCC	Recipients are required. Multiple email addresses are supported. Use CC or BCC to notify additional recipients. Email delivery depends on mail server configuration. If the mail server is not configured or the test fails, alarms cannot be sent by email.
Webhook	URL, request method, headers, TLS verification	Enter the receiving endpoint URL and select a request method. If authentication is required, add a token or other credentials in the request headers. Skip TLS verification only in trusted test environments or self-signed certificate scenarios.
SMS	Provider, authentication information, signature, template or API URL, recipient phone number	Fill in the parameters required by the selected SMS provider. For Alibaba Cloud SMS, provide the AccessKey, signature, template code, and recipient phone number. For Generic HTTP, provide the API endpoint, authentication method, request body, and success matching rule according to the SMS gateway requirements. SMS messages are charged by the provider. Use SMS mainly for critical or emergency alarms.

Save the notification channel and run a test delivery.

A successful test means ZCF has submitted a test notification to the target channel. Confirm the received result in the target group, workflow, email inbox, Webhook receiving service, or SMS recipient phone. If the test fails, check the endpoint, credentials, chatbot security settings, mail server, or SMS provider configuration. SMS tests consume SMS quota.
Create or update a notification policy to send matching alarms to this channel.

Note: A notification channel only defines where alarms can be sent. To send specific alarms to the channel, create a notification policy.

Configure Notification Policies and Noise-Reduction Rules

Notification policies, silence policies, and inhibition rules together control whether alarms are sent through external channels and how duplicate notifications are reduced. None of them removes alarm messages. Matching alarms remain available for viewing and handling in Alarm Center.

Rule	Purpose	When to Use It
Notification Policy	Filters alarms that require external notification and defines delivery channels and notification grouping.	When important alarms must be sent to on-call staff, business teams, or external systems.
Silence Policy	Pauses external notifications for matching alarms during a specified time range.	During planned maintenance, planned changes, or other expected exception periods.
Inhibition Rule	When a root-cause alarm is active, pauses notifications for target alarms caused by the same issue.	When alarm dependencies are known and cascading failures could otherwise create duplicate notifications.

Notification Policy

A notification policy defines which alarms are sent to external channels and how notifications are grouped. Before creating a policy, create and test at least one notification channel, and identify the alarms that require external notification.

In the upper-right corner of the main menu, switch to Global Management. Go to Operations > Alarm Center > Notification Settings, open the Notification Policies tab, and create a policy.

Configuration Item	Description
Policy Name and Description	Identify the policy purpose. Include the recipient or scenario, such as critical alarm notifications for the on-call team, capacity-risk notifications, or notifications for a specific component.
Notification Rules	Filter alarms that require external notification. You can match conditions such as alarm severity, product type, resource type, region, cluster, host, alarm name, source system, event domain, connected instance, lifecycle state, and acknowledgment state.
Match Operator	Supports equals, does not equal, regex match, and regex mismatch. Use regex matching to include a class of objects, or does-not-equal and regex mismatch to exclude one.
Notification Channels	Select enabled external notification channels. A policy can bind multiple channels when the same type of alarm must notify multiple teams or systems.
Resolved Alarms	When enabled, sends a notification when an alarm is resolved so that on-call staff can confirm that the risk has been cleared.
Grouping and Repeat Notifications	Groups similar alarms by resource, cluster, alarm name, or other fields, and sets the initial wait, group interval, and repeat interval to reduce frequent notifications for the same type of alarm.
Multiple Matching Policies	An alarm can match multiple notification policies. Each policy sends through its bound channels independently. Avoid policies that send duplicate notifications to the same team.

After saving the policy, go to Operations > Alarm Center > Alarm Messages to view alarm messages and notification delivery results. Alarms that do not match an external notification policy still appear in Alarm Messages but are not sent to external channels.

Silence Policy

A silence policy pauses external notifications for matching alarms during an expected time period, such as planned maintenance, to avoid unnecessary interruptions to on-call staff.

In Notification Settings, open the Silence Policies tab, create a policy, and complete the following configuration.

Configuration Item	Description
Policy Name and Reason	Describes the silence scope and its reason, making the policy easier to identify during maintenance and review later.
Effective Time and Time Zone	Specifies the start time, end time, and time zone. The silence is effective only within that time range.
Alarm Matching Conditions	Defines the alarms for which external notifications are paused. Narrow the scope by platform, resource type, alarm severity, or other supported conditions.
Policy Status	You can enable, disable, edit, or delete a policy as needed. When the policy is lifted, previously suppressed notifications are not replayed. For alarms that remain unresolved, the system generates one summary notification according to the current notification policy.

Note: Keep matching conditions limited to the platforms, resource types, or alarm severities involved in maintenance. Disable or delete policies that are no longer needed after maintenance so that subsequent risks can be reported normally.

Inhibition Rule

An inhibition rule pauses notifications for target alarms derived from the same issue when a root-cause alarm has been triggered, reducing duplicate notifications.

In Notification Settings, open the Inhibition Rules tab, create a rule, and complete the following configuration.

Configuration Item	Description
Rule Name and Reason	Describes the relationship between the root-cause and derived alarms, making the rule easier to maintain and review.
Source Alarm Matching Conditions	Defines when inhibition is triggered, which identifies the root-cause alarm.
Target Alarm Matching Conditions	Defines the alarms for which external notifications are paused, which are the alarms that may result from the root cause.
Equal Labels	Requires the source and target alarms to have the same values for specified labels before the rule takes effect. This prevents alarms from different platforms, regions, or resource scopes from affecting one another.
Rule Status	You can enable, disable, edit, or delete a rule as needed. When the rule is lifted, previously suppressed notifications are not replayed. For alarms that remain unresolved, the system generates one summary notification according to the current notification policy.

Note: The source alarm defines when inhibition is triggered, and the target alarm defines the scope of external notifications to pause. Review rule scope regularly to avoid suppressing real risks for an extended period.

View and Handle Alarm Messages

The Alarm Messages page centralizes resource alarms and event alarms. Use it to filter active risks, confirm handling status, check notification delivery, and continue troubleshooting from related resource, monitoring, or log pages. If an alarm matches a notification policy and the policy references notification channels, ZCF sends the alarm to the corresponding external channels. You can check the delivery result in the alarm details and confirm receipt in the third-party channel.

In the upper-right corner of the main menu, switch to Global Management.
Go to Operations > Alarm Center > Alarm Messages.

Select an alarm view.

View	Description
Active Alarms	Shows unresolved risks that currently require attention.
Recovered Alarms	Shows alarms whose trigger conditions have recovered.
Alarm History	Shows historical alarm records for review and tracing.
Resource Alarms	Shows alarms generated by resource metrics or resource status rules.
Event Alarms	Shows event alarms reported by connected components.
Event Records	Shows raw event records used for event alarm analysis. When an inference service becomes unknown, ZCF records it as an event record for tracing status changes. The event does not create a persistent alarm or send a recovery notification.

Filter alarms by severity, resource type, source component, lifecycle status, confirmation status, or time range.

Open an alarm to review the details.

Item	Description
Alarm Summary	Shows the alarm name, severity, status, first trigger time, and latest trigger time.
Affected Object	Shows the related component, resource type, resource object, and region.
Trigger Condition	Shows the rule, threshold, metric value, or event information that triggered the alarm.
Notification Delivery Result / Notification Channel	Shows the matched notification policy, notification channel, recipient, delivery status, retries, and failure reason.
Handling Suggestions and Comments	Shows recommended actions and records the handling process.

Confirm the alarm, add comments, or mark it as handled according to the handling result.
If an external notification channel is configured for the alarm, go to the corresponding third-party channel to confirm that the notification message was received.

Use the notification channel, recipient, and delivery status in the alarm details to confirm the same notification on the third-party side.
If further diagnosis is required, go to the related resource detail, monitoring query, log query, or Alarm Center configuration page.

Note: If an alarm is not delivered to an external channel, check the delivery details first, and then verify the notification channel and notification policy configurations.

Manage Alarm Rules

Before managing alarm rules, make sure the alarm rules that need maintenance already exist.

Use the Alarm Rules page to view and maintain built-in and custom rules. You can enable, disable, edit, clone, import, export, or delete rules as supported, and continuously refine the risk detection scope.

In the upper-right corner of the main menu, switch to Global Management.
Go to Operations > Alarm Center > Alarm Rules.

Review existing alarm rules.

Rule Type	How to Use
Built-in	Covers common resource risks. You can enable, disable, adjust editable fields, or restore defaults when the page supports these operations.
Custom	Adds metric conditions required by your business. You can create, edit, clone, import, export, or delete custom rules.

Manage rules as needed.

Operation	Description
Enable or Disable	Controls whether the rule participates in alarm detection.
Edit	Adjusts the rule name, description, platform type, resource type, alarm item, trigger rule, alarm severity, or alarm scope.
Clone	Creates a similar rule based on an existing one.
Import or Export	Moves custom rule configurations between environments.
Restore Defaults	Restores built-in rule settings when supported.
Delete	Deletes rules that are no longer needed. Built-in rules may not support deletion.

Note: After adjusting alarm rules, continue monitoring the number and trigger frequency of alarm messages to confirm that the rule changes meet expectations.

PreviousNetwork Service NextUnified Portal