type AlarmChange

alarm_id

ID of the alarm.

Data type Cardinality Parent element Child element
String 0..1 None None

detail

Details (in JSON format) of the change.

Refer to "Details of the alarm history" below for details.

Data type Cardinality Parent element Child element
String 0..1 None None

event_id

ID of the change event.

Data type Cardinality Parent element Child element
String 0..1 None None

on_behalf_of

ID of the project.

Data type Cardinality Parent element Child element
cron 0..1 None None

project_id

ID of the project.

Data type Cardinality Parent element Child element
String 0..1 None None

timestamp

Change datetime of the alarm.

Format: "YYYY-MM-DDThh:mm:ss.SSSSSS"

Data type Cardinality Parent element Child element
Datetime 0..1 None None

type

Type of alarm history.
  • creation: Create
  • change: Change
  • state transition: State transition
  • deletion: Delete
  • action: Action
Data type Cardinality Parent element Child element
Enum 0..1 None None

user_id

ID of the user.

Data type Cardinality Parent element Child element
String 0..1 None None

Table 1. Details of the alarm history
type Description
creation Information (in JSON format) on a new alarm. Refer to "type Alarm" for details (note that fields such as "threshold_rule" and "combination_rule" are changed to "rule").
change Information (in JSON format) on a changed alarm. Refer to "type Alarm" for details (note that fields such as "threshold_rule" and "combination_rule" are changed to "rule").
state

transition

 Value (in JSON format) of the "state" field of an alarm after transition.
deletion Information (in JSON format) on a deleted alarm. Refer to "type Alarm" for details (note that fields such as "threshold_rule" and "combination_rule" are changed to "rule").
action Contain the following (in JSON format):
  • action_state: Execution result of the action
    • Succeeded: If the action was successful
    • Failed: If the action failed
  • action: Information of the executed action
  • region: Region name
  • reason: Reason why the action was executed
  • alarm: Information on the alarm
    • Refer to "type Alarm" for details (note that fields such as "threshold_rule" and "combination_rule" are changed to "rule").
  • previous: State of the alarm before transition
  • error: Error information of the action execution result (status code).
  • error_message: Error message of alarm execution (if action_state is "Failed").

If action_state is "Failed", check the relevant details based on the action service and value or "error":

Table 2. Action execution errors
Target service error Description Action
autoscale 401 The user does not have the privileges to perform operations on the specified stack. Create the alarm again as a user that has privileges to perform operations on the target stack.
404 The specified stack or resource does not exist. Check the stack ID, stack name, and resource name, and change them to the correct value if necessary.
500 Internal error. Contact Fujitsu technical support.
503 The service cannot be used temporarily. Contact Fujitsu technical support.
compute 401 The user does not have the privileges to perform operations on the specified instance. Create the alarm again as a user that has privileges to perform operations on the target instance.
404 The specified instance does not exist. Check the specified instance ID, and change it to the correct value if necessary.
500 Internal error. Contact Fujitsu technical support.
503 The service cannot be used temporarily. Contact Fujitsu technical support.
queue 400 The specified queue does not exist. Check the specified queue name, and change it to the correct value if necessary.
403 The number of messages in the queue has reached the upper limit or the user does not have privileges to perform operations on the specified queue. <=Delete=> If the number of messages in the queue has reached the upper limit, delete messages from the queue.

If the user does not have privileges, create the alarm again as a user that has privileges to perform operations on the specified queue.
500 Internal error. Contact Fujitsu technical support.
503 The service cannot be used temporarily. Contact Fujitsu technical support.
mail 500 Internal error. Contact Fujitsu technical support.
503 The service cannot be used temporarily. Contact Fujitsu technical support.