Help Center/ Cloud Eye/ FAQs/ Product Usage/ Alarm Management/ Why Are Resource Names Not Displayed in Alarm Notifications?
Updated on 2025-11-14 GMT+08:00
View PDF
Share

Why Are Resource Names Not Displayed in Alarm Notifications?

In alarm notifications of Cloud Eye, instance names are not displayed for some cloud services. The possible causes are as follows:

  • Cloud services are not properly interconnected in accordance with Cloud Eye specifications.
  • Cloud services are not interconnected with RMS, so Cloud Eye cannot obtain the resource names from RMS.
  • Other: The resources have been deleted, or some resources do not have names.

Table 1 lists the cloud services whose resource information, such as resource names and enterprise projects, is not reported in the current alarm notification.

Table 1 Cloud services with no resource names reported

Cause

Namespace

Cloud Service

Non-standard cloud service interconnection

SYS.SFS

Scalable File Service

SYS.VOD

Video on Demand

SYS.DBSS

Database Security Service

SYS.OBS

Object Storage Service

SYS.FunctionGraph

FunctionGraph

SYS.ROMA

ROMA Connect

SYS.Maas

Marketplace as a Service

The cloud service not interconnected with the RMS

SYS.APIG

API Gateway

SYS.CloudTable

CloudTable Service

SYS.DDOS

Anti-DDoS

SYS.EG

EventGrid

SYS.GA

Global Accelerator

SYS.LIVE

Live

SYS.DAYU

Database Security Service

SYS.WAF

Web Application Firewall

Other cases (resources being deleted, unnamed, or of a special type)

SYS.GAUSSDB

TaurusDB

SYS.RMS

Config

SYS.RDS

Relational Database Service

The preceding statistics will be regularly updated. If the resource name information is not displayed in the alarm notification, log in to the Cloud Eye console and search for the resource name in the alarm record based on the resource ID.

Parent topic: Alarm Management