Key concepts
KakaoCloud Alert Center is a service that allows you to configure alert policies and set up notification channels to receive alerts when events or resource failures occur in KakaoCloud services. By configuring alerts in Alert Center and receiving notifications in a timely manner, you can quickly identify and resolve issues occurring in KakaoCloud services.
Manage IAM roles
Role management in Alert Center follows KakaoCloud's IAM role-based access control (RBAC). This allows you to manage alert recipients in conjunction with IAM project roles. By default, project administrators and project members can manage alert recipients. For more details on IAM roles and user role management, refer to IAM > Key concepts and Manage user IAM roles.
Starting March 18, 2025, IAM roles in Alert Center will be further segmented.
The existing project member permissions will be reduced, and new roles such as Alert Center organization viewer, Alert Center project manager, and Alert Center project viewer will be added.
👉🏻 Therefore, to ensure smooth usage of Alert Center services by project members, organization administrators and project administrators should assign appropriate roles before March 18, 2025.
You can check your IAM role permissions in KakaoCloud Console > Top-right profile > Account information.
Organization roles
Starting March 18, 2025, IAM organization roles in Alert Center will be updated as follows. Roles marked with *
are newly added.
Permission | Organization administrator (admin) | Alert Center organization manager (manager) (previously Alert Center administrator (admin)) | Alert Center organization viewer (viewer)* |
---|---|---|---|
Create, edit, delete alert policies | ✓ | ✓ | |
View alert policies | ✓ | ✓ | ✓ |
Create, edit, delete notification channels | ✓ | ✓ | |
View notification channels | ✓ | ✓ | ✓ |
View outgoing history | ✓ | ✓ | ✓ |
Project roles
Starting March 18, 2025, IAM project roles in Alert Center will be updated as follows. Roles marked with *
are newly added.
Since project member roles have been reduced, ensure that appropriate IAM roles are assigned to organization/project members in advance for seamless use of Alert Center services.
- Project members will not have permissions to create, edit, or delete alert policies and notification channels.
- Assign the Alert Center project manager (manager) role to members who need permissions to create, edit, or delete alert policies and notification channels.
Permission | Project administrator (admin) | Alert Center project manager (manager)* | Alert Center project viewer (viewer)* | Project member (member) | Project reader (reader) |
---|---|---|---|---|---|
Create, edit, delete alert policies | ✓ | ✓ | |||
View alert policies | ✓ | ✓ | ✓ | ✓ | ✓ |
Create, edit, delete notification channels | ✓ | ✓ | |||
View notification channels | ✓ | ✓ | ✓ | ✓ (cannot view recipient list) | ✓ (cannot view recipient list) |
View outgoing history | ✓ | ✓ | ✓ | ✓ | ✓ |
Alert policies
An alert policy defines the conditions and methods for receiving notifications. In Alert Center, you can configure alerts based on service events. Events can be set per service, and additional services will be added continuously. For more details, refer to Create and manage alert policies.
Services supporting alert configuration by event condition type
Category | Supported services in kr-central-2 | Description |
---|---|---|
Metric | - Beyond Compute Service ㄴ Virtual Machine ㄴ Bare Metal Server ㄴ GPU - MemStore - MySQL - Load Balancing - Monitoring Flow - PostgreSQL - Pub/Sub | Configure metric-based alerts for overall system performance |
Log | - Beyond Compute Service ㄴ Virtual Machine ㄴ Bare Metal Server ㄴ GPU | Configure log-based alerts |
Event | Organization events - IAM - Billing Project events - Various cloud services | Specialized event alerts for KakaoCloud services |
Metric alert policies
Metric-based policies monitor the status and changes of computing resources, allowing you to respond to system-wide performance fluctuations. You can configure alerts for various events related to CPU, memory, disk I/O, and more.
For detailed explanations of provided metrics, refer to the Monitoring document.
Log alert policies
Log-based policies help efficiently manage operational issues using instance logs. You can set specific keywords in log values, and alerts will be triggered whenever these keywords appear. Alert Center provides various keyword types beyond simple text strings, such as instance names.
Log alert keyword types
Category | Description |
---|---|
Keyword | Search for a specific string regardless of type |
Instance ID | Instance ID of an instance installed on Beyond Compute Service (BCS) |
Host | Hostname of an instance installed on Beyond Compute Service (BCS) |
File path | Path of the log file |
Event alert policies
Event-based policies operate by detecting real-time events triggered by specific actions. The Alert Center service provides relevant event notifications for each KakaoCloud service.
For example, the Container Registry service offers event notifications for repository deletion/creation, garbage collection execution/completion, and more. You can also apply detailed filters to receive more precise notifications.
Notification channels
You can configure notification channels and recipients for receiving event alerts. Alert recipients can be set as IAM users within a project to receive alerts when service events occur. For more details, refer to Create and manage notification channels.
Available channels
Category | Description |
---|---|
Sends alerts via registered email | |
SMS | Sends alert messages via registered phone number |
KakaoTalk alert | Sends alerts via KakaoTalk business messaging service |
Slack | Sends chatbot messages to a configured Slack channel |
Webhook | Sends alerts to a configured webhook |
Pub/Sub | Sends alerts to a configured KakaoCloud Pub/Sub topic |
Sent history
You can view message delivery results for each service. Message statuses include Success
, Failure
, and Sending
. You can also check the number of failed messages, error codes, and failure details. For more details, refer to View sent history.