Show Table of Contents
第4章 クラウドアラート API
4.1. アラートの一覧表示
4.1.1. 説明
アプリに関連付けれたアラートを一覧表示します。
4.1.2. エンドポイント
- URI: /box/srv/1.1/cm/eventlog/alert/list
- メソッド: POST
4.1.3. リクエストボディー
{
"appGuid":"<24 char String>",
"env":"<environment>"
}4.1.4. レスポンスボディー
4.1.4.1. 成功
{
"list":[
{
"alertName": "AppTerminated",
"emails": "test@example.com",
"enabled": true,
"env": "dev",
"eventCategories": "APP_STATE",
"eventNames": "",
"eventSeverities": "FATAL",
"guid": "iV5E_ASJcQ_83TOgbDpYbHIp",
"sysCreated": "2013-06-28 11:09:05",
"sysModified": "2013-06-28 11:09:05",
"uid": "ajBTU-_UMtc7ggOCL6MbZRP_"
},
...
],
"status":"ok"
}4.1.4.2. エラー
{
"status": "error",
"message": "<error_message>"
}4.2. アラートの作成
4.2.1. 説明
アプリの新規アラートを作成します。
4.2.2. エンドポイント
- URI: /box/srv/1.1/cm/eventlog/alert/create
- メソッド: POST
4.2.3. リクエストボディー
{
"alertName": "<The name of the alert, for example, TestAlert>",
"emails": "<The recipients of the alert>",
"enabled": "<true|false>",
"env": "<environment>",
"eventCategories": "<any of the event categories, for example, APP_STATE>",
"eventNames": "<any of the event name, for example, APP_TERMINATED. NOTE, if this is specified as well as the event categories and severities, need to make sure categories and severies are valid for the events>",
"eventSeverities": "<any of the event severities, for example, FATAL>",
"uid": "<the guid of the app>"
}4.2.4. レスポンスボディー
4.2.4.1. 成功
{
"alertName": "TestAlert",
"emails": "test@example.com",
"enabled": true,
"env": "dev",
"eventCategories": "APP_STATE",
"eventNames": "TERMINATED",
"eventSeverities": "FATAL",
"guid": "F9zwTLwAwsaTZP7I45sOtRKJ",
"sysCreated": "2013-07-04 15:32:54",
"sysModified": "2013-07-04 15:32:54",
"uid": "ajBTU-_UMtc7ggOCL6MbZRP_",
"status":"ok"
}4.2.4.2. エラー
{
"status": "error",
"message": "<error_message>"
}4.3. アラートの更新
4.3.1. 説明
アプリの既存アラートを更新します。
4.3.2. エンドポイント
- URI: /box/srv/1.1/cm/eventlog/alert/update
- メソッド: POST
4.3.3. リクエストボディー
{
"guid":"<The unique id of the alert>",
"alertName": "<The name of the alert, for example, TestAlert>",
"emails": "<The recipients of the alert>",
"enabled": "<true|false>",
"env": "<environment>",
"eventCategories": "<any of the event categories, for example, APP_STATE>",
"eventNames": "<any of the event name, for example, APP_TERMINATED. NOTE, if this is specified as well as the event categories and severities, need to make sure categories and severies are valid for the events>",
"eventSeverities": "<any of the event severities, for example, FATAL>",
"uid": "<the guid of the app>"
}4.3.4. レスポンスボディー
4.3.4.1. 成功
{
"alertName": "TestAlert",
"emails": "test@example.com, test1@example.com",
"enabled": true,
"env": "dev",
"eventCategories": "APP_STATE",
"eventNames": "TERMINATED",
"eventSeverities": "FATAL",
"guid": "F9zwTLwAwsaTZP7I45sOtRKJ",
"sysCreated": "2013-07-04 15:32:54",
"sysModified": "2013-07-04 15:32:54",
"uid": "ajBTU-_UMtc7ggOCL6MbZRP_",
"status":"ok"
}4.3.4.2. エラー
{
"status": "error",
"message": "<error_message>"
}4.4. アラートの削除
4.4.1. 説明
アプリの既存アラートを削除します。
4.4.2. エンドポイント
- URI: /box/srv/1.1/cm/eventlog/alert/delete
- メソッド: POST
4.4.3. リクエストボディー
{
"guid":"<The unique id of the alert>",
"alertName": "<The name of the alert, for example, TestAlert>",
"emails": "<The recipients of the alert>",
"enabled": "<true|false>",
"env": "<environment>",
"eventCategories": "<any of the event categories, for example, APP_STATE>",
"eventNames": "<any of the event name, for example, APP_TERMINATED. NOTE, if this is specified as well as the event categories and severities, need to make sure categories and severies are valid for the events>",
"eventSeverities": "<any of the event severities, for example, FATAL>",
"uid": "<the guid of the app>"
}4.4.4. レスポンスボディー
4.4.4.1. 成功
{
"alertName": "TestAlert",
"emails": "test@example.com, test1@example.com",
"enabled": true,
"env": "dev",
"eventCategories": "APP_STATE",
"eventNames": "TERMINATED",
"eventSeverities": "FATAL",
"guid": "F9zwTLwAwsaTZP7I45sOtRKJ",
"sysCreated": "2013-07-04 15:32:54",
"sysModified": "2013-07-04 15:32:54",
"uid": "ajBTU-_UMtc7ggOCL6MbZRP_",
"status":"ok"
}4.4.4.2. エラー
{
"status": "error",
"message": "<error_message>"
}4.5. メール通知の一覧表示
4.5.1. 説明
アプリについて送信されるメール通知をすべて一覧表示します。
4.5.2. エンドポイント
- URI: /box/srv/1.1/cm/eventlog/alert/listAudit
- メソッド: POST
4.5.3. リクエストボディー
{
"appGuid":"<24 char String>",
"env":"<environment>"
}4.5.4. レスポンスボディー
4.5.4.1. 成功
{
"list":[
{
"alertName": "AppTerminated",
"body": "<Email Content>",
"env": "dev",
"guid": "RD0O6ByAU_BwJRolaZUhXpl8",
"recipients": "wei.li@feedhenry.com",
"subject": "FeedHenry DynoFarm Testing Alert: AppTerminated - EventsTestApp1 (ajBTU-_UMtc7ggOCL6MbZRP_)",
"sysCreated": "2013-07-04 14:24:23",
"sysModified": "2013-07-04 14:24:23",
"uid": "ajBTU-_UMtc7ggOCL6MbZRP_"
},
...
],
"status":"ok"
}4.5.4.2. エラー
{
"status": "error",
"message": "<error_message>"
}
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.