Integration
- Print
- PDF
Integration
- Print
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
Available in Classic and VPC
This page explains how to create and manage channels in Integration.
You can send an event occurred to the endpoint URL specified by the user when it occurs by creating a channel in Integration.
To access the Integration menu, access NAVER Cloud Platform portal and click [Console] > Services > Management & Governance > Cloud Insight (Monitoring) > Configuration > Integration in order.
Integration page
The Integration page is laid out as follows.
Field | Description |
---|---|
① Menu name | Name of the menu currently being viewed |
② Basic features | Features displayed when you initially enter the Integration menu |
③ Post-creation features | Features enabled after creating a channel |
④ Search window | You can search channels with channel names. |
⑤ Channel list | Created channels are displayed. |
Create channel
The following shows how to create a channel.
- In the NAVER Cloud Platform console, click Services > Management & Governance > Cloud Insight (Monitoring) in order.
- Click Configuration> Integration in order.
- Click the [Create channel] button.
- Enter the channel information in the channel creation popup window, and click the [Create] button.
- For the Type, only Outgoing Webhook is currently supported.
- Enter Endpoint address.
- Check Payload. You can edit Payload freely. (Refer to Edit payload)
- You can add or delete Header. As for the Header, there are limitations as follows:
- Up to 10 headers are possible, and each heather (including key/value) is limited to 100 bytes.
- For the header value, only English letters, numbers, hyphens (-), and underscores (_) are permitted.
- Click the [Data transfer test] button to see if the Endpoint address, payload, and header are valid.
Edit channel
The following shows how to modify a channel.
- In the NAVER Cloud Platform console, click Services > Management & Governance > Cloud Insight (Monitoring) in order.
- Click Configuration> Integration in order.
- Select the channel to edit, and click the [Edit] button.
- Make the necessary changes, and click the [Save] button.
- When editing the Endpoint address, payload, and header, click the [Data transfer test] button to see if they are valid.
Delete channel
The following shows how to delete a channel.
- In the NAVER Cloud Platform console, click Services > Management & Governance > Cloud Insight (Monitoring) in order.
- Click Configuration> Integration in order.
- Select the channel to delete, and click the [Delete] button.
- Check the details in the notification popup window, and click the [Delete] button.
Edit payload
Here is detailed information on the payload editing feature.
- When creating or editing channels, the Payload editing feature is provided.
- Only JSON format is available for the Payload, and it is limited to 15 KB at maximum.
- It provides 22 variables in total, which can be used in the format, such as #{variable name}.
Provided variables
name | description | example |
---|---|---|
DOMAIN_CODE | Platform information about the resource where the event occurred | PUB |
REGION_CODE | Region information about the resource where the event occurred | KR |
PRODUCT_KEY | cw_key of the resource where the event occurred | "123123123123123" |
PRODUCT_NAME | Product name of the resource where the event occurred | "Server(VPC)" |
RESOURCE_NAME | Name of the resource where the event occurred | "server001" |
DIMENSIONS | Dimension information about the resource where the event occurred | "{"type": "svr", "instanceNo": "11111111"}" |
RULE_ID | Event Rule ID | 321321321321321321 |
RULE_NAME | Name of event rule | "integration-rule" |
DATA_TIME | Data collection time | 1644650534051 |
LEVEL | Event rule's level | INFO |
OPERATOR | Event rule's operator | GE |
METRIC | Event rule's target metric | avg_cpu_used_rto |
UNIT | Unit of the event rule's target metric | "%" |
AGGREGATION_METHOD | Aggregation information about the event rule's target metric | AVG |
CRITERIA | Event rule's condition value that the user set | 0.0 |
DURATION | Event rule's retention time that the user set | 1 |
ALARM_START_TIME | Event occurrence time | 1644650534051 |
ALARM_END_TIME | Event end time | 1644650594050 |
EVENT_CAUSE_TYPE | Cause of the event | RULE_EVENT, REMINDER_EVENT |
VALUE | Value at the time when the event occurred | 0.0 |
CURRENT_VALUE | Current value | 1.0 |
EVENT_STATUS | Status of the event | OPEN, REMIND, RESOLVE |
Was this article helpful?