No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

HUAWEI CLOUD Stack 6.5.0 Alarm and Event Reference 04

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
ALM-0004000700010006 The Request Count 4xx of an OBS Exceeds the Threshold

ALM-0004000700010006 The Request Count 4xx of an OBS Exceeds the Threshold

Alarm Description

This alarm is generated when the number of requests whose response error status code is 4xx exceeds the threshold specified by the administrator.

The threshold can be manually set on the Monitoring Center > Monitoring Configuration > Performance Threshold Maintenance page.

Alarm Attribute

Alarm ID

Alarm Severity

Alarm Type

0004000700010006

Critical/Major/Minor/Warning

QoS

There are four severity levels of PerfMonitor threshold-crossing alarms, including critical, major, minor, and warning. The four levels of alarms are handled in the same way.

Alarm Parameters

Resource Type

Parameter

Description

OBS server

Name

Resource name of an OBS server

ID

ID

Impact on the System

System functions may be unavailable.

Possible Causes

  • The threshold settings are inappropriate.
  • Error code 400 is returned, indicating that a request error occurs.
  • Error code 403 is returned, indicating that the request is rejected.
  • Error code 404 is returned, indicating that the requested resource does not exist.
  • Error code 405 is returned, indicating that the request method is not allowed.
  • Error code 408 is returned, indicating that the request timed out.
  • Error code 409 is returned, indicating that a request conflict occurs.
  • Error code 411 is returned, indicating that the request requires a content length header.
  • Error code 412 is returned, indicating that the request of precondition fails.
  • Error code 416 is returned, indicating that the request scope is inappropriate.

Handling Procedure

  1. Check the threshold settings of the monitoring indicator.

    1. Choose Monitoring Center > Monitoring Configuration from the main menu. In the navigation pane, choose Performance Threshold Maintenance.
    2. On the Performance Threshold Maintenance page, locate the row that contains the target monitoring indicator.
    3. Click to check whether the threshold settings are appropriate.
      • If yes, go to 3.
      • If no, go to 2.

  2. Modify the alarm threshold policy of the indicator.

    1. Modify the alarm threshold based on the actual indicator data.
    2. Wait for 240 minutes, choose Alarms > Current Alarms from the main menu, and check whether the alarm is cleared.
      • If yes, no further action is required.
      • If no, go to 3.

  3. If services are running properly, contact service O&M personnel to expand or migrate services. In other cases, contact technical support for assistance.

Alarm Clearance

When the fault is rectified, the system will automatically clear the alarm. Manual clearing is not required.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 37957

Downloads: 31

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next