This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

ServiceWatch

1 - Overview

Service Overview

ServiceWatch is a service that provides various tools to collect metrics, logs, events, and other data from resources created on the Samsung Cloud Platform for monitoring, offering observability of resources overall, including performance and operational status.

Features

We provide the following special features.

  • Resource Monitoring: Collects and visualizes performance metrics of resources (CPU Usage, etc.). Also creates a dashboard that allows visual inspection of multiple metrics in one place for quick overview.
  • Alert Policy Configuration and Automatic Notification: You can create alert policies by setting predefined conditions and thresholds, and when a threshold is exceeded, you receive notifications, allowing you to quickly check and respond to resource status.
  • Log Analysis and Storage: Collect logs generated from resources for easy viewing and searching. Collected logs are stored in log groups for management, and log groups can be stored for free up to 5GB. Additionally, you can set a log retention policy to specify the retention period, and logs that exceed the retention period do not require separate management.
  • Cost Efficiency: ServiceWatch offers a flexible pay-as-you-go pricing model, allowing cost‑effective usage. It also provides a free usage tier, so you can try it for free and then scale to a paid plan as needed.

Provided features

We provide the following features.

  • Metric Monitoring
    • Metrics: ServiceWatch receives metric data from services of the Samsung Cloud Platform, and ServiceWatch collects and stores the metric data to provide it to users.
    • Dashboard: Visualizes metrics of a single region to provide an integrated view of resources. In ServiceWatch, dashboards are divided into automatically generated service dashboards for each service and user-created custom dashboards.
    • Alert: Provides an alert feature that allows monitoring of metric changes based on user-defined thresholds and sends notifications when thresholds are exceeded.
  • Log Monitoring
    • ServiceWatch provides log management capabilities. Logs collected from Samsung Cloud Platform services are stored in log groups for management. You can set log retention policies to manage the retention period. Additionally, you can view and search log data through the console, and it offers the ability to store log groups in Object Storage.
  • ServiceWatch Agent
    • Through the ServiceWatch Agent, you can collect detailed metrics on processes, CPU, memory, disk usage, and network performance from Virtual Servers, GPU Servers, Bare Metal Servers, and other resources. GPU performance metrics can also be collected. Additionally, the Agent can collect logs generated by the resources. (Planned for December 2025)
  • Event Monitoring
    • ServiceWatch can create event rules from system events about changes to resources created in the Samsung Cloud Platform, allowing you to receive notifications under specific conditions.

Component

Metric

Metrics refer to system performance data. By default, we provide basic monitoring based on free metrics for resources of services integrated with ServiceWatch. Additionally, services such as Virtual Server can enable detailed monitoring to provide paid metrics.

Indicator data can be viewed for up to 15 months (455 days).

For detailed information related to metrics, please refer to Metrics.

log

You can collect, store, and view logs of systems, applications, and services used in Samsung Cloud Platform services such as Virtual Server resources and Kubernetes Engine.

For detailed information related to logs, refer to 로그.

event

An event represents a change in the environment in the Samsung Cloud Platform service. Below are examples of events.

  • Generates an event when the status of a Virtual Server changes from Stopped to Running.
  • Generates an event when a new bucket is created in Object Storage.
  • An event is generated when an IAM user is removed from a user group.

For detailed information about events, refer to the Events.

Dashboard

ServiceWatch provides a pre-built service dashboard for each service automatically, and users can also create dashboards manually.

information
Pre-built dashboards for each service will be available starting March 2026.

ServiceWatch Agent

The ServiceWatch Agent is a software component that collects metrics and logs from Virtual Servers, GPU Servers, and on‑premises servers, among others. This enables monitoring of infrastructure and applications with greater granularity than the default monitoring provided out of the box.

Reference

Collecting custom metrics/logs via the ServiceWatch Agent is currently available only on Samsung Cloud Platform For Enterprise. It will be offered in other offerings in the future.

Constraints

The limitations of ServiceWatch are as follows.

CategoryExplanation
Metric query periodMetric queries can be set up to a maximum of 455 days from the time of query
  • Applies to dashboards, widgets, and metric queries
Number of metric queriesYou can select up to 500 indicators and view them in a graph.
Download indicator image fileImage download available for metric data of up to 100 metrics
Export Metrics to Object StorageUp to 10 metrics, and exporting to Obect Storage is possible for metric data with a maximum query period of up to 2 months (63 days).
Number of widgets/metrics per dashboard
  • Up to 500 widgets per dashboard
  • Up to 500 metrics per widget within a dashboard
  • A single dashboard can have up to 2,500 metrics across all its widgets
Number of alert policiesAccount/per region 5,000 or fewer
Alarm HistoryAlert history is available for 30 days
Number of notification recipients per alert policy100 or fewer
Number of log groupsAccount/10,000 or fewer per region
Log downloadExcel download: up to 1 MB per log event, with a maximum of 10,000 log events can be downloaded
  • If a log event exceeds 1 MB or the number of log events exceeds 10,000, it is recommended to use log group export
Number of log group export tasks
  • Can execute export tasks one per Account at a time
Log event size1 MB or less
Number of event rulesAccount/No more than 300 per region
Event pattern size2 MB or less
Number of notification recipients per event rule100 or fewer
Table. ServiceWatch constraints

The following is ServiceWatch’s monthly free offering details.

CategoryFree offering
logUp to 5 GB of storage per month
indicator
  • Basic monitoring metrics for each service
  • Detailed monitoring metrics / custom metrics / log pattern metrics, 10 per month
DashboardFor dashboards referencing 50 or fewer metrics, up to 3 per month
  • If referencing 51 or more metrics, billing for 1 dashboard per month
Alert Policy10 per month
Table. ServiceWatch free offering scope

Provision status by region

ServiceWatch is available in the following environments.

RegionWhether provided
Korea West (kr-west1)Provide
Korea East (kr-east1)Provide
South Korea 1 (kr-south1)Provide
South Korea South 2 (kr-south2)Provide
South Korea 3(kr-south3)Provide
Table. ServiceWatch regional availability status

Preliminary Service

There are no prerequisite services for ServiceWatch.

1.1 - Metric

Metric

Metrics are data about system performance. By default, many services provide free metrics for resources (e.g., Virtual Server, File Storage, etc.), which are offered as basic monitoring through ServiceWatch. Detailed monitoring can be used for certain resources such as Virtual Server.

Indicator data is retained for 15 months (455 days), so you can view both the latest data and historical data.

TermExampledescription
namespaceVirtual ServerLogical distinctions for separating and grouping metrics
Metric (metric)CPU usagethe name of the specific data you want to collect
Dimension(Dimensions)resource_idUnique identifier for the metric
Collection interval5 minutesPlease refer to the collection interval of metric data from each service that provides metrics
StatisticsaverageHow to aggregate metric data over a specified period
unit%Statistical measurement units
  • unit please refer to.
Aggregation period5 minutesThe period for aggregating collected metric data
AlertCPU usage >= 80%Occurs for 5 minutesIf CPU usage stays above 80% for 5 minutes, change to Alert state.
Table. ServiceWatch metric terms

Namespace

A namespace is a logical separation used to distinguish and group ServiceWatch metrics. In Samsung Cloud Platform services, namespaces are generally the same as the service name, and can be found in the ServiceWatch 연계 서비스 목록.

For custom metrics, users can define a namespace in ServiceWatch to distinguish them from other metrics, and can define it via the ServiceWatch Agent settings or OpenAPI. Detailed information about custom metrics and logs can be found in 사용자 정의 지표 및 로그.

Metric (metric)

A metric represents a set of data points sorted chronologically as they are collected in ServiceWatch. Each data point consists of a timestamp, the collected data, and the unit of the data.

For example, the CPU utilization of a specific Virtual Server is one of the basic monitoring metrics provided by Virtual Server. The data point itself can be generated by any application or activity that collects data.

By default, the Samsung Cloud Platform services integrated with ServiceWatch provide resource metrics for free. Detailed monitoring for some resources is offered as a paid service and can be enabled in each service.

Metrics can only be viewed in the region where they were created. Metrics cannot be arbitrarily deleted by users. However, if new data is not posted to ServiceWatch, they will automatically expire after 15 months. Data points older than 15 months (455 days) expire sequentially, and when new data points are added, data older than 15 months (455 days) is deleted.

Timestamp

The timestamp of a data point is the time information indicating when the data point was recorded. Each metric data point consists of a timestamp (time) and data.

A timestamp consists of hours, minutes, seconds, and a date.

Metric retention period

We maintain ServiceWatch metric data as follows.

  • Data points with a collection interval set to 60 seconds (1 minute) are available for up to 15 days.
  • Data points with a collection interval set to 300 seconds (5 minutes) are available for up to 63 days.
  • Data points with a collection interval set to 3600 seconds (1 hour) are usable for up to 455 days (15 months).

Data points that were initially collected at a short interval are downsampled and stored for long-term retention.

For example, if data is collected at a 1‑minute interval, it is retained in 1‑minute granularity for 15 days. After 15 days, the data continues to be retained but can only be queried in 5‑minute intervals. After 63 days, the data is re‑aggregated and provided in 1‑hour intervals. If you need to retain metric data points longer than the metric retention period, you can archive them separately using the File Download or Object Storage Export features.

Dimension(Dimensions)

A key-value pair that serves as a unique identifier for a metric, allowing you to classify and filter data points.

For example, you can identify metrics for a specific server by using the resource_id dimension of the Virtual Server metrics.

Collection interval

It refers to the interval for collecting data points for each service’s metrics and is provided according to the collection interval predefined by each service.

Refer to each service’s ServiceWatch metrics page for the metric collection interval.

Reference
Refer to Metrics and Log Monitoring for the metric page of ServiceWatch integrated services.

For example, Virtual Server provides a collection interval of 5 minutes during basic monitoring, and a 1‑minute interval when detailed monitoring is enabled.

Statistics

Statistics are a method of aggregating metric data over a specified period. ServiceWatch provides data aggregated as statistics based on metric data points supplied to ServiceWatch from each service. Aggregation is performed within the specified aggregation period using namespace, metric name, dimension, and data point units.

The provided statistics are sum, average, minimum, maximum.

  • Total: sum of all data point values collected during the period
  • Average: During the specified period, (sum of all data pointer values during that period) / (number of data pointers during that period) value
  • Minimum: the lowest value observed during the specified period
  • Maximum: the highest value observed during the specified period

unit

Each statistic has a measurement unit. Examples of units include Bytes, Second, Count, Percent, etc.

Aggregation period

Each statistic calculates the data points of the metric collected during the selected aggregation interval. The aggregation interval can be chosen from 1 minute, 5 minutes, 15 minutes, 30 minutes, 1 hour, 3 hours, 6 hours, 12 hours, or 1 day, with the default being 5 minutes. The aggregation interval is closely related to the collection frequency of metric data points, and to obtain correct aggregation results, the aggregation interval must be equal to or longer than the collection frequency.

For example, if you select average, choose 5 minutes as the aggregation period, and pick a metric with a 1‑minute collection interval, data points are collected every minute and the average is calculated over the data points collected during the 5‑minute period. Conversely, if the aggregation period is shorter than the collection interval, it means a valid aggregation result cannot be obtained.

Downsampling is applied for long-term storage of metric data. For example, if data is collected at a 1‑minute interval, after 15 days the data can only be queried in 5‑minute increments. If you set the aggregation period for such metrics from 5 minutes to 30 minutes, up to 5 minutes may be required to retrieve the downsampled data correctly. After 63 days, the data is re‑aggregated and provided in 1‑hour intervals. At that point, selecting an aggregation period from 1 hour to 1 day may take up to 1 hour to retrieve the data correctly. This occurs because aggregating the downsampled metric data takes time, which can cause aggregation delays.

Reference
When querying metric data, the most recent data point may not be displayed due to aggregation delay. In this case, you can either reduce the aggregation period to be smaller than the set value or query after a certain time (5 minutes or 1 hour) to view the data correctly.
Aggregation periodAggregation delay
1 minute-
5 minutesup to 5 minutes
15 minutesup to 5 minutes
30 minutesup to 5 minutes
1 hourup to 1 hour
3 hoursup to 1 hour
6 hoursup to 1 hour
12 hoursup to 1 hour
Day 1up to 1 hour
Table. Aggregation delay by ServiceWatch aggregation period

Alert

When creating an alert policy, you can evaluate a single metric over the specified evaluation period, and if it meets the condition set based on the threshold, you can notify the user with an alert.

The alarm status is classified as Alert (alert), Normal (normal), Insufficient data (no data).

  • Alert(Alert): when the metric meets the configured condition
  • Normal (Normal): when the indicator does not meet the set conditions.
  • Insufficient data(no data): when the metric data does not exist, is missing, or has not yet arrived

When the alarm status is Alert, after evaluating the alarm, if it deviates from the condition, the alarm status changes back to Normal.

For detailed information about alerts, refer to the 경보 entry.

Basic monitoring and detailed monitoring

ServiceWatch provides two types of monitoring: basic monitoring and detailed monitoring.

The Samsung Cloud Platform services integrated with ServiceWatch provide basic monitoring by publishing a default set of metrics to ServiceWatch for free. By default, if you use any of these services, basic monitoring is automatically enabled and can be viewed in ServiceWatch.

Reference
The services that provide basic monitoring can be found in the ServiceWatch Integrated Service List and will be gradually expanded.

Detailed monitoring is available only for certain services and incurs charges. To use detailed monitoring, you must enable it in the service details.

Detailed monitoring options vary depending on the service provided.

  • The default monitoring for Virtual Server has a collection interval of 5 minutes. When detailed monitoring is enabled, the metrics provided by default monitoring are collected at a 5 minutes → 1 minute interval.
  • Basic monitoring of Object Storage is provided for basic metrics, and enabling replication metrics provides additional replication metrics.

The following includes services and guides that provide detailed monitoring.

Table. ServiceWatch detailed monitoring service

1.2 - Alert

Alert

You can create alerts that monitor metrics and send notifications. For example, you monitor the CPU usage and disk read/write of a Virtual Server, then send a notification to the user to handle the increased load.

Alert Policy

The alert policy can monitor metrics of the same Account and evaluate alerts for a single metric. This alert policy compares the specified threshold with metric conditions and sends a notification when the conditions are met.

If you disable the alert policy, its evaluation continues, but you can restrict sending alerts to the designated recipients. If you want to temporarily stop sending alerts for resources with an alarm policy configured, you can use alarm policy deactivation.

When you enable an alert policy, evaluation of the policy starts, and according to the configured conditions, the alert status changes to Alert, with a notification sent each time the alert status changes.

The alarm policy status indicates whether the alarm policy is enabled or disabled.

Alert policy statusdescription
ActiveIn a state where the alert policy is enabled, notifications can be sent according to the configured conditions
  • Evaluates alerts according to the settings and sends notifications to the designated recipients
InactiveAlert policy is disabled, and notification sending is restricted.
  • Alert evaluation for the policy is not stopped, only notification sending is limited.
Table. Alarm Policy Status

You can set alert stages in the alert policy. Depending on the alert stage, the alert color (red/pink/purple) is displayed differently, allowing visual distinction of stages by color. You can filter alarm policies by their alarm level and view policies for each level.

Alert Leveldescription
HighWhen you set the step for the alarm policy condition to High, the alarm level is displayed in red.
MidleIf you set the stage to Middel in the alarm policy condition, the alarm stage is displayed in pink.
LowIf you set the stage to Middel in the alert policy condition, the alert stage is displayed in purple.
Table. Alert Policy Stages

Alert Status

The alarm state changes according to the alarm evaluation of the alarm policy. The alarm state is divided into three states: Normal (normal), Insufficient data (insufficient data), Alert (alert).

Alarm statusdescription
NormalIndicates a normal state that does not meet the conditions set in the alert policy
  • Normal state is displayed in green
Insufficient dataThe alarm policy has just been created, the metric is unavailable, or there is insufficient data to determine the alarm state from the metric
  • The Insufficient data state is displayed in gray
AlertState that meets the conditions set in the alert policy
  • Alert state is displayed in red
  • When the state changes to Alert, send a notification to the user
Table. Alarm Status
Reference
When an alarm policy is first created, the alarm state is initialized to Insufficient data. When metric data is later collected, the alarm state changes to Normal or Alert.

Alert Evaluation

Termdescription
Metric data pointStatistical data calculated from indicator data. Data points consist of a timestamp, collected statistical data, and the unit of the data
  • The statistics of a data point are calculated as sum, average, minimum, and maximum
Metric collection intervalTime interval for collecting metric data per service
  • It is specified per metric in the namespace
  • Example: 1 minute or 5 minutes
Alert evaluation cycleThe time interval for evaluating whether an alert meets the condition
  • If the metric collection interval is 1 minute or more, fix the alert evaluation interval to a 1 minute granularity
  • If the alert evaluation range × metric collection interval exceeds 24 hours, fix the alert evaluation interval to a 1 hour granularity
Alert Evaluation ScopeIt is recommended to set the evaluation time range for alarm evaluation
  • to the collection interval or multiple of the collection interval
Alarm evaluation count / Alarm violation countDuring the alarm evaluation interval, if the condition is satisfied for violation count out of evaluation count, the alarm state is switched to Alert
  • violation count can be set less than or equal to evaluation count
  • The default is set to 1
Alert evaluation intervalAlarm evaluation range(seconds) X Alarm evaluation count
Table. Alarm Evaluation Terms

For example, for a metric with a 1‑minute collection interval, if you set a 1‑minute evaluation window with 4 violations out of 5 evaluation attempts, the evaluation interval is 5 minutes. For a metric with a 5‑minute collection interval, if you set a 10‑minute evaluation window with 3 violations out of 3 evaluation attempts, the evaluation interval is 30 minutes.

CategoryExample 1Example 2
Metric collection interval1 minute5 minutes
Alert evaluation cycle (fixed)1 minute1 minute
Alert Evaluation Scope1 minute10 minutes
Alarm evaluation count5 times3 times
Alarm violation count4th3 times
Alert evaluation interval (seconds)5 minutes (300 seconds)30 minutes (1,800 seconds)
ConditionIf evaluated 5 times within 5 minutes and meets the condition 4 times, change the alarm state to Alert.If evaluated three times within 30 minutes and the three-time condition is met, change the alarm state to Alert.
Table. Alarm Evaluation Example

Evaluation Scope

The evaluation scope of an alert policy is the time range used for alert evaluation.

  • It is recommended to set it as the indicator’s collection interval or a multiple of the collection interval.
  • You can enter up to 604,800 (7 days) seconds.
Caution
If the evaluation range is set smaller than the collection interval or not a multiple of the collection interval, the alarm evaluation may not work properly.
Evaluation scopeConfigurable evaluation count
7 days (604,800 seconds)1
1 day (86,400 seconds)7 or less
6 hours (21,600 seconds)28 or less
1 hour (3,600 seconds)168 or less
15 minutes (900 seconds)96 or less
5 minutes (300 seconds)288 or less
1 minute (60 seconds)1,440 or less
Table. Configurable number of evaluations by evaluation range
Guide

There are the following limitations on the evaluation scope and the number of evaluations:

  • When the evaluation range is at least 1 hour (3,600 seconds), the evaluation interval (evaluation count × evaluation range) can be up to 7 days (604,800 seconds).
  • When the evaluation range is less than 1 hour (3,600 seconds), the evaluation interval (evaluation count × evaluation range) can be up to 1 day (86,400 seconds).

condition

The conditions for alarm evaluation require a conditional operator and threshold setting.

Termdescription
StatisticsMethod for calculating metric data over the evaluation period for alert assessment
conditional operatorFor alarm evaluation, after calculating metric data over the evaluation period, select the conditional operator to compare the value with the threshold.
thresholdFor alarm evaluation, calculate the metric data over the evaluation range and then define a threshold to compare the values using conditional operators.
Table. Condition Terms

When the namespace is Virtual Server and the metric is CPU Usage (unit: %), the alarm evaluation condition is completed as follows.

CategoryExample 1Example 2
Metric collection interval1 minute5 minutes
Alert evaluation cycle (fixed)1 minute1 minute
Alert Evaluation Scope1 minute10 minutes
Alarm evaluation count5 times3 times
Alarm violation countRound 43 times
Alert evaluation interval (seconds)5 minutes (300 seconds)30 minutes (1,800 seconds)
StatisticsaverageTotal
conditional operator>=<
threshold8020
ConditionIf the average CPU Usage >= 80% for 4 occurrences over 5 minutes, change the alert status to Alert.Change to < 20% 이면, 경보 상태를 Alert if the average CPU usage occurs three times within 30 minutes.
Table. Alarm Evaluation Example - Conditional Operators, Thresholds, Statistics Added

Alert Notification

If the alarm evaluation criteria are met, change the alarm status to Alert and send a notification to the recipients configured in the alarm policy.

Reference
  • Only users with a login history (users who have registered an email or mobile phone number) can be added as alert recipients.
  • The notification reception method (E-mail or SMS) can be set on the Notification Settings page by selecting the notification target as Service > Alert.
  • You can add up to 100 notification recipients.
information
  • Users without login history cannot be designated as notification recipients.
  • On the Notification Settings page, if you select the notification target as Service > Alarm but do not configure a notification delivery method, you will not receive notifications.

Method for handling missing data during alarm evaluation

Some resources may be unable to send metric data to ServiceWatch under certain conditions. For example, if a resource is inactive or does not exist, it will not be sent to ServiceWatch. If metrics are not collected for a certain period, the alert evaluation will change the alert status to Insufficient data.

ServiceWatch provides a way to handle missing data during alert evaluation. The methods for handling missing data are as follows:

  • Ignore: maintains the current alarm state. (default)
  • Missing: Treat missing data points as missing. If all data points within the evaluation range are missing, the alert status changes to Insufficient data.
  • Breaching: Process missing data points as satisfying the threshold condition.
  • Not breaching: Treat missing data points as normal when they do not satisfy the threshold condition.
Reference
  • For alert policies created before the December 2025 release, missing data is handled with the default Ignore, and starting with the December 2025 release, you can directly select how to handle missing data.
  • In the alert policy, the method for handling missing data can be modified, and from the time of modification onward, missing data will be processed using the updated method.

Alert History

The change history of the alarm status is recorded in the alarm history. The alarm history can be viewed for 30 days.

1.3 - Log

Log

By using ServiceWatch logs, you can monitor, store, and access log files collected from the resources of the service that provides the logs.

Log Group 1Log Group 1Log Group 1Log Group 2Log Group 2Log Group 2
Log Stream1Log Stream2Log Stream3Log Stream ALog Stream Blog stream
Log EventLog EventLog EventLog EventLog EventLog Event
Log EventLog EventLog EventLog EventLog Event
Table. Log Configuration - Log Group, Log Stream, Log Event
Reference

The following is an example of log configuration.

  • 📂 Log Group: “WebApp-Logs”
    • 📄 Log Stream 1: “Server-1”
      • 📝 Log Event 1: “[2025-03-20 10:00:01] User logged in”
      • 📝 Log Event 2: “[2025-03-20 10:05:34] Database connection error”

Log Group

Log groups are containers for log streams that share the same retention policy settings. Each log stream must belong to a single log group. For example, if there are separate log streams for the logs of each cluster in Kubernetes Engine, you can group the log streams into a single log group called /scp/ske/{cluster name}.

Log Retention Policy

The log retention policy allows you to set the period for retaining log events in ServiceWatch. Log events whose retention period has expired are automatically deleted. Log The retention period assigned to the group applies to the log streams and log events belonging to the log group.

The retention period can be selected from the following options and is set in days.

Retention period
  • No expiration
  • 1 day
  • 3 days
  • 5 days
  • 1 week (7 days)
  • 2 weeks (14 days)
  • 1 month (30 days)
  • 2 months (60 days)
  • 3 months (90 days)
  • 4 months (120 days)
  • 5 months (150 days)
  • 6 months (180 days)
  • 1 year (365 days)
  • 13 months (400 days)
  • 18 months (545 days)
  • 2 years (731 days)
  • 3 years (1096 days)
  • 5 years (1827 days)
  • 6 years (2192 days)
  • 7 years (2557 days)
  • 8 years (2922 days)
  • 9 years (3288 days)
  • 10 years (3653 days)
Table. Log Group Retention Policy Period

Log stream

A log stream is a collection of log events ordered by the sequence in which they occurred from the same source. For example, all log events generated by a particular Kubernetes Engine cluster can form a single log stream.

Log Event

Log events are individual records that capture logs generated by a resource. A log event record includes two attributes: a timestamp of when the event occurred and a log message. Each message must be encoded in UTF-8.

log pattern

You can create log patterns to filter log data that matches the pattern. Log patterns define the words or patterns to search for in the log data collected by ServiceWatch, allow you to view the status of log occurrences as graphs, and serve as metrics for creating alert policies.

Log patterns are not applied retroactively to data. They are applied to log events collected after the log pattern is created.

Log pattern namespace

A namespace is a logical separation used to distinguish and group metrics. In ServiceWatch, it is divided into namespaces associated with services, namespaces for custom metrics, and namespaces for log patterns.

  • Namespace associated with services such as Virtual Server
  • A namespace consisting of custom metrics, i.e., the namespace of metrics collected through the custom metrics API or ServiceWatch Agent.
  • Namespace of the metric generated by the log pattern

When creating metrics for a log pattern, you can either create a new namespace for the log pattern or select from existing log pattern namespaces.

Metric name

The monitored log information is the name of the metric generated by ServiceWatch. You must configure it so that the metric name does not duplicate within the namespace where the metric will exist.

Metric Value

It is the numeric value posted to the metric each time a log matching the pattern is found. For example, when counting occurrences of a specific word (e.g., Error), this value becomes 1 for each occurrence. When calculating transmitted bytes, it can be incremented by the actual number of bytes found in the log event.

default value

This is the value recorded in the log pattern for periods during log collection when no matching logs can be found. Setting the default to 0 prevents the metric from becoming irregular due to periods with no matching data.

When setting a dimension on a metric created from a log pattern, you cannot set a default value for that metric.

dimension

Dimensions are key-value pairs that further define a metric. You can add dimensions to metrics generated from log patterns. Since dimensions are part of a metric’s unique identifier, each time a unique name/value pair is extracted from logs, a new variant of that metric is created.

When you choose the log pattern format as either a whitespace-delimited pattern or a JSON format pattern, you can set the dimension, and it can be configured using one of the parameters defined in the pattern. You can assign up to three dimensions to an indicator. If a default value is set, you cannot configure dimensions. To set dimensions, you must disable the use of the default value.

Pattern format

This explains how ServiceWatch interprets data from each log event. The pattern format can be selected from three options as shown below.

  • String Pattern: log containing a specific string
  • Space-separated pattern: timestamps, IP addresses, strings, and other logs separated by spaces
  • JSON format pattern: log containing specific JSON fields

Available regular expression syntax

When using regular expressions to search and filter log data, you must enclose the expression with %.

Patterns that contain regular expressions can only include the following.

  • Alphanumeric - An alphanumeric character is a character that corresponds to a letter (A~Z or a~z) or a digit (0~9).
    • It can be used with A-Z, a-z, 0-9.
  • The supported symbol characters are as follows.
    • :, _, #, =, @, /, ;, ,, -
    • For example, %servicewatch!% cannot be used because ! is not supported.
  • The supported operators are as follows.
    • It includes ^, $, ?, [, ], {, }, |, \, *, +, ..
    • (, ) The operator is not supported.
operatorHow to use
^Fix the start position of the string to the matching item. For example, %^[ab]cd% matches acd and bcd, but does not match bcd.
$Fix the end position of the string to the matching item. For example, %abc$% matches xyzabc and xyabc, but does not match abcd.
?? matches when the preceding character appears 0 or 1 times. For example, %abc?d% matches both abcd and abd, while abc and abccd do not match.
[]Matches a list of characters or a range of characters enclosed in square brackets. For example, %[abc]% matches a, b, c, and %[a-z]% matches all lowercase letters from a to z, and %[abcx-z]% matches a, b, c, x, y, z.
{m, n}It matches when the preceding character is repeated m~n times. For example, %a{3,5}% matches only aaa, aaaa and aaaaa, and does not match a or aa.
\By using an escape character, you can treat this character literally instead of as a special operator.
*Matches the preceding character zero or more times. For example, %12*3% matches 13, 123, 122223.
+Matches the preceding character one or more times. For example, %12+3% can match 123, 1223, 12223, but does not match 13.
.Matches any character. For example, %.ab% matches cab, dab, bab, 8ab, #ab, ab (including spaces), and ab which end with a three-character string.
\d, \DMatches digits and non-digit characters. For example, %\d% is equivalent to %[0-9]%, and %\D% matches all characters except digits, like %[^0-9]%.
\s, \SMatches whitespace characters and non-whitespace characters. Whitespace characters include tab (\t), space ( ), and line break (\n) characters.
\w, \WMatches alphanumeric and non-alphanumeric characters. For example, %\w% is equivalent to %[a-zA-Z_0-9]%, and %\W% is equivalent to %[^a-zA-Z_0-9]%.
\xhhMatches the ASCII mapping of a two‑digit hexadecimal character. \x is an escape sequence indicating that the following character is the hexadecimal value in ASCII. hh specifies a two‑digit hexadecimal (0–9 and A–F) that refers to a character in the ASCII table.
Table. Regular expression syntax operators available for log patterns
Reference
To represent an IP address such as 123.123.123.1 with a regular expression, use %123\.123\.123\.1%.

string pattern

String pattern using regular expressions

You can search for matching patterns in log events using a regex string pattern wrapped with %(percentage) at the beginning and end. Below is an example pattern that retrieves all log events containing the ERROR keyword. Please refer to Available regex syntax.

%ERROR%

The above pattern matches log event messages like the ones below.

  • [2026-02-13 14:22:01] ERROR 500 POST /api/v1/checkout (192.168.1.10) - NullPointerException at com.app.controller.CheckoutController.java:55
  • [ERROR] Configuration file not found: /etc/app/config.yaml
String pattern in unstructured log events

It is a string pattern for searching strings in log events that are not in formats such as JSON. Below is an example of a log event message, and you can view log events that match various string pattern classifications.

ERROR CODE 400 BAD REQUEST
ERROR CODE 401 UNAUTHORIZED REQUEST
ERROR CODE 419 MISSING ARGUMENTS
ERROR CODE 420 INVALID ARGUMENTS
CategoryPatternMatching log event message
single stringERROR CODEERRORlog event containing
  • ERROR CODE 400 BAD REQUEST
  • ERROR CODE 401 UNAUTHORIZED REQUEST
  • ERROR CODE 419 MISSING ARGUMENTS
  • ERROR CODE 420 INVALID ARGUMENTS
Multiple strings (AND condition)ERROR REQUESTlog events containing the strings ERROR and REQUEST
  • ERROR CODE 400 BAD REQUEST
  • ERROR CODE 401 UNAUTHORIZED REQUEST
Multiple strings (Or condition)?ERROR ?400ERRORor 400log event containing the string
  • ERROR CODE 400 BAD REQUEST
  • ERROR CODE 401 UNAUTHORIZED REQUEST
  • ERROR CODE 419 MISSING ARGUMENTS
  • ERROR CODE 420 INVALID ARGUMENTS
Exact match string“BAD REQUEST”“BAD REQUEST”log event containing the exact phrase
  • ERROR CODE 400 BAD REQUEST
Exclude specific stringERROR -400A pattern that includes some terms and excludes others. Enter - before the string you want to exclude. The following is a log event that includes the string ERROR and excludes the string 400:
  • ERROR CODE 401 UNAUTHORIZED REQUEST
  • ERROR CODE 419 MISSING ARGUMENTS
  • ERROR CODE 420 INVALID ARGUMENTS
Table. String patterns in unstructured log events

Space-separated pattern

Generate a pattern to search for matching strings in space-separated log events.

Whitespace-separated pattern example (1)

The following is an example of log events separated by spaces.

2023-10-27T10:00:01Z [INFO] 1234 login success 192.168.1.1

The above log event is a space‑separated log event that includes timestamp, logLevel, user_id, action, status, ip. Characters between brackets ([]) and double quotes ("") are considered a single field.

To create a pattern that searches for matching strings in space-separated log events, enclose the pattern in brackets ([]) and specify name-separated fields with commas (,). The following pattern parses six fields.

A pattern like [timestamp, logLevel, user_id, action, status = success, ip] can be used to find log events where the fifth field, status, is success.

Whitespace-separated pattern example (2)
abc xxx.log james 2023-10-27T10:00:01Z POST 400 1024
abc xxx.log name 2023-10-27T10:00:02Z POST 410 512

The above log event is a space‑separated log event that includes host, logName, user, timestamp, request, statusCode, and size.

A pattern like [host, logName, user, timestamp, request, statusCode=4*, size] can find log events where the sixth field, statusCode, starts with 4.

If you do not know the exact number of fields in a space-separated log event, you can use an ellipsis (). A pattern such as […, statusCode=4*, size] represents the first five fields using an ellipsis.

AND(&&) operator and OR(||) operator can be used to create composite expressions. […, statusCode=400 || statusCode=410, size] can find log events where the sixth field, statusCode, is 400 or 410.

You can use regular expressions to provide conditions in a pattern. [host, logName, user, timestamp, request, statusCode=%4[0-9]{2}%, size] can find log events where the sixth field, statusCode, is a number that starts with 4.

JSON format pattern

You can create a pattern to search for matching strings or numeric values in JSON log events. Patterns are enclosed in curly braces ({}).

String-based JSON format pattern
  • Use $. to represent JSON fields.
  • The operator can use = or !=.
  • The string to compare with the field can be enclosed in double quotes (""). Strings containing characters other than alphanumerics and the underscore must be enclosed in double quotes. Use an asterisk (*) as a wildcard to match text.
{ $.resourceType = "trail" }
{ $.resourceType = "%trail%" }
{ $.arrayKey[0] = "value" }
  • Use $. to represent JSON fields.
  • You can use numeric operators.
    • greater than(>), less than(<), equal to(=), not equal to(!=), greater than or equal to(>=), less than or equal to(<=)
  • You can include addition(+) or subtraction(-) symbols. An asterisk(*) can be used as a wildcard.
{ $.errorCode = 400} 
{ $.errorCode >= 400} 
{ $.errorCode != 500 }
{ $.sourceIPAddress != 123.123.* }

Export Log Group

You can export log data from a log group to Object Storage for log retention and analysis. You can also export log groups for log data that resides in the same account.

To start exporting a log group, you must create an Object Storage bucket to store the log data.

Exporting a log group can take a long time depending on the amount of logs. When exporting a log group, you can reduce the export duration by specifying particular streams within the log group or by defining a time range.

Log group export can only be executed one at a time per account. To start another log group export, the ongoing export task must be completed.

You can delete a log group’s export history after the export succeeds or after the export cancellation is completed. Canceling a log group export does not delete the saved file exported from the log group. To delete the saved file exported from the log group, delete the stored file directly in Object Storage.

Log group export statusdescription
SuccessThe log group export operation completed successfully.
PendingThe log group export task is pending.
In progressThe log group export operation is in progress.
FailedThe log group export operation failed.
CancelingCancelling the log group export task. If the cancellation request fails, it will be set to a Failed state.
CanceledThe log group export task has been cancelled.
Table. Log Group Export Status

1.4 - Event

An event represents a change in the environment in the Samsung Cloud Platform service.

ServiceWatch receives events generated by most Samsung Cloud Platform services. Events from each service can be viewed and processed in the ServiceWatch of the same Account.

Refer to the ServiceWatch Event Reference for the list of services that send events to ServiceWatch and the events they send.

Each service sends events to ServiceWatch based on Best Effort delivery. Best Effort delivery means that the service attempts to send all events to ServiceWatch, but occasionally some events may not be delivered.

When a valid event is delivered to ServiceWatch, ServiceWatch compares the event with the rules and then sends a notification to the alert recipients configured in the event rule.

Event Rules

You can specify the actions that ServiceWatch performs on events delivered from each service to ServiceWatch. To do this, create an event rule. An event rule defines which events are sent to which targets.

Event rules evaluate an event when it arrives. Each event rule checks whether the event matches the rule’s pattern. If the event matches, ServiceWatch processes the event.

Based on the event data criteria (called an event pattern), you can generate matching rules for incoming events. When an event matches the criteria defined in the event pattern, the event is delivered to the target specified in the rule.

  • Event rules can, by default, designate the recipients who will receive notifications when an event occurs.
  • The event rules are planned to be expanded to include multiple Samsung Cloud Platform services as recipients when events occur. (Planned for 2026)

To create an event rule, refer to How-to Guides > Create Event Rule.

Event source

In ServiceWatch, the event source can be selected as a Samsung Cloud Platform service name. You can select the service name of the event you want to receive as the event source.

Service Categoryservice
ComputeVirtual Server
ComputeGPU Server
ComputeBare Metal Server
ComputeMulti-node GPU Cluster
ComputeCloud Functions
StorageBlock Storage(BM)
StorageFile Storage
StorageObject Storage
StorageArchive Storage
StorageBackup
ContainerKubernetes Engine
ContainerContainer Registry
NetworkingVPC
NetworkingSecurity Group
NetworkingLoad Balancer
NetworkingDNS
NetworkingVPN
NetworkingFirewall
NetworkingDirect Connect
NetworkingCloud LAN-Campus
NetworkingCloud LAN-Datacenter
NetworkingCloud WAN
NetworkingGlobal CDN
NetworkingGSLB
DatabaseEPAS(DBaaS)
DatabasePostreSQL(DBaaS)
DatabaseMariaDB(DBaaS)
DatabaseMySQL(DBaaS)
DatabaseMicrosoft SQL Server(DBaaS)
DatabaseCacheStore(DBaaS)
Data AnalyticsEvent Streams
Data AnalyticsSearch Engine
Data AnalyticsVertica(DBaaS)
Data AnalyticsData Flow
Data AnalyticsData Ops
Data AnalyticsQuick Query
Application ServiceAPI Gateway
SecurityKey Management Service
SecurityConfig Inspection
SecurityCertificate Manager
SecuritySecret Vault
ManagementCloud Control
ManagementIdentity and Access Management(IAM)
ManagementID Center
ManagementLogging&Audit
ManagementOrganization
ManagementResource Groups
ManagementServiceWatch
ManagementSupport Center
AI-MLCloudML
AI-MLAI&MLOps Platform
Table. ServiceWatch event source

Event Type

The Samsung Cloud Platform service has its own resource types. Event types are classified the same as resource types, and you select the type of events from the event source to use in an event rule.

The following are the event types of a Virtual Server.

Service CategoryServiceSubserviceEvent type
ComputeVirtual ServerVirtual ServerServer
ComputeVirtual ServerImageImage
ComputeVirtual ServerKeypairKeypair
ComputeVitual ServerServer GroupServer Group
ComputeVirtual ServerLaunch ConfigurationLaunch Configuration
ComputeVirtual ServerAuto-Scaling GroupAuto-Scaling Group
ComputeVirtual ServerBlock StorageVolume
ComputeVirtual ServerBlock StorageSnapshot
Table. ServiceWatch - Virtual Server Event Types

For other event types available in ServiceWatch, refer to ServiceWatch Event.

Event

Events can select either all events generated from an event source’s event type or specific events.

The following are some events of the Server event type for Virtual Server.

Service CategoryServiceSubserviceEvent typeEvent
ComputeVirtual ServerVirtual ServerServerCompute Virtual Server Create Start
ComputeVirtual ServerVirtual ServerServerCompute Virtual Server Create End
ComputeVirtual ServerVirtual ServerServerCompute Virtual Server Create Error
ComputeVirtual ServerVirtual ServerServerCompute Virtual Server Delete Start
ComputeVirtual ServerVirtual ServerServerCompute Virtual Server Delete End
ComputeVirtual ServerVirtual ServerServerCompute Virtual Server Delete Error
ComputeVirtual ServerVirtual ServerServerCompute Virtual Server Lock End
ComputeVirtual ServerVirtual ServerServerCompute Virtual Server Unlock End
ComputeVirtual ServerVirtual ServerServerCompute Virtual Server Stop Start
ComputeVirtual ServerVirtual ServerServerCompute Virtual Server Stop Success
ComputeVirtual ServerVirtual ServerServerCompute Virtual Server Start Start
ComputeVirtual ServerVirtual ServerServerCompute Virtual Server Start Success
ComputeVirtual ServerVirtual ServerServerCompute Virtual Server Reboot Start
ComputeVirtual ServerVirtual ServerServerCompute Virtual Server Reboot End
ComputeVirtual ServerVirtual ServerServerCompute Virtual Server Reboot Error
ComputeVirtual ServerVirtual ServerServerCompute Virtual Server Power On Start
ComputeVirtual ServerVirtual ServerServerCompute Virtual Server Power On End
ComputeVirtual ServerVirtual ServerServerCompute Virtual Server Power On Error
Table. Some events of ServiceWatch - Virtual Server Server

For other events available in ServiceWatch, refer to ServiceWatch Event.

Applied Resources

Set an event pattern for the selected event on all resources or a specific resource.

event pattern

When you select the event source, event type, event, and target resource, the event pattern configuration for the event rule is completed.

The following is an example of an event pattern set in ServiceWatch’s event rule.

Color mode
{
	"source": [ // namespace
		"Virtual Server"
	],
	"detail-type": [ // event type
		Server
	],
	"detail": {
		"event": [ // individual event
			Compute Virtual Server Create End
		]
	},
	"resources": [ // individual resources
		"srn:{offerring}::{account_id}:{region}::virtualserver:server/{resource_id}"
	]
}
{
	"source": [ // namespace
		"Virtual Server"
	],
	"detail-type": [ // event type
		Server
	],
	"detail": {
		"event": [ // individual event
			Compute Virtual Server Create End
		]
	},
	"resources": [ // individual resources
		"srn:{offerring}::{account_id}:{region}::virtualserver:server/{resource_id}"
	]
}
code block. ServiceWatch - Virtual Server event pattern example

To create an event rule, refer to How-to Guides > Create Event Rule.

Event Notification

If the event matches the pattern, a notification is sent to the alert recipients configured in the event rule.

Reference
  • It is possible to send notifications to users with a login history (users who have registered an email or mobile phone number).
  • You can add up to 100 notification recipients.
  • The notification reception method (E-mail or SMS) can be changed on the Notification Settings page after selecting the notification target as Service > ServiceWatch.
information
  • Users without login history cannot be designated as notification recipients.
  • If you select the notification target as Service > ServiceWatch on the Notification Settings page but do not configure a notification delivery method, you will not receive notifications.

1.5 - ServiceWatch integration service

You can view services integrated with ServiceWatch.

Metrics and Log Monitoring

Below you can see the service that integrates ServiceWatch with metric and log monitoring.

Reference
For information on basic monitoring and detailed monitoring, see ServiceWatch 기본 모니터링과 세부 모니터링.
Service CategoryServicenamespaceIndicator
Basic Monitoring
indicator
detailed monitoring
Log monitoringGuide
ComputeVirtual ServerVirtual Server-
ComputeGPU ServerVirtual Server-
ComputeBlock StorageTBDScheduled for July 2026--
ComputeBare Metal Server----
ComputeMulti-node GPU Cluster----
ComputeCloud FuctionsCloud Functions-
  • Cloud Functions are automatically linked to ServiceWatch for log collection upon creation. No additional configuration is required.
StorageBlock Storage(BM)TBDScheduled for July 2026--
StorageFile StorageFile Storage-
StorageObject StorageObject Storage--
StorageArchive StorageArchive Storage--
ContainerKubernetes EngineKubernetes Engine-
ContainerContainer RegistryContainer Registry--
NetworkingVPC - Internet GatewayInternet Gateway--
NetworkingLoad BalancerLoad Balancer--
NetworkingDNSDNS--
NetworkingVPNVPN--
NetworkingGlobal CDNGlobal CDN--
NetworkingDirect ConnectDirect Connect--
NetworkingCloud WANTBDScheduled for September 2026--
DatabaseEPAS(DBaaS)TBDScheduled for July 2026-Scheduled for July 2026
  • For new resources, monitoring via ServiceWatch is available starting July 2026.
  • Resources created before July 2026 are scheduled to be transitioned by September 2026. After September 2026, monitoring via ServiceWatch will be possible. For more details, see EPAS(DBaaS) > How-to guides.
DatabasePostgreSQL(DBaaS)TBDScheduled for July 2026-Scheduled for July 2026
  • For new resources, monitoring via ServiceWatch will be available starting July 2026.
  • Resources created before July 2026 are scheduled to be transitioned by September 2026. Monitoring via ServiceWatch will be available after September 2026. For more details, see PostgreSQL(DBaaS) > How-to guides.
DatabaseMariaDB(DBaaS)MariaDB-
  • For new resources, monitoring via ServiceWatch is available starting March 2026
  • Resources created before March 2026 are scheduled to be transitioned by July 2026. After July 2026, monitoring via ServiceWatch will be available. For details, see MariaDB(DBaaS) > How-to guides.
DatabaseMySQL(DBaaS)MySQL-
  • For new resources, monitoring via ServiceWatch is available starting March 2026
  • Resources created before March 2026 are scheduled to be transitioned by July 2026. After July 2026, monitoring via ServiceWatch will be available. For details, see MySQL(DBaaS) > How-to guides.
DatabaseMicrosoft SQL Server(DBaaS)TBDScheduled for July 2026-Scheduled for July 2026
  • For new resources, monitoring via ServiceWatch will be available starting July 2026
  • Resources created before July 2026 are scheduled to be transitioned by September 2026. Monitoring via ServiceWatch will be available after September 2026. For more details, see Microsoft SQL Server(DBaaS) > How-to guides.
DatabaseCachestore(DBaaS)TBDScheduled for July 2026-Scheduled for July 2026
  • For new resources, monitoring via ServiceWatch will be available starting July 2026.
  • Resources created before July 2026 are scheduled to be transitioned by September 2026. Monitoring via ServiceWatch will be available after September 2026. For more details, see Cachestore(DBaaS) > How-to guides.
DatabaseScalable DB(DBaaS)Scalable DB-
Data AnalyticsEvent StreamsEvent Streams-
  • For new resources, monitoring via ServiceWatch is available starting March 2026
  • Resources created before March 2026 are scheduled to be transitioned by July 2026. After July 2026, monitoring via ServiceWatch will be available. For more details, see Event Streams > How-to guides.
Data AnalyticsSearch EngineTBDScheduled for July 2026-Scheduled for July 2026
  • For new resources, monitoring via ServiceWatch will be available starting July 2026.
  • Resources created before July 2026 are scheduled to be transitioned by September 2026. Monitoring via ServiceWatch will be possible after September 2026. For more details, see Search Engine > How-to guides.
Data AnalyticsVertica(DBaas)TBDScheduled for July 2026-Scheduled for July 2026
  • For new resources, monitoring via ServiceWatch will be available starting July 2026.
  • Resources created before July 2026 are scheduled to be transitioned by September 2026. Monitoring via ServiceWatch will be available after September 2026. For more details, see Vertica(DBaas) > How-to guides.
Data AnalyticsData FlowData Flow-
Data AnalyticsData OpsData Ops-
Data AnalyticsQuick QueryQuick Query-
Data AnalyticsCloud HadoopCloud Hadoop-
Application ServiceAPI GatewayAPI Gateway-
Application ServiceQueue ServiceQueue Service--
ManagementLoggiing&AuditLogging&Audit--
AI/MLAIOSAIOS--
Table. ServiceWatch metrics and log integration services and guide

event

Below you can see the service that integrates ServiceWatch with events.

Reference
For information related to event rules, see the Event. Refer to the list of Samsung Cloud Platform services that generate events and the events at ServiceWatch Event.
Service CategoryServiceSubserviceEvent sourceResource type (event type)
ComputeVirtual ServerVirtual ServerVirtual ServerServer
ComputeVirtual ServerImageVirtual ServerImage
ComputeVirtual ServerKeypairVirtual ServerKeypair
ComputeVitual ServerServer GroupVirtual ServerServer Group
ComputeVirtual ServerLaunch ConfigurationVirtual ServerLaunch Configuration
ComputeVirtual ServerAuto-Scaling GroupVirtual ServerAuto-Scaling Group
ComputeVirtual ServerBlock StorageVirtual ServerVolume
ComputeVirtual ServerBlock StorageVirtual ServerSnapshot
ComputeGPU ServerGPU ServerGPU ServerServer
ComputeGPU ServerGPU ServerGPU ServerImage
ComputeBare Metal ServerBare Metal ServerBare Metal ServerBare Metal Server
ComputeMulti-node GPU ClusterGPU NodeMulti-node GPU ClusterGPU Node
ComputeMulti-node GPU ClusterCluster FabricMulti-node GPU ClusterCluster Fabric
ComputeCloud FunctionsFunctionCloud FunctionsCloud Functions
StorageBlock Storage(BM)Block Storage(BM)Block Storage(BM)Volume
StorageBlock Storage(BM)Volume Group(BM)Block Storage(BM)Volume Group
StorageFile StorageFile StorageFile StorageVolume
StorageObject StorageObject StorageObject StorageBucket
StorageArchive StorageArchive StorageArchive StorageBucket
StorageBackupBackupBackupBackup
ContainerKubernetes EngineClusterKubernetes EngineCluster
ContainerKubernetes EngineNodeKubernetes EngineNodepool
ContainerContainer RegistryRegistryContainer RegistryContainer Registry
ContainerContainer RegistryRepositoryContainer RegistryRepository
NetworkingVPCVPCVPCVPC
NetworkingVPCSubnetVPCSubnet
NetworkingVPCPortVPCPort
NetworkingVPCInternet GatewayVPCInternet Gateway
NetworkingVPCNAT GatewayVPCNAT Gateway
NetworkingVPCPublic IPVPCPublic IP
NetworkingVPCPrivate NATVPCPrivate NAT
NetworkingVPCVPC EndpointVPCVPC Endpoint
NetworkingVPCVPC PeeringVPCVPC Peering
NetworkingVPCPrivate Link ServiceVPCPrivate Link Service
NetworkingVPCPrivate Link EndpointVPCPrivate Link Endpoint
NetworkingVPCTransit GatewayVPCTransit Gateway
NetworkingSecurity GroupSecurity GroupSecurity GroupSecurity Group
NetworkingLoad BalancerLoad BalancerLoad BalancerLoad Balancer
NetworkingLoad BalancerLoad BalancerLoad BalancerLB Listener
NetworkingLoad BalancerLB server groupLoad BalancerLB Server Group
NetworkingLoad BalancerLB health checkLoad BalancerLB Health Check
NetworkingDNSPrivate DNSPrivate DNSPrivate DNS
NetworkingDNSHosted ZoneHosted ZoneHosted Zone
NetworkingDNSPublic Domain NamePublic Domain NamePublic Domain Name
NetworkingVPNVPNVPNVPN Gateway
NetworkingVPNVPN TunnelVPNVPN Tunnel
NetworkingFirewallFirewallFirewallFirewall
NetworkingDirect ConnectDirect ConnectDirect ConnectDirect Connect
NetworkingCloud LAN-CampusCampus NetworkCloud LAN - Campus (Network)Cloud LAN - Campus (Network)
NetworkingCloud LAN-DatacenterCloud LAN NetworkCloud LAN NetworkCloud LAN Network
NetworkingCloud LAN-DatacentervDeviceCloud LAN NetworkvDevice
NetworkingCloud LAN-DatacenterInterfaceCloud LAN NetworkInterface
NetworkingCloud LAN-DatacentervCableCloud LAN NetworkvCable
NetworkingCloud WANCloud WAN NetworkCloud WANNetwork(WAN)
NetworkingCloud WANSegmentCloud WANSegment
NetworkingCloud WANSegmentCloud WANSegment Location
NetworkingCloud WANSegmentCloud WANSegment Sharing
NetworkingCloud WANAttachmentCloud WANAttachment
NetworkingGlobal CDNGlobal CDNGlobal CDNGlobal CDN
NetworkingGSLBGSLBGSLBGSLB
DatabaseEPAS(DBaaS)EPAS(DBaaS)EPASEPAS
DatabasePostreSQL(DBaaS)PostreSQL(DBaaS)PostreSQLPostreSQL
DatabaseMariaDB(DBaaS)MariaDB(DBaaS)MariaDBMariaDB
DatabaseMySQL(DBaaS)MySQL(DBaaS)MySQLMySQL
DatabaseMicrosoft SQL Server(DBaaS)Microsoft SQL Server(DBaaS)Microsoft SQL ServerMicrosoft SQL Server
DatabaseCacheStore(DBaaS)CacheStore(DBaaS)CacheStoreCacheStore
DatabaseScalable DB(DBaaS)Scalable DB(DBaaS)Scalable DBScalable DB
Data AnalyticsEvent StreamsEvent StreamsEvent StreamsEvent Streams
Data AnalyticsSearch EngineSearch EngineSearch EngineSearch Engine
Data AnalyticsVertica(DBaaS)Vertica(DBaaS)VerticaVertica
Data AnalyticsData FlowData FlowData FlowData Flow
Data AnalyticsData FlowData Flow ServicesData FlowData Flow Service
Data AnalyticsData OpsData OpsData OpsData Ops
Data AnalyticsData OpsData Ops ServicesData OpsData Ops Service
Data AnalyticsQuick QueryQuick QueryQuick QueryQuick Query
Application ServiceAPI GatewayAPI GatewayAPI GatewayAPI Gateway
Application ServiceQueue ServiceQueueQueueQueue
SecurityKey Management ServiceKey Management ServiceKey Management ServiceKey
SecurityConfig InspectionConfig InspectionConfig InspectionConfig Inspection
SecurityCertificate ManagerCertificate ManagerCertificate ManagerCertificate
SecuritySecrets ManagerSecrets ManagerSecrets ManagerSecret
SecuritySecret VaultSecret VaultSecret VaultSecret
ManagementCloud ControlCloud ControlCloud ControlLanding zone
ManagementIdentity and Access Management(IAM)User groupIdentity and Access ManagementGroup
ManagementIdentity and Access Management(IAM)UserIdentity and Access ManagementUser
ManagementIdentity and Access Management(IAM)policyIdentity and Access Managementpolicy
ManagementIdentity and Access Management(IAM)roleIdentity and Access Managementrole
ManagementIdentity and Access Management(IAM)Credential ProviderIdentity and Access ManagementCredential Provider
ManagementIdentity and Access Management(IAM)My Info.Identity and Access ManagementAccess Key
ManagementID CenterID CenterIdentity CenterID Center
ManagementID CenterPermission setIdentity CenterPermission set
ManagementLogging&AuditTrailLogging&AuditTrail
ManagementOrganizationOrganizational structureOrganizationorganization
ManagementOrganizationOrganizational structureOrganizationOrganization account
ManagementOrganizationOrganizational StructureOrganizationOrganization invitation
ManagementOrganizationOrganizational StructureOrganizationorganizational unit
ManagementOrganizationControl PolicyOrganizationControl Policy
ManagementOrganizationOrganization SettingsOrganizationDelegation Policy
ManagementResource GroupsResource GroupsResource GroupsResource Group
ManagementServiceWatchDashboardServiceWatchDashboard
ManagementServiceWatchAlertServiceWatchAlert
ManagementServiceWatchlogServiceWatchLog group
ManagementServiceWatchEvent RulesServiceWatchEvent Rules
ManagementSupport CenterService requestSupportService request
ManagementSupport CenterContactSupportContact
AI-MLCloudMLCloudMLCloud MLCloud ML
AI-MLAI&MLOps PlatformAI&MLOps PlatformAI&MLOps PlatformAI&MLOps Platform
Table. ServiceWatch event service

1.6 - Custom Metrics and Logs

ServiceWatch can collect custom metrics defined by the user and can gather log files from resources created by the user.

There are two ways to collect custom metrics and logs.

The first method is to install the ServiceWatch Agent directly on the resource, configure the resources to be collected, and collect them.
The second option is to collect custom metrics and logs using the OpenAPI/CLI offered by ServiceWatch.

Reference
Collecting custom metrics/logs via the ServiceWatch Agent is currently available only on Samsung Cloud Platform For Enterprise. It will be offered in other offerings in the future.
Caution

The ServiceWatch metric API incurs costs for calls. Collecting metrics via the ServiceWatch Agent also operates on an OpenAPI basis, so metric API calls incur costs.
Caution is required to avoid excessive API calls when collecting metrics and logs. The billable metric APIs are listed below.

APIdescription
ListMetricDataRetrieve metric data list.
  • Since a single API call can request multiple metrics, charges are applied per 1,000 metric requests
DownloadMetricDataImageMetric data widget image download.
  • Since a single API call can request multiple metrics, a fee is charged per 1,000 metric requests
ListMetricInfosRetrieve indicator data.
  • This API incurs a charge per 1,000 calls
CreateCustomMetricMetasCreate custom metric metadata
  • This API is billed per 1,000 calls
CreateCustomMetricsCreate (send) custom metric data
  • This API incurs a charge per 1,000 calls
ShowDashboardDashboard view
  • This API is charged per 1,000 calls
ListDashboardsDashboard list retrieval
  • This API incurs a charge per 1,000 calls
CreateDashboardCreate Dashboard
  • This API incurs a charge per 1,000 calls
SetDashboardEdit Dashboard
  • This API is charged per 1,000 calls
DeleteBulkDashboardsDelete Dashboard
  • This API incurs a charge per 1,000 calls
Table. Indicator API Billing Information

Since logs incur charges based on the amount of data collected, there is no additional charge for API calls.

※ For detailed pricing information, refer to the ServiceWatch pricing details on the Samsung Cloud Platform Service Portal.

ServiceWatch Agent

You can install the ServiceWatch Agent on user resources such as Virtual Server, GPU Server, Bare Metal Server, etc., to collect custom metrics and logs.

ServiceWatch Agent Constraints

ServiceWatch Agent network environment

The ServiceWatch Agent is designed to collect data using OpenAPI by default, so installing and using it on server resources requires external communication over the Internet. Please create an Internet Gateway in the VPC where the resources reside and configure a NAT IP on the server resources to enable communication with the outside.

ServiceWatch Agent Supported OS Image

The OS images available for the ServiceWatch Agent are as follows.

OS Image versionEOS Date
Alma Linux 8.102029-05-31
Alma Linux 9.62025-11-17
Oracle Linux 8.102029-07-31
Oracle Linux 9.62025-11-25
RHEL 8.102029-05-31
RHEL 9.42026-04-30
RHEL 9.62027-05-31
Rocky Linux 8.102029-05-31
Rocky Linux 9.62025-11-30
Ubuntu 22.042027-06-30
Ubuntu 24.042029-06-30
Windows 20192029-01-09
Windows 20222031-10-14
Table. OS images supported by ServiceWatch Agent

Provides the same as the OS Image provided for Virtual Server. Refer to Virtual Server > OS Image 제공 버전.

Quick Guide for Using ServiceWatch Agent

Below, we present a Quick guide for collecting OS metrics and logs of a Virtual Server in a Linux environment.

Installing and Configuring Node Exporter

  1. Refer to Node Exporter installation and install Node Exporter on the server to collect custom metrics.
    • When you install Node Exporter, you can collect OS metrics through Node Exporter in addition to the metrics provided by ServiceWatch’s default monitoring.
  2. Refer to ServiceWatch Agent 설정, then download the ServiceWatch_Agent archive, configure the ServiceWatch Manager, and run it.
    • By referring to the examples/os-metric-min-examples folder in the archive, you can run the ServiceWatch Agent by configuring at least two metrics.
Caution

Metric collection through the ServiceWatch Agent is classified as custom metrics and, unlike the default metrics collected from each service, incurs charges, so be careful not to configure unnecessary metric collection. Ensure that only the metrics that need to be collected are collected.

  • Free provision is limited to 10 per account/region.
Reference
For detailed information about using the ServiceWatch Agent, refer to How-to guides > Using ServiceWatch Agent.

ServiceWatch Custom Metrics and Logs API

You can collect custom metrics and logs using the OpenAPI/CLI provided by ServiceWatch.

You can deliver custom metric data and custom logs to ServiceWatch via the ServiceWatch OpenAPI/CLI, and view the visualized information in the Console.

Caution

Collecting metrics via ServiceWatch OpenAPI/CLI is classified as custom metrics, and unlike the default metrics collected from each service, it incurs charges, so be careful not to configure unnecessary metric collection. Ensure that only the metrics that need to be collected are configured for collection.

  • Free provision is limited to 10 per account/region.

Create custom metric metadata

To collect metric data generated from a user’s resources or applications—not the metrics provided by Samsung Cloud Platform services (e.g., Virtual Server, etc.)—into ServiceWatch, you must create custom metric metadata.

Parameterdescription
namespaceUsers can define a namespace in ServiceWatch that distinguishes it from other metrics.
  • The namespace must be 3 to 128 characters long, consisting of letters, numbers, spaces, and special characters (_-/), and must start with a letter.
metricMetas > metricNameSet the name of the metric to be collected. The metric name must be 3 to 128 characters, consisting of letters, numbers, and special characters (_), and must start with a letter.
  • Example: custom_cpu_seconds_total
metricMetas > storageResolutionSet the collection interval for the relevant metric. The default is 60 (1 minute), and it can be set in seconds.
metricMetas > unitMetric unit can be set
  • Example: Bytes, Count, etc.
metricMetas > dimensionsYou can set dimensions to identify custom metric data and visualize it in the Console. When visualizing the collected metrics in the Console, they are displayed in combinations based on the dimension (dimensions) settings.
metricMetas > descriptionKoKorean description of the metrics being collected
metricMetas > descriptionEnEnglish description of the metrics being collected
Table. Description of custom metric metadata parameters

For detailed information on creating custom metric metadata, see CreateCustomMetricMetas.

Create custom metric

After generating custom metric metadata, you can send the resulting metric data to ServiceWatch using the CreateCustomMetrics API.

The transmitted metric data can be queried, organized by the configured namespace.

For detailed information on generating custom metric data, see CreateCustomMetrics.

Metric Data Query

Metric data, including custom metrics, can be retrieved using the Console and the ListMetricInfos API.

For detailed information on retrieving metric data, see ListMetricInfos and ListMetricData.

Create log stream

A ServiceWatch log group is required for custom log collection. Log groups can only be created in the Console. After creating a log group in advance, you can use the log stream creation API to create a log stream that will be delivered to ServiceWatch.

For detailed information on creating a log stream, see CreateCustomLogStream.

Log Event Creation

To collect custom logs, after creating a log group and log stream, we use the log event creation API to deliver individual log messages (log events) to ServiceWatch.

For detailed information on creating log events, refer to CreateCustomLogEvents.

2 - How-to guides

Users can monitor resources created on the Samsung Cloud Platform through ServiceWatch.

Using the Dashboard

You can monitor resources on the ServiceWatch dashboard detail screen.

information
  • To use the dashboard, you must first create a dashboard and register monitoring metrics as widgets.
  • Please refer to Creating a Dashboard for detailed information on dashboard creation.

To monitor resources with the dashboard, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. 1. Navigate to the Service Home page.
  2. On the Service Home page, click the Dashboard > Dashboard List menu. 2. Navigate to the Dashboard List page.
  3. On the Dashboard List page, click the dashboard for the resource you want to monitor. 3. Navigate to the Dashboard Details page.
  4. Dashboard Details page, select the monitoring period and time zone, then monitor resources using the widget.
    CategoryDetailed description
    Dashboard nameDashboard name
    • click to select another dashboard
    Period setting areaPeriod selection applied to widgets in the dashboard
    • Metric queries can be set from now up to a maximum of 455 days
    Time Zone Settings SectionSelect the time zone applied to the period setting
    Reset buttonReset all actions and settings made on the dashboard detail screen.
    Refresh Settings AreaSelect refresh interval for widget information
    • Refresh button displays information anew based on the current time
    • Click the refresh interval to select the desired period: Off, 10 seconds, 1 minute, 2 minutes, 5 minutes, 15 minutes
    EditEdit dashboard information
    • When the Edit button is clicked, navigate to the Dashboard Edit page
    MoreDisplay additional tasks for managing the dashboard
    Alert StatusShow the number of active alerts linked to recommended metrics on the service dashboard, displayed by stage
    • When the View All Alert Policies button is clicked, navigate to the Alert Policy List page
    • When the Expand button is clicked, the content is provided as widgets (up to 12)
      • View Alert Policy: navigate to the Alert Policy Details page for the corresponding metric
    Dashboard statusDisplay metric widgets for monitoring each resource
    • Click the Widget Expand View button to view detailed information about the metric
    • Click the More button to manage widgets
    • When the mouse cursor is placed on the graph, a popup displays the time, data value, and metric data for that point
    • You can drag the mouse to zoom in on a specific area of the graph
    • Clicking a resource name shown in the legend displays detailed information about that resource in a popup
    Table. Dashboard detailed items
Reference
  • Click the More > View Metrics button at the top right of the widget to view metric information for that widget on the Metrics page.
  • For detailed information about the Metric page, please refer to Metric View.

Setting dashboard favorites

You can bookmark frequently used dashboards and easily navigate to the dashboard from the ServiceWatch Service Home page. To bookmark the dashboard, follow these steps.

  1. All Services > Management > ServiceWatch menu, click. 1. Go to the Service Home page.
  2. On the Service Home page, click the Dashboard > Dashboard List menu. 2. Navigate to the Dashboard List page.
  3. Dashboard List page, check the favorite icon of the dashboard you want to bookmark. Click the dashboard to view its details. 3. Navigate to the Dashboard Details page.
    • Bookmarked dashboards are added to the bottom of the Dashboard > Dashboard Favorites menu and the Dashboard Favorites section on the Service Home page.

Widget Details

You can enlarge widgets within the dashboard to view them individually. To enlarge and view an individual widget, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. 1. Go to the Service Home page.
  2. On the Service Home page, click the Dashboard > Dashboard List menu. 2. Navigate to the Dashboard List page.
  3. Dashboard List page, click the dashboard for the resource you want to monitor. 3. Navigate to the Dashboard Details page.
  4. On the Dashboard Details page, click the Widget Zoom button for the widget you wish to enlarge. 4. The Metric Details popup opens for this widget.
    CategoryDetailed description
    Widget nameDisplay widget name
    Period setting areaPeriod selection applied to the widget
    • Metric lookup can be set from now up to a maximum of 455 days
    Time Zone Settings SectionSelect the time zone applied to the period setting
    Reset buttonReset all actions and settings made on the dashboard detail screen.
    StatisticsSelect statistical basis for the metric displayed in the widget
    • Click the statistical basis to select: average, minimum, maximum, sum
    Aggregation Period Setting AreaSelect aggregation period for widget information
    • Click the aggregation period to choose the desired interval: 1 minute, 5 minutes, 15 minutes, 30 minutes, 1 hour, 3 hours, 6 hours, 12 hours, 1 day
    Refresh Settings AreaSelect refresh interval for widget information
    • Refresh button displays information anew based on the current time
    • Click the refresh interval to select the desired period: Off, 10 seconds, 1 minute, 2 minutes, 5 minutes, 15 minutes
    Chart areaDisplay monitoring results as a chart
    • When the mouse cursor is placed over the graph or legend area, a popup shows the time, data value, and metric data for that point
    • You can drag the graph area to zoom into the selected region
    • Clicking a resource name displayed in the legend opens a popup with the alarm status for that resource
    Table. Detailed indicator items

Check alarm history

You can view the alert history for metrics registered on the ServiceWatch dashboard. To view the alarm history, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. 1. Service Home Go to the page.
  2. On the Service Home page, click the Alarm > Alarm History menu. 2. Go to the Alarm History page.
  3. Check the alarm history on the Alarm History page.
    CategoryDetailed description
    Alert filter and search areaFilter or search alarm history
    • All alarm statuses: Filter by selecting an alarm status
    • Enter the alarm policy name in the search field to search
    • Advanced search: Search by entering the alarm policy name, alarm status, or change timestamp
    Alert Policy NameAlert policy name
    • Click the alert policy name to view detailed information of that alert policy
    ConditionAlarm trigger conditions and total occurrence time
    • Stage display according to severity: High, Middle, Low
    CategoryDistinguish alarm creation and alarm status change information
    Alarm statusCurrent alert status
    • Normal: when the metric does not meet the configured condition
    • Insulfficient data: when the metric data cannot be retrieved (missing, nonexistent, not arrived)
    • Alert: when the metric meets the configured condition
    Alert levelWhen the alarm status is Alert, display the alarm level
    • High, Middle, Low
    Table. Alarm History Items
Reference
  • You can view the recent alarm status through Copilot.
    • ‘Alarm name’ or ‘ID’ alarm query: You can view the alarm status widget for the past 3 hours. * When you click the Alert Policy Shortcut button, you will be taken to the detail page of that alert policy.
    • ‘Show recent alerts’: You can view up to 5 of the most recent alerts. * Click the Alert Policy List Shortcut button to go to the alert policy list page.
  • You can create and manage new alert policies. * For detailed information about the alert policy, please refer to View alert policy.

Monitoring Metrics

You can view and monitor the metrics available in ServiceWatch.

Compare by indicator

You can select one or multiple metrics and resources to monitor. To compare and monitor by metric, follow these steps.

  1. All Services > Management > ServiceWatch menu, click. 1. Navigate to the Service Home page.

  2. On the Service Home page, click the Metrics menu. 2. Go to the Indicator page.

  3. On the Metrics page, in metric view mode, click Metric Comparison.

  4. Select the metric to monitor from the metric list on the Metric page. 4. The monitoring chart for the selected metric is displayed in the Selected Metric area at the bottom.

    CategoryDetailed description
    Indicator List AreaList of metrics that can be monitored in ServiceWatch
    • Click the + button in front of the namespace or dimension to view the sub-level list
    • When you select a metric to monitor, it is displayed as a chart in the Selected Metrics area
    Search filter areaAfter setting the search items to filter, click the Apply Filter button to filter the metric list
    • Namespace-Dimension Name: Search based on the sub-dimension names of the selected namespace
    • Metric Name: Search by entering the exact metric name
    • Resource Name: Search by entering the exact resource name
    • Resource ID: Search by entering the exact resource ID
    • Keyword: Search based on the selected top-level category and the entered keyword
      • Proceed with item-specific searches excluding metric name, resource name, resource ID, and tag key
    • Tag Key: Search using the selected tag key
    Table. Indicator list items

  5. Check the monitoring chart in the Selected metric area.

    CategoryDetailed description
    Period setting areaSelect the period applied to the chart
    • Indicator lookup can be set from now up to a maximum of 455 days
    Time Zone Settings AreaSelect the time zone applied to the chart
    Reset buttonReset all modifications and settings made on the chart
    Refresh Settings AreaSelect chart refresh interval
    • Refresh button displays information anew based on the current time
    • Click the refresh interval to select the desired interval: Off, 10 seconds, 1 minute, 2 minutes, 5 minutes, 15 minutes
    MoreDisplay additional tasks for managing charts
    graph areaData graph collected during the period applied to the chart
    • When the mouse cursor is placed on the graph, a popup displays the time, data value, and metric data information for that point
    • You can drag the mouse to zoom in on a specific area of the graph
    • Clicking a label name displayed in the legend shows detailed information about that legend in a popup
    Table areaView and edit labels, statistics, and aggregation periods for each legend
    • Legend: Color per legend
      • Click a legend color to change it to another color
    • Label: Displays the namespace, resource name, and metric name of the selected metric
      • Click the legend name to edit it
      • Enter using letters, numbers, and special characters, between 3 and 255 characters
    • Statistics: Choose how to aggregate metric data
      • Select from Average (default), Minimum, Maximum, Sum
    • Aggregation period: Choose the time unit for aggregating metric values
      • Select from 1 minute, 5 minutes (default), 15 minutes, 30 minutes, 1 hour, 3 hours, 6 hours, 12 hours, 1 day
    • More: Delete a legend or create an alert policy for the legend
    Table. Indicator comparison monitoring chart items
    Reference
    • The statistical method is as follows.
      • Total: sum of all data point values collected during the period
      • Average: the value obtained by dividing the sum over the specified period by the number of data pointers during that period.
      • Minimum: the lowest value observed during the specified period
      • Maximum: the highest value observed during the specified period
    • For a detailed description of the metric, refer to Metric Overview.

Compare by Date

You can monitor by comparing a metric and a resource across dates or time periods. To compare and monitor by date or period, follow these steps.

  1. All Services > Management > ServiceWatch menu, click it. 1. Navigate to the Service Home page.

  2. On the Service Home page, click the Metrics menu. 2. Go to the Indicator page.

  3. On the Metrics page, in view mode, click Date Comparison.

  4. Select the metric to monitor from the metric list on the Metric page. 4. The monitoring chart for the selected metric is displayed in the Selected Metric area at the bottom.

    CategoryDetailed description
    Indicator List AreaList of metrics that can be monitored in ServiceWatch
    • Click the + button in front of the namespace or dimension to view the sub-level list
    • When you select a metric to monitor, it is displayed as a chart in the selected metric area
    Search filter areaAfter setting the search items to filter, click the Apply Filter button to filter the metric list
    • Namespace-Dimension Name: Search based on the sub-dimension names of the selected namespace
    • Metric Name: Search by entering the exact metric name
    • Resource Name: Search by entering the exact resource name
    • Resource ID: Search by entering the exact resource ID
    • Keyword: Search based on the selected top-level category and the entered keyword
      • Proceed with item-specific searches excluding metric name, resource name, resource ID, and tag key
    • Tag Key: Search using the selected tag key
    Table. Indicator list items

  5. Check the monitoring chart in the selected metric area.

    CategoryDetailed description
    Date comparison / period comparisonSelect criteria for comparing indicators
    • Date comparison: Compare by selecting a specific date
    • Period comparison: Compare by selecting a specific period
    Date and period setting areaSelect date or period to compare
    • Date comparison: Select the date to view on the chart
    • Period comparison: Select the period to view on the chart
    • You can select up to four dates or periods within a maximum of 455 days from today
    Time Zone Settings SectionSelect the time zone applied to the chart
    Reset buttonReset all manipulations and settings made on the chart
    Refresh Settings AreaSelect chart refresh interval
    • Refresh button updates the information based on the current time
    • Click the refresh interval to select the desired interval: Off, 10 seconds, 1 minute, 2 minutes, 5 minutes, 15 minutes
    MoreDisplay additional tasks for managing charts
    graph areaData graph collected during the period applied to the chart
    • When the mouse cursor is placed on the graph, a popup displays the time, data value, and metric data information for that point
    • You can drag the mouse to zoom in on a specific area of the graph
    • Clicking the date or period shown in the legend displays detailed information about that legend in a popup
    Table areaView and edit labels, statistics, and aggregation periods for each legend
    • Legend: Color per legend
      • Click a legend color to change it to another color
    • Period: Period applied to the chart
    • Metric: Displays the namespace, resource name, and metric name of the selected metric
    • Statistics: Choose how to aggregate metric data
      • Average(default), Minimum, Maximum, Sum can be selected.
      • Refer to the green icon displayed to the right of a meaningful metric in the relevant metric
    • Aggregation Period: Select the aggregation period unit for metric values
      • 1 minute, 5 minutes(default), 15 minutes, 30 minutes, 1 hour, 3 hours, 6 hours, 12 hours, 1 day can be selected
    • More: Delete a legend or create an alert policy for a legend
    Table. Date comparison monitoring chart items
    Reference
    • The statistical method is as follows.
      • Total: sum of all data point values collected during the period
      • Average: the value obtained by dividing the sum over the specified period by the number of data pointers during that period
      • Minimum: the lowest value observed during the specified period
      • Maximum: the highest value observed during the specified period
    • For detailed explanations of the metrics, refer to the Metric Overview.

Log Monitoring

You can monitor logs collected from the Samsung Cloud Platform service.

information
To view log monitoring data, you must first create a log group and log stream. For detailed information about log groups, please refer to Log Monitoring.

To view the log monitoring data, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. 1. Navigate to the Service Home page.
  2. On the Service Home page, click the Log > Log Group menu. 2. Navigate to the Log Group List page.
  3. On the Log Group List page, click the log group name to view its details. 3. Navigate to the Log Group Details page.
  4. On the Log Group Details page, click the Log Stream tab. 4. Log Stream list is displayed.
  5. log stream Click the log stream name in the list to view detailed information. 5. Navigate to the Log Stream Details page.
    • Click the All Log Streams View button at the top of the log stream list to go to the All Log Streams Details page.
      CategoryDetailed description
      Excel downloadLog stream history can be downloaded as an Excel file
      Timestamp listMessage list by timestamp
      • Select period, user time zone, can filter using message input
      Table. Log group details - Log stream detail items

Receive event notifications

You can create a system event rule for changes to resources generated in Samsung Cloud Platform and receive them as notifications.

guide
To receive event notifications, you must first create an event rule. For detailed information on creating event rules, see Create Event Rule.

Installing ServiceWatch Agent

You can install the ServiceWatch Agent to collect custom metrics and logs from the monitoring target.

Caution
Collecting metrics through the ServiceWatch Agent is classified as custom metrics, and unlike the default metrics collected from each service, it incurs charges, so you should be careful not to configure unnecessary metric collection. Make sure to configure it so that only the metrics that need to be collected are collected.

To install the ServiceWatch Agent, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. 1. Navigate to the Service Home page.
  2. On the Service Home page, click the Agent Setup & Guideline button. 2. Agent Setup & Guideline A popup window opens.
  3. Agent Setup & Guideline Copy the installation file URL from the popup window and go to that address. 3. Agent, manager, and configuration files can be downloaded.
Reference
Collecting custom metrics and logs via the ServiceWatch Agent is currently available only on Samsung Cloud Platform For Enterprise. It will also be available in other offerings in the future.

2.1 - Managing Dashboards and Widgets

In the Samsung Cloud Platform Console, you can create and manage dashboards to monitor the resources of the services you are using.

Create Dashboard

You can create a ServiceWatch dashboard.

Creating a dashboard by adding individual widgets

To create a dashboard, follow these steps.

  1. All Services > Management > ServiceWatch menu, click it. You will be taken to the Service Home page.

  2. Click the Dashboard > Dashboard List menu on the Service Home page. You will be taken to the Dashboard List page.

  3. On the Dashboard List page, click the Create Dashboard button.

  4. Please enter the dashboard name.

    • Enter the dashboard name using English letters, numbers, and special characters (-_) within 3 ~ 40 characters.
    • You cannot enter a name that is already in use on the service dashboard.
  5. Add a widget to configure the dashboard. A popup window appropriate to the widget addition method will open.

    • Add Individual Widget: You can add a single widget that combines metrics and resources. Clicking the button opens the Add Individual Widget popup.
      Category
      Required status
      Detailed description
      Indicator classificationSelectionIn ServiceWatch, filter the monitorable metrics as All or Key Metrics and display them in the metric list
      Indicator List AreaRequiredList of metrics that can be monitored in ServiceWatch
      • Click the + button in front of the namespace and dimension to view the sub-level list
      • When you select a metric to monitor, it is displayed as a chart in the Selected Metrics area
      Search filter area-After setting the search items to filter, click the Apply Filter button to filter the metric list
      • Namespace-Dimension Name: Search based on the sub-dimension names of the selected namespace
      • Metric Name: Enter the exact metric name to search
      • Resource Name: Enter the exact resource name to search
      • Resource ID: Enter the exact resource ID to search
      • Keyword: Search based on the selected top-level category and the entered keyword
        • Proceed with item-specific searches excluding metric name, resource name, resource ID, and tag key
      • Tag Key: Search using the selected tag key
      Selected metric area-Monitoring chart for the selected metric in the metric list area
      • Data graph collected during the period applied to the chart
        • When the mouse cursor is placed on the graph, a popup displays the time, data value, and metric data information for that point
        • You can drag the mouse to zoom in on a specific area of the graph
        • Clicking the resource name shown in the legend displays detailed information about that resource in a popup
      • Item values in the table area within the chart can be edited
        • Label: Enter the legend name using English letters, numbers, or special characters, between 3 ~ 255 characters
        • Statistics: Choose the method for aggregating metric data
          • Options: average (default), minimum, maximum, sum
        • Aggregation period: Select the aggregation period unit for metric values
          • Options: 1 minute, 5 minutes (default), 15 minutes, 30 minutes, 1 hour, 3 hours, 6 hours, 12 hours
        • Delete: Remove the legend
      Table. Individual widget additional items
  6. Click the Complete button in the widget addition popup. The widget will be added to the dashboard on the dashboard creation page.

  7. After confirming the added widget, click the Create button. A popup indicating dashboard creation will appear.

  8. Click the Confirm button. Dashboard creation is complete.

Creating a dashboard by adding multiple widgets

To create a dashboard, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. You will be taken to the Service Home page.

  2. On the Service Home page, click the Dashboard > Dashboard List menu. You will be taken to the Dashboard List page.

  3. On the Dashboard List page, click the Create Dashboard button.

  4. Enter the name of the dashboard.

    • Enter the dashboard name using English letters, numbers, and special characters (-_) within 3 ~ 40 characters.
    • You cannot enter a name that is already in use on the service dashboard.
  5. Add a widget to configure the dashboard. A corresponding popup window will open according to the widget addition method.

    • Add Multiple Widgets: Select the desired resources by metric unit and add multiple widgets at once. Clicking the button opens the Add Multiple Widgets popup window.
      Category
      Required or not
      Detailed description
      Indicator classificationSelectIn ServiceWatch, filter the monitorable metrics as All or Key Metrics and display them in the metric list
      Indicator selection areaRequiredSelect the namespace and resources to add
      • Click the + button in front of the namespace and resources to view the list of sub-resources and metrics
      • When you check the metrics to add to the widget from the metric list, the Selected Metrics and Selected Resources sections are displayed
      • Multiple metrics can be selected
      Selection indicatorRequiredDisplay the list of selected metrics from the namespace and resource list
      • When a metric is clicked, the Selected Resources area shows the list of resources included in that metric
      Selected resourceRequiredSelected Indicator list, add resources to the selected indicator
      • After clicking the Select button, choose resources that can be added to the indicator, allowing up to five additions
      • Resources must be added for all indicators in the Selected Indicator list
      StatisticsRequiredSelect the statistical basis for the indicator value
      • You can choose from average (default), minimum, maximum, or sum
      Aggregation periodRequiredSelect the aggregation period unit for metric values
      • Choose from 1 minute, 5 minutes (default), 15 minutes, 30 minutes, 1 hour, 3 hours, 6 hours, or 12 hours
      Table: Additional items for multiple widgets
  6. Click the Complete button on the widget addition popup. The widget will be added to the dashboard on the dashboard creation page.

  7. After confirming the added widget, click the Create button. A popup indicating dashboard creation will appear.

  8. Click the Confirm button. The dashboard has been created.

Create a dashboard by loading a dashboard

To create a dashboard, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. You will be taken to the Service Home page.

  2. Click the Dashboard > Dashboard List menu on the Service Home page. You will be taken to the Dashboard List page.

  3. On the Dashboard List page, click the Create Dashboard button.

  4. Enter the name of the dashboard.

    • Enter the dashboard name using English letters, numbers, and special characters (-_) within 3 ~ 40 characters.
    • You cannot enter a name that is already in use on the service dashboard.
  5. Add a widget to configure the dashboard. A corresponding popup window will open according to the widget addition method.

    • Dashboard Load: You can load widgets from dashboards registered in ServiceWatch. When you click the button, the Dashboard Load popup opens.
      Category
      Required
      Detailed description
      DashboardRequiredDisplay the list of dashboards registered in ServiceWatch
      • When a dashboard is selected, the widgets applied to the dashboard are displayed in the preview area
      PreviewRequiredDisplay widgets applied to the selected dashboard from the dashboard list
      • Check the widget name to select widgets to add to the dashboard to be created
      • If you check the Select All item, all metrics of that dashboard are selected
      Table. Load Dashboard Items
  6. Click the Complete button in the widget addition popup. The widget will be added to the dashboard on the dashboard creation page.

  7. After confirming the added widget, click the Create button. A popup indicating dashboard creation will open.

  8. Click the Confirm button. Dashboard creation is complete.

Check the dashboard

You can view the information of the selected dashboard on the Dashboard List page. To view the dashboard, follow the steps below.

  1. Click the All Services > Management > ServiceWatch menu. You will be taken to the Service Home page.
  2. On the Service Home page, click the Dashboard > Dashboard List menu. You will be taken to the Dashboard List page.
    CategoryDetailed description
    Dashboard nameDashboard name
    • User dashboards are the dashboard names set by the user. Service dashboards are the Samsung Cloud Platform service name that matches the service namespace
    Dashboard CategoryDashboard classification
    • User: Dashboard created directly by the user
    • Service: Dashboard automatically composed of pre-built key metrics for each service
    Modification date and timeDashboard modification timestamp
    Creation date and timeDashboard creation date and time
    FavoritesIf bookmarked, it is displayed in yellow
    • Click the star icon to set or remove a bookmark
    Table. Dashboard list items
  3. On the Dashboard List page, click the dashboard whose details you want to view. You will be taken to the Dashboard Detail page.
    CategoryDetailed description
    Dashboard nameDisplay the dashboard name
    • Click the name to select another dashboard
    Period setting areaPeriod selection applied to widgets in the dashboard
    • Metric queries can be set from now up to a maximum of 455 days
    Time zone setting areaSelect the time zone applied to the period setting
    Reset buttonReset all actions and settings made on the dashboard detail screen
    Refresh Settings AreaSelect refresh interval for widget information
    • Refresh button updates the information based on the current time
    • Click the refresh interval to choose the desired period: Off, 10 seconds, 1 minute, 2 minutes, 5 minutes, 15 minutes
    EditYou can edit the dashboard name or manage widgets
    • When you click the Edit button, you are taken to the Dashboard Edit page
    MoreDisplay additional tasks for managing the dashboard
    • Dashboard duplication and deletion, view details, view source are possible
    Widget areaDisplay widgets for monitoring each resource
    • You can manage the widget by clicking the More button at the top right of the widget
    • You can edit, duplicate, download files, view metrics, and view source of the widget
    Table. Dashboard detailed items

Dashboard Management

Dashboard Details page allows you to edit or manage dashboard information and widgets.

Edit Dashboard

You can modify the dashboard name and change the widget configuration.

Information
The service dashboard cannot be edited.

To modify the dashboard, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. You will be taken to the Service Home page.
  2. Click the Dashboard > Dashboard List menu on the Service Home page. You will be taken to the Dashboard List page.
  3. On the Dashboard List page, click the dashboard you want to view details for. You will be taken to the Dashboard Details page.
  4. Click the Edit button at the top right of the Dashboard Details page. You will be taken to the Dashboard Edit page.
  5. After modifying the dashboard’s information or widgets, click the Save button.
    CategoryDetailed description
    Dashboard nameDashboard name cannot be edited
    • Enter within 34 characters using English letters, numbers, and special characters (-_)
    • Dashboard names that are currently in use cannot be used
    Widget NameWidget name can be edited
    • English letters, numbers, spaces, special characters(-_.\
    Widget ManagementWhen you hover the mouse over a widget, a management button appears on the right side of the widget border
    • Edit: Widget Edit popup allows you to modify the widget’s metrics and resources
    • Duplicate: Duplicate the current widget and add it to the dashboard
    • Delete: Remove the current widget from the dashboard
    • Expand: Display the current widget with an expanded size
      • Collapse: If the widget is expanded, clicking again reduces its size
    Add widgetAdd a new widget to the dashboard
    • Add individual widget: Add a single widget that combines metrics and resources
    • Add multiple widgets: Select desired resources per metric to add multiple widgets at once
    • Load dashboard: Load and add widgets from another dashboard
    Table. Dashboard edit items

View detailed dashboard information

You can view detailed information about the dashboard. To view detailed information of the dashboard, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. You will be taken to the Service Home page.
  2. Click the Dashboard > Dashboard List menu on the Service Home page. You will be taken to the Dashboard List page.
  3. On the Dashboard List page, click the dashboard you want to view details for. You will be taken to the Dashboard Details page.
  4. Dashboard Details page’s top right corner has a More > Details button. Click the button. The Dashboard Details popup opens.
    CategoryDetailed description
    Dashboard nameDashboard name
    Dashboard CategoryDashboard usage classification
    • User: dashboard created directly by the user
    • Service: dashboard composed of automatically pre-built key metrics for each service
    Serviceservice name
    Resource Typedashboard
    SRNUnique resource ID in Samsung Cloud Platform
    • In ServiceWatch, it refers to the dashboard’s SRN
    Resource nameResource Name
    • In ServiceWatch, the meaning of the dashboard name
    Resource IDUnique resource ID in the service
    ConstructorUser who created the dashboard
    Creation date and timeDashboard creation date and time
    EditorUser who edited the dashboard information
    Modification date and timeDashboard information modification timestamp
    Table. Dashboard Details - Detail Information Popup Items
Reference

When sorting dashboard names in the dashboard list, follow the sorting rules below.

  1. Whitespace and control characters
  2. Some special characters ( !"#$%&()*+,-./ )
  3. Numbers (0–9)
  4. Some special characters ( ; < = > ? @ )
  5. English (A–Z, a–z, case-insensitive)
  6. Remaining special characters ([\]^_`)
  7. Other characters

Check the dashboard source code

You can view the dashboard’s source code. To view the source code of the dashboard, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. You will be taken to the Service Home page.
  2. Click the Dashboard > Dashboard List menu on the Service Home page. You will be taken to the Dashboard List page.
  3. On the Dashboard List page, click the dashboard you want to view details for. You will be taken to the Dashboard Details page.
  4. Dashboard Details on the top right of the page, click the More > View Source button. The Dashboard View Source popup opens.
    CategoryDetailed description
    Source informationDisplay the dashboard source code in JSON format
    Copy codeCopy the source code to the clipboard
    Table. Dashboard Details - Dashboard Source View Popup Items

Duplicate Dashboard

You can duplicate a widget from the current dashboard and add it to another dashboard.

Information

User permission is required to duplicate the dashboard.

  • User: {email}
  • Action: iam:CreatGroup
  • On resource: {SRN}
  • Context: no identity-based policy allows the action

To duplicate the dashboard, follow these steps.

  1. All Services > Management > ServiceWatch menu, click it. You will be taken to the Service Home page.

  2. On the Service Home page, click the Dashboard > Dashboard List menu. You will be taken to the Dashboard List page.

  3. On the Dashboard List page, click the dashboard you want to view details for. You will be taken to the Dashboard Details page.

  4. Click the More > Duplicate button at the top right of the Dashboard Details page. The Dashboard Duplicate popup opens.

  5. After selecting the dashboard duplication method, enter the required information. The required information varies depending on the duplication method.

    Category
    Required
    Detailed description
    Replication target-Name of the dashboard to duplicate
    Cloning methodRequiredAfter duplicating the dashboard widget, select the dashboard to add it to
    • New Dashboard: Create a new dashboard and generate it by duplicating the current dashboard’s widget
    • Existing Dashboard: Duplicate the current dashboard’s widget and add it to an existing dashboard
    Dashboard nameRequiredEnter the name of the new dashboard
    • Displayed when the duplication method is set to New Dashboard
    • Enter using English letters, numbers, and special characters (-_) within 3 to 40 characters
    Select DashboardRequiredSelect the dashboard to which the duplicated widget will be added from the existing dashboards
    • Displayed when the duplication method is selected as Existing dashboard
    Table. Dashboard clone items

  6. After entering the required information, click the Complete button. A popup notifying that the dashboard is being duplicated will appear.

  7. Click the Confirm button on the popup window. The dashboard duplication task is complete.

Reference
You can duplicate a service dashboard to add widgets to a user dashboard, or create a new dashboard.

Delete dashboard

You can delete unused dashboards.

Information
The service dashboard cannot be deleted.

To delete the dashboard, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. You will be taken to the Service Home page.
  2. On the Service Home page, click the Dashboard > Dashboard List menu. You will be taken to the Dashboard List page.
  3. On the Dashboard List page, select the checkbox of the dashboard you want to delete, then click the Delete button. A popup confirming the dashboard deletion will appear.
    • You can delete multiple dashboards simultaneously.
    • You can also delete individually by clicking the More > Delete button located at the top right of the Dashboard Details page.
  4. In the delete confirmation input field, type Delete and then click the Confirm button. The dashboard will be deleted.

Manage Widgets

Dashboard Details page lets you edit or manage widgets.

Edit Widget

You can modify the widget’s metrics and resources.

Information
Widgets on the service dashboard cannot be edited.

To modify the widget, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. You will be taken to the Service Home page.
  2. On the Service Home page, click the Dashboard > Dashboard List menu. You will be taken to the Dashboard List page.
  3. On the Dashboard List page, click the dashboard whose widget you want to edit. You will be taken to the Dashboard Details page.
  4. On the Dashboard Details page, click the More > Edit Widget button at the top right of the widget you want to edit. The Edit Widget popup will open.
  5. After modifying the widget’s metrics and resources, click the Confirm button. The widget modification is complete.
    Category
    Required status
    Detailed description
    Indicator classificationSelectIn ServiceWatch, filter the monitorable metrics as All or Key Metrics and display them in the metric list
    Indicator List AreaRequiredList of metrics that can be monitored in ServiceWatch
    • Click the + button in front of the namespace and dimension to view the sub-level list
    • When you select a metric to monitor, it is displayed as a chart in the Selected Metrics area
    Search filter area-After setting the search items to filter, click the Apply Filter button to filter the metric list
    • Namespace-Dimension Name: Search based on the sub-dimension names of the selected namespace
    • Metric Name: Enter the exact metric name to search
    • Resource Name: Enter the exact resource name to search
    • Resource ID: Enter the exact resource ID to search
    • Keyword: Search based on the selected top-level category and the entered keyword
      • Proceed with item-specific searches excluding metric name, resource name, resource ID, and tag key
    • Tag Key: Search using the selected tag key
    Selected metric area-Monitoring chart for the selected metric in the metric list area
    • Data graph collected during the period applied to the chart
      • When the mouse cursor is placed on the graph, a popup displays the time, data value, and metric data information for that point
      • You can drag the mouse to zoom in on a specific area of the graph
      • Clicking the label name displayed in the legend shows detailed information for that legend in a popup
    • In the table area within the chart, you can view and edit legend labels, statistics, and aggregation periods
      • Legend: color per legend
        • Click a legend color to change it to another color
      • Period: period applied to the chart
      • Metric: displays the selected metric’s namespace, resource name, and metric name
      • Statistics: select the method for aggregating metric data
        • Choose among Average (default), Minimum, Maximum, Sum
      • Aggregation period: select the aggregation period unit for metric values
        • Choose among 1 minute, 5 minutes (default), 15 minutes, 30 minutes, 1 hour, 3 hours, 6 hours, 12 hours, 1 day
      • Delete: remove the legend
    Table. Individual widget additional items

Widget Replication

You can copy the widget and add it to another dashboard.

Information

User permission is required to duplicate the dashboard.

  • User: {email}
  • Action: iam:CreatGroup
  • On resource: {SRN}
  • Context: no identity-based policy allows the action

To duplicate a widget, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. You will be taken to the Service Home page.

  2. Service Home page, click the Dashboard > Dashboard List menu. You will be taken to the Dashboard List page.

  3. On the Dashboard List page, click the dashboard you want to duplicate. You will be taken to the Dashboard Details page.

  4. On the Dashboard Detail page, click the More > Widget Clone button located at the upper right of the widget to be duplicated. The Widget Clone popup window opens.

  5. After selecting the widget duplication method, enter the required information. The required information varies depending on the duplication method.

    Category
    Whether required
    Detailed description
    Replication target-Name of the dashboard to duplicate
    Cloning methodRequiredAfter duplicating the widget, select the dashboard to add it to
    • Existing Dashboard: Add the widget to an existing dashboard
    • New Dashboard: Create a new dashboard and add the widget
    Select DashboardRequiredSelect the dashboard to which the duplicated widget will be added from the existing dashboards
    • When the duplication method is selected as Existing Dashboard, it is displayed
    Dashboard nameRequiredEnter the name of the new dashboard
    • Displayed when the duplication method is set to New Dashboard
    • Enter using English letters, numbers, and special characters (-_) within 3 to 40 characters
    Widget nameRequiredWhen adding a widget to the dashboard, enter the widget name
    • English letters, numbers, special characters(-_.\
    Table. Widget duplication items

  6. After entering the required information, click the Complete button. A popup window notifying the addition of the widget will open.

  7. Click the Confirm button in the popup window. The widget will be duplicated and added to the dashboard.

Download widget file

You can download widget information as a file. To download widget information, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. You will be taken to the Service Home page.
  2. On the Service Home page, click the Dashboard > Dashboard List menu. You will be taken to the Dashboard List page.
  3. On the Dashboard List page, click the dashboard from which you want to download widget information. You will be taken to the Dashboard Detail page.
  4. Dashboard Details page, click the More > File Download button at the top right of the widget whose information you want to download. The File Download popup window opens.
  5. After selecting the file download method, click the Confirm button. The download will start.
    • Download methods can be selected simultaneously.
      CategoryDetailed description
      CSVConvert the widget’s metrics and monitoring data to an Excel (*.csv) file and download it.
      PNGConvert the widget chart to an image (*.png) file and download
      Table. Widget file download item

Check widget metrics

You can view the widget’s resource and metric information on the Metrics page. To view widget metrics on the metrics page, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. You will be taken to the Service Home page.
  2. Service Home page, click the Dashboard > Dashboard List menu. You will be taken to the Dashboard List page.
  3. On the Dashboard List page, click the dashboard you want to view widget metrics for. You will be taken to the Dashboard Details page.
  4. On the Dashboard Detail page, click the More > View Metrics button at the top right of the widget you will view on the Metrics page. You will be taken to the Metrics page.
    • The resources and metric information of the selected widget are automatically configured and displayed on the Metrics page.
Reference
For detailed information about the Metric page, please refer to View Metrics.

Check widget source code

You can view the source code of the dashboard.

information
In the service dashboard, you cannot view the widget’s source information.

To check the dashboard’s source code, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. You will be taken to the Service Home page.
  2. Service Home page, click the Dashboard > Dashboard List menu. You will be taken to the Dashboard List page.
  3. On the Dashboard List page, click the dashboard you want to view details for. You will be taken to the Dashboard Detail page.
  4. On the Dashboard Details page, click the More > View Source button located at the top right of the widget to view its source code. The Widget Source View popup will open.
    CategoryDetailed description
    Source informationDisplay the widget source code in JSON format
    Copy codeCopy the source code to the clipboard
    Table. Widget source view item

Download widget file

You can download widget information as a file. To download widget information, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. You will be taken to the Service Home page.
  2. Service Home page, click the Dashboard > Dashboard List menu. You will be taken to the Dashboard List page.
  3. Dashboard List page, click the dashboard to download widget information. You will be taken to the Dashboard Detail page.
  4. Dashboard Details page, click the More > File Download button at the top right of the widget whose information you want to download. The File Download popup window opens.
  5. After selecting the file download method, click the Confirm button. The download will start.
    • Download methods can be selected simultaneously.
      CategoryDetailed description
      CSVConvert the widget’s metrics and monitoring data to an Excel (*.csv) file and download it.
      PNGConvert the widget chart to an image (*.png) file and download
      Table. Widget file download item

Export to Object Storage

You can store widget information in Object Storage.

information

User permissions are required to store data in Object Storage.

  • User: {email}
  • Action: iam:CreatGroup
  • On resource: {SRN}
  • Context: no identity-based policy allows the action

To store widget information in Object Storage, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. You will be taken to the Service Home page.
  2. On the Service Home page, click the Dashboard > Dashboard List menu. You will be taken to the Dashboard List page.
  3. On the Dashboard List page, click the dashboard from which you want to download widget information. You will be taken to the Dashboard Detail page.
  4. On the Dashboard Details page, click the More > Export to Object Storage button located at the top right of the widget whose information you want to download. The Export to Object Storage popup will open.
  5. After selecting the bucket to store widget information, click the Done button. A popup confirming the save will appear.
  6. Click the Confirm button in the popup window. Data export will begin.
Information
  • The limitations of metrics that can be exported to Object Storage are as follows.
    • Number of indicators: up to 10
    • Query period: within 2 months (63 days)
  • If the query period exceeds 2 months (63 days), only data for up to 63 days will be stored.
Reference
  • If there is no Object Storage to store metric data, create an Object Storage first, then proceed.
  • Metric data is stored in the “metricname-yyyymmddhhmmss.json” file format and can be accessed in the ~/servicewatch/metric path of the Object Storage bucket.

2.2 - Alert

In ServiceWatch, you can set threshold criteria for the metrics to be monitored, and create and manage alert policies that generate alert notifications when the specified conditions are met.

Reference
The Auto-Scaling Group policy will be integrated with ServiceWatch starting March 25, 2026. The policies of an Auto-Scaling Group are created in conjunction with ServiceWatch alarm policies, and alarm policies linked to an Auto-Scaling Group cannot be modified or deleted in ServiceWatch; they can only be managed through the Auto-Scaling Group.

Create Alert Policy

You can create an alert policy for a metric and set the criteria for alert triggering. To create an alert policy, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. You will be taken to the Service Home page.

  2. On the Service Home page, click the Alarm > Alarm Policy menu. You will be taken to the Alarm Policy List page.

  3. Click the Create Alert Policy button on the Alert Policy List page. You will be taken to the Create Alert Policy page.

  4. After entering the name and description of the alert policy in the Basic Information Input area, click the Select Metric button. The Select Metric popup window will open.

  5. Metric Selection In the popup window, after selecting the metric for which to create an alert policy, click the Confirm button. The Metric and Condition Settings area will be displayed.

    Category
    Required status
    Detailed description
    Indicator classificationRequiredIn ServiceWatch, filter the monitorable metrics as All or Key Metrics and display them in the metric list
    Indicator List AreaRequiredList of metrics that can be monitored in ServiceWatch
    • Click the **+** button in front of the namespace and dimension to view the sub-level list
    • When you select a metric to monitor, it is displayed as a chart in the **Selected Metric** area
      • If the metric is associated with a namespace, the **Service Dashboard** is displayed
      • Clicking the **Service Dashboard** navigates to the detailed page of that dashboard
    | | Search filter area | - | After setting the search items to filter, click the **Apply Filter** button to filter the metric list
    • **Namespace-Dimension Name**: Search based on the sub-dimension names of the selected namespace
    • **Metric Name**: Enter the exact metric name to search
    • **Resource Name**: Enter the exact resource name to search
    • **Resource ID**: Enter the exact resource ID to search
    • **Keyword**: Search based on the selected top-level category and the entered keyword
      • Proceed with item-specific searches excluding metric name, resource name, resource ID, and tag key
    • **Tag Key**: Search using the selected tag key
    | | Selected metric area | - | Monitoring chart for the selected metric in the metric list area
    • Data graph collected during the period applied to the chart
      • When the mouse cursor is placed on the graph, a popup displays the time, data value, and metric data information for that point
      • You can drag the mouse to zoom in on a specific area of the graph
      • Clicking a label displayed in the legend shows detailed information for that legend in a popup
    • In the table area within the chart, you can view and edit legend labels, statistics, and aggregation periods
      • **Legend**: color for each legend
        • You can click a legend color to change it to another color
      • **Period**: period applied to the chart
      • **Metric**: displays the selected metric's namespace, resource name, and metric name
      • **Statistics**: select the method for aggregating metric data
        • Choose among **Average** (default), **Minimum**, **Maximum**, **Sum**
      • **Aggregation Period**: select the aggregation period unit for metric values
        • Choose among **1 minute**, **5 minutes** (default), **15 minutes**, **30 minutes**, **1 hour**, **3 hours**, **6 hours**, **12 hours**, **1 day**
      • **Delete**: remove the legend
    |
    Table. Indicator selection popup items

  6. Set the threshold values for generating alerts in the Indicator and Condition Settings area.

    Category
    Required status
    Detailed description
    namespace-Namespace of the selected metric
    Indicator name-Name of the selected metric
    unit-Data unit of the selected metric
    Evaluation scopeRequiredTime range (seconds) for alarm evaluation
    • Input allowed up to a maximum of 604,800 seconds in multiples of 60
    • If set smaller than the collection interval or not in a multiple of the collection interval, alarm evaluation may be applied abnormally
    StatisticsRequiredSelect the method for calculating metric data over the evaluation range
    • Sum: The sum of all data point values collected during the period
    • Average: The value obtained by dividing the Sum over the specified period by the number of data points during that period
    • Minimum: The lowest value observed during the specified period
    • Maximum: The highest value observed during the specified period
    Additional configurationSelectSetting evaluation count, violation count, and missing data handling method
    • When the additional configuration is set to Use, you can set the evaluation count and violation count used for alarm evaluation. If the number of violations meets the condition within the evaluation count during the evaluation period (seconds), the alarm state changes to Alert
      • Evaluation Count: Number of evaluations that trigger an alarm
        • 1 ~ 8,640 enterable range
      • Violation Count: Allowed number of violations before an alarm is triggered
        • 1 ~ Evaluation Count enterable range
      • If the evaluation period is less than 1 hour (3,600 seconds), evaluation count/evaluation period can be set up to a maximum of 1 day (86,400 seconds)
      • If the evaluation period is 1 hour (3,600 seconds) or more, evaluation count/evaluation period can be set up to a maximum of 7 days (604,800 seconds)
    • When the additional configuration is set to Use, you can specify how to handle missing data during alarm evaluation.
      • Treat missing data as missing (Missing)
      • Ignore missing data and maintain the current alarm state (Ignore)
      • Treat missing data as satisfying the condition (Breaching)
      • Treat missing data as not satisfying the condition (Not breaching)
    Condition settingRequired
    • Condition Operator: After calculating metric data over the evaluation period, select a condition operator to compare the value with the threshold
    • Threshold: After calculating metric data over the evaluation period, set the threshold to compare the value with the condition operator
      • Input allowed from 0 ~ 2,147,483,647
    • Condition: Explanation of alert state (Alert) change conditions based on the configured Condition Operator and Threshold
    Alert levelRequiredSelect alert stage based on the importance of the alert policy
    Resource ID-Metric monitoring target resource ID
    Resource Name-Metric Monitoring Target Resource Name
    Table. Indicator and Condition Setting Items

  7. In the Notification Settings area, select the user who will receive notifications when an alarm occurs.

    • Only users with a login history (users who have registered an email or mobile phone number) can be added as notification recipients.
    • You can add up to 100 notification recipients.
Reference
  • If there is no user to add, you can create a user on the IAM service’s User Creation page. For detailed information on user creation, refer to Create User.
  • The notification reception method (E-mail or SMS) can be changed on the Alert Settings page after selecting the notification target as Service > Alert. For detailed information about alert settings, refer to 알림 설정 확인하기.
  1. Add tag information in the Additional Information Input area.
  2. After reviewing the summary information, click the Create button. A popup indicating the creation of the alert policy will open.
  3. Click the Confirm button. The alert policy has been created.
Reference
Creating an alert policy may take several tens of minutes depending on its scale.

Check detailed alert policy information

You can view and manage detailed information about alert policies. To view detailed information about the alert policy, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. Navigate to the Service Home page.
  2. On the Service Home page, click the Alert > Alert Policy menu. You will be taken to the Alert Policy List page.
    • In the Alert Policy menu, you can click the Alert Level button to filter and view only the list of alert policies that correspond to that alert level.
  3. On the Alert Policy List page, click the alert policy name to view its details. You will be taken to the Alert Policy Details page.
    CategoryDetailed description
    Alert policy statusAlert policy status
    • Active: The alert policy is in an active state
    • Inactive: The alert policy is in an inactive state
    • You can change it by clicking the Activate or Deactivate button
    Delete alarm policyDelete the relevant alert policy
    Alarm statusCurrent alert status
    • Normal: when the metric does not meet the configured condition
    • Insulfficient data: when the metric data cannot be verified (missing, nonexistent, not arrived)
    • Alert: when the metric meets the configured condition
    • When the alert status is Alert, display the alert level (>High, Middle, Low) as well
    Metric Monitoring ChartMetric monitoring chart for the configured period
    Information Classification TabAlert policy information tabs
    • Details, notifications, alert history, tags, operation history
    • Click each tab to view the corresponding information
    Table. Alarm detailed items
Reference

When sorting alarm policy names in the alarm policy list, follow the sorting rules below.

  1. Whitespace and control characters
  2. Some special characters ( !"#$%&()*+,-./ )
  3. Numbers (0–9)
  4. Some special characters ( ; < = > ? @ )
  5. English (A–Z, a–z, case-insensitive)
  6. Remaining special characters ([\]^_`)
  7. Other characters

Detailed Information

On the Alert Policy List page, you can view the selected alert policy’s basic information and metric information.

CategoryDetailed description
Serviceservice name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In ServiceWatch, it refers to the SRN of the resource type
Resource NameResource name
  • In ServiceWatch, it refers to the name of the alert policy
Resource IDUnique resource ID in the service
ConstructorUser who created the service
Creation dateService creation timestamp
EditorUser who edited the service information
Modification date and timeDate and time the service information was modified
Alert Policy NameName of the alert policy
NamespaceMetric namespace
Indicator NameIndicator name
Evaluation scopeTime range for alert evaluation
unitUnit of indicator data
Evaluation countAlert policy evaluation count
Number of violationsNumber of alert policy violations
StatisticsMethod of calculating metric data during the evaluation period
evaluation intervalEvaluation interval: evaluation range (unit) × number of evaluations
ConditionAlert state change condition based on the configured condition operator and threshold
Alert levelAlert level when an alert occurs
Target metric information areaDescription of the alert policy target metric, resource ID, and resource name
Table. Alert Policy Details – Details Tab Items

Notification

On the Alert Policy List page, you can view the notification recipients of the selected alert policy.

CategoryDetailed description
Notification recipient listUser ID, creation date and time, last login, status information
  • More button to click to change the notification status (enabled/disabled) for the user or delete the user
DeleteDelete all selected users from the notification recipient list
  • Enabled when you check the users to delete from the notification recipient list
MoreChange the notification status (enable/disable) for the selected user in the notification recipient list
  • When you check the user whose status you want to change in the notification recipient list, it becomes enabled
Add notification recipientAdd new notification recipient possible
  • Add Notification Recipient Select users to add in the popup window
Table. Alarm Policy Details - Notification Tab Items
Reference
  • Only users with a login history (users who have registered an email or mobile phone number) can be added as notification recipients.
  • You can add up to 100 notification recipients.
  • If there is no user to add, you can create a user on the IAM service’s User Creation page. For detailed information on creating users, see Create User.
  • The notification delivery method (E-mail or SMS) can be changed on the Notification Settings page after selecting the notification target as Service > Alert. For more details on notification settings, see Check Notification Settings.
Reference
You cannot add notification recipients to alarm policies associated with an Auto-Scaling Group.

Alert History

Alarm Policy List page lets you view the alarm status change history of the selected alarm policy.

CategoryDetailed description
Alert History ListAlarm status change timestamp, change status classification information, alarm description
  • Click View Details to view the detailed information of the alarm history and the source code in JSON format
View DetailsYou can view detailed alarm history information and the source code in JSON format
  • Enabled only when one alarm is selected from the alarm history list to view its details
Table. Alert Policy Details - Alert History Tab Items

tag

Alert Policy List page lets you view the tag information of the selected alert policy, and you can add, modify, or delete it.

CategoryDetailed description
Tag listTag’s Key and Value information
Edit tagYou can modify, delete, or add new tags to existing tag information
  • Up to 50 tags can be added per resource
  • When adding a tag, entering a Key and Value allows you to select from the list of previously created tag Keys and Values
Table. Alert Policy Details - Tag Tab Items

Job History

You can view the operation history of the selected alert policy on the Alert Policy List page.

CategoryDetailed description
Task History ListResource Change History
  • You can view task details, task date and time, resource type, resource name, task result, and operator information
    • Click the Settings button to modify information fields
  • Filtering is possible using Period Selection, User Time Zone, entering operator information, and Advanced Search
  • Click a task entry in the Task History List to navigate to the Task Activity Details page for that task
Table. Alert Policy Details - Work History Tab Items

Modify Alert Policy

You can modify the target metrics and policy settings of the alert policy. To modify the alert policy, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. You will be taken to the Service Home page.
  2. On the Service Home page, click the Alert > Alert Policy menu. It navigates to the Alert Policy List page.
  3. On the Alert Policy List page, click the alert policy name to view detailed information. You will be taken to the Alert Policy Details page.
  4. On the Detail Information tab of the Alert Policy Details page, click the Edit button of Metric Information. The Edit Metric Information popup opens.
  5. After modifying the metric information and policy settings, click the Confirm button. A popup notifying the metric modification will open.
  6. Click the Confirm button. The alert policy update is complete.
Reference
Alarm policies associated with an Auto-Scaling Group can be modified through the Auto-Scaling Group.

Disable Alert Policy

You can disable the alert policy to stop sending notifications when the alert status changes. Even if the alert policy is disabled, alert evaluation continues, and alert history accumulates as the alert status changes. However, notifications are not sent.

If you want to block receiving notifications for a specific period, you can disable the corresponding alert policy.

To disable the alert policy, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. You will be taken to the Service Home page.
  2. On the Service Home page, click the Alert > Alert Policy menu. You will be taken to the Alert Policy List page.
  3. On the Alert Policy Details page, click the Disable button. The Alert Policy Deactivation Notification popup opens.
  4. Click the Confirm button. Check the status of the alert policy.
Reference
Alert policies associated with an Auto-Scaling Group cannot be enabled or disabled.

Activate Alert Policy

You can enable the alert policy to resume sending notifications when the alert status changes. To enable the alert policy, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. You will be taken to the Service Home page.
  2. On the Service Home page, click the Alert > Alert Policy menu. You will be taken to the Alert Policy List page.
  3. On the Alert Policy Details page, click the Enable button. The Alert Policy Activation Notification popup window opens.
  4. Click the Confirm button. Check the status of the alert policy.
Reference
Alarm policies associated with an Auto-Scaling Group cannot be enabled or disabled.

Delete Alert Policy

You can delete unused alert policies. To delete an alert policy, follow these steps.

  1. All Services > Management > ServiceWatch menu, click it. You will be taken to the Service Home page.
  2. On the Service Home page, click the Alert > Alert Policy menu. You will be taken to the Alert Policy List page.
  3. On the Alert Policy List page, select the checkbox of the alert policy you want to delete, then click the Delete button. A popup notifying the alert policy deletion will appear.
    • You can delete multiple alert policies at once.
    • You can also delete individually by clicking the Delete button at the far right of each alert policy, or by clicking the Delete Alert Policy button on the corresponding Alert Policy Details page.
  4. Click the Confirm button. The alert policy will be deleted.
Reference
Alarm policies associated with an Auto-Scaling Group can be deleted through the Auto-Scaling Group.
Reference
Deleting an alarm policy can take several tens of minutes, depending on its scale.

2.3 - indicator

Users can monitor metrics of service resources in the Samsung Cloud Platform Console and use them for management.

Check Indicators

You can view the metrics available in ServiceWatch. To check the indicator, follow these steps.

  1. All Services > Management > ServiceWatch menu, click it. 1. Go to the Service Home page.
  2. On the Service Home page, click the Metrics menu. 2. Go to the Indicator page.
  3. Check the metrics in the metric list on the Metrics page.
CategoryDetailed description
Indicator Comparison ModeSelect the method for comparing indicators
  • Indicator Comparison: Select multiple indicators and resources to compare within a specific date or period
  • Date Comparison: Select a single indicator and resource to compare for a specific date or period
  • Only one indicator can be selected
Indicator classificationDisplay the metrics that can be monitored in ServiceWatch, filtered and categorized as All or Key Metrics, in the metric list
Indicator List AreaList of metrics that can be monitored in ServiceWatch
  • Click the + button in front of the namespace or dimension to view the sub-level list
  • Select a metric to monitor
  • If the metric is associated with a namespace, Service Dashboard is displayed
    • Click Service Dashboard to navigate to the detailed page of that dashboard
Search filter areaAfter setting the search items to filter, click the Apply Filter button to filter the metric list
  • Namespace-Dimension Name: Search based on the sub-dimension names of the selected namespace
  • Metric Name: Enter the exact metric name to search
  • Resource Name: Enter the exact resource name to search
  • Resource ID: Enter the exact resource ID to search
  • Keyword: Search based on the selected top-level category and the entered keyword
    • Proceed with item-specific searches excluding metric name, resource name, resource ID, and tag key
  • Tag Key: Search using the selected tag key
Selected indicatorDisplay monitoring information for the selected metric from the metric list
Table. Indicator list items

Manage Indicator Charts

You can add the metric monitoring result chart as a widget or manage the data.

Add as widget

You can add the selected metric as a widget to the dashboard.

information
You can add it as a widget only when you select the Metric Comparison mode.

To add a metric as a widget, follow these steps.

  1. All Services > Management > ServiceWatch Click the menu. 1. Go to the Service Home page.

  2. On the Service Home page, click the Metrics menu. 2. Navigate to the Indicator page.

  3. Select the metric to monitor from the metric list on the Metric page. 3. The monitoring chart for the selected metric is displayed in the Selected Metric area at the bottom.

  4. After configuring the table area in the monitoring chart of the Selected metric region, click the More > Add widget button. 4. Add Widget The popup window opens.

  5. After selecting the method to add the widget, enter the required information. 5. The required information varies depending on the addition method.

    Category
    Required status
    Detailed description
    Replication MethodRequiredAfter duplicating the widget, select the dashboard to add it to
    • Existing Dashboard: Add the widget to the existing dashboard
    • New Dashboard: Create a new dashboard and add the widget
    Select DashboardRequiredSelect the dashboard to which the duplicated widget will be added among the existing dashboards
    • Displayed when the duplication method is selected as Existing Dashboard
    Dashboard nameRequiredEnter the name of the new dashboard
    • Displayed when selecting the duplication method as New Dashboard
    • Enter using English letters, numbers, and special characters (-_) within 3 ~ 40 characters
    Widget nameRequiredWhen adding a widget to the dashboard, enter
    • English letters, numbers, special characters(-_.\
    Table. Widget additional items

  6. When you have finished entering the required information, click the Complete button. 6. A popup window notifying the addition of a widget opens.

  7. Click the Confirm button on the popup window. 7. A widget will be added to the dashboard.

Share monitoring chart URL

You can download monitoring chart information as a file. To download the monitoring chart information, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. 1. Navigate to the Service Home page.
  2. On the Service Home page, click the Metrics menu. 2. Go to the Indicator page.
  3. Select the metric to monitor from the metric list on the Metrics page. 3. The monitoring chart for the selected metric is displayed in the Selected Metric area at the bottom.
  4. After setting the table area in the monitoring chart of the Selected metric region, click the More > URL Share button. 4. URL sharing A popup window opens.
  5. In the URL Share popup, click the Copy URL button. 5. The generated URL is copied.
    • Information within the monitoring chart is provided as metadata links.

Download Monitoring Chart File

You can download monitoring chart information as a file. To download the monitoring chart information, follow these steps.

  1. All Services > Management > ServiceWatch menu, click it. 1. Go to the Service Home page.
  2. On the Service Home page, click the Metrics menu. 2. Navigate to the Indicator page.
  3. Select the metric to monitor from the metric list on the Metric page. 3. The monitoring chart for the selected metric is displayed in the Selected Metric area at the bottom.
  4. In the monitoring chart of the selected metric area, set the table region, then click the More > File Download button. 4. File Download popup window opens.
  5. After selecting the file download method, click the Confirm button. 5. The download will start.
    • The download method can be selected simultaneously.
      CategoryDetailed description
      CSVConvert chart metrics and monitoring data to an Excel (*.csv) file and download
      PNGConvert the chart to an image (*.png) file and download
      • Available only when the metric comparison mode is set to Metric Comparison
      • Up to 100 metric data items can be downloaded
      Table. Indicator monitoring file download item

Export to Object Storage

You can store monitoring chart data in Object Storage.

information

User permission is required to store in Object Storage.

  • User: {email}
  • Action: iam:CreatGroup
  • On resource: {SRN}
  • Context: no identity-based policy allows the action

To store monitoring chart data in Object Storage, follow these steps.

  1. All Services > Management > ServiceWatch click the menu. 1. Go to the Service Home page.
  2. On the Service Home page, click the Metrics menu. 2. Go to the Indicator page.
  3. Select the metric to monitor from the metric list on the Metric page. 3. The monitoring chart for the selected metric is displayed in the Selected Metric area at the bottom.
  4. In the monitoring chart of the Selected metric area, after setting the table region, click the More > Export to Object Storage button. 4. Object Storage Export The popup window opens.
  5. After selecting the bucket to store the data, click the Done button. 5. A popup window notifying data saving opens.
  6. Click the Confirm button in the popup window. 6. Data export is starting.
information
  • The limitations of metrics that can be exported to Object Stroage are as follows.
    • Number of indicators: up to 10
    • Query period: within 2 months (63 days)
  • If the query period exceeds 2 months (63 days), only data for up to 63 days will be stored.
Reference
  • If there is no Object Storage to store the metric data, create an Object Storage and then proceed.
  • Metric data is stored in the “MetricName-yyyymmddhhmmss.json” file format and can be accessed in the ~/servicewatch/metric path of the Object Storage bucket.

View monitoring chart source

You can view the source code of the monitoring chart.

information
You can view the source code only when you select the metric comparison mode as Metric Comparison.

To view the source code of the monitoring chart, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. 1. Go to the Service Home page.
  2. On the Service Home page, click the Metrics menu. 2. Go to the Indicator page.
  3. Please select the metric to monitor from the metric list on the Metric page. 3. The monitoring chart for the selected metric is displayed in the Selected Metric area at the bottom.
  4. After setting the table area in the monitoring chart of the selected metric region, click the More > View Source button. 4. View Widget Source A popup window opens.
    CategoryDetailed description
    Source informationDisplay the source code of the monitoring chart in JSON format
    Copy codeCopy the source code to the clipboard
    Table. Monitoring chart source view items

2.4 - Log

In ServiceWatch, you can set threshold criteria for the metrics you monitor, and when the specified conditions are met, you can create and manage log groups to generate alarm notifications.

Create Log Group

You can create a log group for the metric. To create a log group, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. You will be taken to the Service Home page.

  2. On the Service Home page, click the Log > Log Group menu. You will be taken to the Log Group List page.

  3. Log Group List page, click the Create Log Group button. You will be taken to the Create Log Group page.

  4. Enter the basic information and tag information required to create a log group.

    Category
    Whether required
    Detailed description
    Log group nameRequiredEnter the name of the log group to monitor in ServiceWatch
    • using English letters, numbers, and special characters (-_./#) within 3 ~ 512 characters
    Log retention policyRequiredSelect the retention period for monitored log data
    TagSelectAdd tag information
    • Up to 50 tags can be added per resource
    • When adding a tag, entering the Key and Value allows selection from the list of previously created tag Keys and Values
    Table. Log group creation items

  5. After reviewing the summary information, click the Create button. A popup notifying the creation of the log group will appear.

  6. Click the Confirm button. Log group creation is complete.

Check log group details

You can view and manage detailed information about log groups.

To view detailed information about the log group, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. You will be taken to the Service Home page.
  2. On the Service Home page, click the Log > Log Group menu. You will be taken to the Log Group List page.
  3. On the Log Group List page, click the log group name to view detailed information. You will be taken to the Log Group Details page.
    CategoryDetailed description
    Log group statusLog group status
    • Active: The log group is in an active state
    • Inactive: The log group is in an inactive state
    Export Log GroupStore log group log data in Object Storage
    Delete log groupDelete the corresponding log group
    Information Classification TabInformation tabs for log groups
    • Details, Log Streams, Tags, Activity History
    • Click each tab to view the corresponding information
    Table. Log Group Details
    Reference
    On the Log Group List page, click the More > Export Log Group button for the log group you want to store in Object Storage to export the data.
Reference

When sorting log group names in the log group list, follow the sorting rules below.

  1. Whitespace and control characters
  2. Some special characters ( !"#$%&()*+,-./ )
  3. Numbers (0–9)
  4. Some special characters ( ; < = > ? @ )
  5. English (A–Z, a–z, case-insensitive)
  6. Remaining special characters ([\]^_`)
  7. Other characters

Detailed Information

Log Group List page allows you to view the basic information and details of the selected log group.

CategoryDetailed description
ServiceService name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In ServiceWatch, it refers to the SRN of the resource type
Resource NameResource name
  • In ServiceWatch, it refers to the name of the log group
Resource IDUnique resource ID in the service
ConstructorUser who created the service
Creation date and timeService creation date and time
EditorUser who edited the service information
Modification date and timeDate and time the service information was modified
Log group nameName of the log group
Log retention policyRetention period of log data
  • Edit Click the button to change the retention period
Log dataTotal stored log data size (bytes)
Table. Log Group Details – Details Tab Items
Reference
Log data is the total stored log data (bytes). It may take time for the log aggregation capacity to be reflected.

Log Stream

Log Group List page allows you to view the log streams of the selected log group.

CategoryDetailed description
View all streamsDetailed information for all log streams in the log stream list can be viewed
Create log streamCreate a new log stream
Log stream listLog stream name and log modification timestamp
  • Delete button can be clicked to delete the log stream
  • After checking the log streams to delete, click the More > Delete button at the top of the list to delete them simultaneously
Table. Log Group Details - Log Stream Tab Items

log pattern

Log Group List page allows you to view the log pattern of the selected log group.

CategoryDetailed description
Log pattern listLog pattern name, pattern, log pattern namespace, metric name, alert policy name information
  • Clicking the log pattern name or alert policy name navigates to the detail page of that item
  • Clicking the metric name navigates to the metric page that includes that metric name in the search query
  • Clicking the alert policy name navigates to the detail page of that alert policy
  • More button can be clicked to perform additional actions
    • Edit, Delete: modify or delete the log pattern
    • Create Alert Policy: navigate to the alert policy creation page
DeleteDelete all selected log patterns from the log pattern list
  • Activates when a log pattern is checked in the log pattern list
Generate log patternCreate a new log pattern
Table. Log Group Details - Log Pattern Tab Items

tag

On the Log Group List page, you can view the tag information of the selected log group and add, modify, or delete it.

CategoryDetailed description
Tag listTag’s Key and Value information
Edit tagYou can modify, delete, or add new tags to existing tag information
  • Up to 50 tags can be added per resource
  • When adding a tag, entering the Key and Value allows you to select from the list of previously created tag Keys and Values
Table. Log Group Details - Tag Tab Items

Job History

Log Group List page lets you view the operation history of the selected log group.

CategoryDetailed description
Task History ListResource Change History
  • You can view task details, task date/time, resource type, resource name, task result, and operator information
    • Settings button can be clicked to modify information fields
  • Filtering is possible using Period Selection, User Time Zone, entering operator information, and Detailed Search
  • Click a task entry in the Task History List to navigate to the Task Activity Details page for that task
Table. Log Group Details - Work History Tab Items

Managing Log Streams

You can create and manage log streams.

Create Log Stream

You can create a new log stream in a log group. To create a Hog stream, follow the steps below.

  1. Click the All Services > Management > ServiceWatch menu. You will be taken to the Service Home page.
  2. On the Service Home page, click the Log > Log Group menu. You will be taken to the Log Group List page.
  3. On the Log Group List page, click the log group name for which you want to create a log stream. You will be taken to the Log Group Details page.
  4. Log Group Details page, click the Log Stream tab. The Log Stream list is displayed.
  5. Click the Create Log Stream button. The Create Log Stream popup opens.
  6. Enter the Log stream name, then click the Create button. Log stream creation is completed.
    • Enter the name using English letters and numbers, within 3~512 characters.

Check detailed log stream information

You can view and manage detailed information about log streams. To view detailed information about the log stream, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. You will be taken to the Service Home page.
  2. On the Service Home page, click the Log > Log Group menu. You will be taken to the Log Group List page.
  3. Click the log group name on the Log Group List page to view detailed information. You will be taken to the Log Group Details page.
  4. On the Log Group Details page, click the Log Stream tab. The Log Stream list is displayed.
  5. Click the log stream name in the Log Stream list to view its details. You will be taken to the Log Stream Details page.
    CategoryDetailed description
    Excel downloadLog stream history can be downloaded as an Excel file
    Timestamp listMessage list by timestamp
    • Period selection, User time zone, can filter using message input
    Table. Log group details - Log stream detail items
    Reference
    When you click the View All Log Streams button at the top of the log stream list, you will be taken to the All Log Stream Details page.

Delete Log Stream

You can delete unused log streams. To delete a log stream, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. You will be taken to the Service Home page.
  2. On the Service Home page, click the Log > Log Group menu. You will be taken to the Log Group List page.
  3. On the Log Group List page, click the log group name whose log stream you want to delete. You will be taken to the Log Group Details page.
  4. Log Group Details page, click the Log Stream tab. The log stream list will be displayed.
  5. Select the checkbox of the log stream to delete in the log stream list, then click the More > Delete button. A popup notifying the log stream deletion will open.
    • You can delete multiple log streams simultaneously.
    • You can also delete each individually by clicking the Delete button at the right end of each log stream.
  6. Click the Confirm button. The log stream will be deleted.

Managing Log Patterns

Create Log Pattern

To create a log pattern, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. You will be taken to the Service Home page.

  2. On the Service Home page, click the Log > Log Group menu. You will be taken to the Log Group List page.

  3. On the Log Group List page, click the log group name for which you want to create a log pattern. You will be taken to the Log Group Details page.

  4. Log Group Details page, click the Log Pattern tab. The log pattern list will be displayed.

  5. Click the Create Log Pattern button. You will be taken to the Create Log Pattern page.

  6. Set the basic information and metric information required to create a log group.

    • In the Basic Information area, enter and select the basic information for the log pattern.
      Category
      Required
      Detailed description
      Log pattern nameRequiredEnter the name of the log pattern
      • using English letters, numbers, and special characters (-_./#) within 3 ~ 512 characters
      Pattern formatRequiredSelect a pattern format or enter manually
      • Pattern format: Choose one of the string pattern, space-delimited pattern, or JSON format pattern provided as pattern formats
      • Direct input: After selecting one of the string pattern, space-delimited pattern, or JSON format pattern, enter a value between 1 ~ 1,024
      Pattern testSelectEnter or select log data to verify using a pattern
      • Direct Input: Enter the log data to be used directly into the Log Event Message
        • Separate log events using line breaks
        • Up to 50 log events can be entered
        • Each log event can be entered within 1 ~ 1,024 bytes
      • Log Data Selection: Choose the log data to use
        • When selecting log data, the corresponding log data is displayed in the Log Event Message
      • Pattern Test: Conduct a test on the log event message
        • If the test succeeds, the test result is displayed at the bottom
      Table. Log Pattern Creation - Basic Information Items
    • Enter and select metric information in the Metric Information area.
      Category
      Required status
      Detailed description
      namespaceRequiredSelect a namespace for the log pattern
      • If there is no namespace for the log pattern, Create New to create one
      • Namespace Name: When creating a new namespace, use English letters, numbers, spaces, and special characters(-_\/#) to enter between 3 ~ 128 characters
      Indicator NameRequiredEnter the name of the indicator
      • using English letters, numbers, and special characters(_) within 3 ~ 128 characters
      indicator valueRequiredEnter the indicator value
      • a number greater than or equal to 0 or $indetifier
      defaultSelectIf you use the default value, enter
      • 0 or greater float value
      • When using the default, dimension cannot be used
      unitRequiredSelect indicator unit
      dimensionSelectionSet the dimension of metrics generated by log patterns
      • Log pattern format is available only when it is a space-delimited pattern or a JSON format pattern
      • Default value cannot be used when entered
      • If Use is checked, you can add custom dimension fields
        • After clicking the Add button, add by entering Field name and Field value
        • You can add up to a maximum of 3
      Table. Log pattern generation - metric information items
  7. After reviewing the summary information, click the Create button. A popup indicating log pattern creation will appear.

  8. Confirm click the button. Log pattern generation is complete.

Check detailed log pattern information

To view detailed information about the log pattern, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. You will be taken to the Service Home page.
  2. On the Service Home page, click the Log > Log Group menu. You will be taken to the Log Group List page.
  3. Click the log group name to view detailed information on the Log Group List page. You will be taken to the Log Group Details page.
  4. Log Group Details page, click the Log Pattern tab. The log pattern list will be displayed.
  5. Log pattern Click the log pattern name in the list to view its details. Log pattern details page will open.
    CategoryDetailed description
    Create alert policyAlert policy creation available
    • When the button is clicked, navigate to the alert policy creation page
    Delete log patternDelete the log pattern currently being examined
    Log pattern nameLog pattern name
    constructorUser who created the log pattern
    Creation date and timeLog pattern creation timestamp
    EditorUser who modified the log pattern information
    Modification dateDate and time the log pattern information was modified
    PatternPattern format
    Indicator InformationMetric information of the pattern group
    • Namespace name, metric name, metric value, default value, unit, alarm policy name, dimension name
    • Edit button allows modification of metric value, default value, unit information
    Table. Log pattern detailed items

Delete log pattern

To delete a log pattern, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. You will be taken to the Service Home page.
  2. On the Service Home page, click the Log > Log Group menu. You will be taken to the Log Group List page.
  3. On the Log Group List page, click the log group name whose log pattern you want to delete. You will be taken to the Log Group Details page.
  4. On the Log Group Details page, click the Log Pattern tab. The log pattern list will be displayed.
  5. After selecting the checkbox of the log pattern to delete in the log pattern list, click the Delete button. A popup notifying the log pattern deletion will open.
    • You can delete multiple log patterns simultaneously.
    • You can also delete individually by clicking the More > Delete button at the far right of each log pattern, or by clicking the Delete Log Pattern button on the log pattern’s detail page.
  6. Click the Confirm button. The log pattern will be deleted.

Export Log Group

Log group data can be stored in Object Storage. To store log group data in Object Storage, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. You will be taken to the Service Home page.

  2. On the Service Home page, click the Log > Log Group Export menu. You will be taken to the Log Group Export List page.

  3. Log Group Export List page, click the Log Group Export button. You will be taken to the Log Group Export page.

    Category
    Required
    Detailed description
    Select log groupRequiredSelect the log group to store in Object Storage
    • If the log group contains log streams, you can click the Select button to choose the log stream to store
    • If no log group is selected, the entire data of the log group will be stored
    Select periodSelectSelect the user time zone and data storage interval
    • In the Time Settings area, you can select the desired interval or click the Enter Manually button to set the start and end date and time
    storage bucketRequiredSelect the bucket to store data
    • Up to 50 tags can be added per resource
    • When adding a tag, entering the Key and Value allows you to select from the list of existing tag Keys and Values
    Table. Log group export items

  4. After selecting the bucket to store the data, click the Complete button. A popup notifying that the data has been saved will open.

  5. In the popup window, click the Confirm button. Data export will begin.

    • You can view the progress on the Log Group Export List page.
Reference
  • If there is no Object Storage to store the log group data, create an Object Storage and then proceed.
  • Exporting log group data may take tens of minutes or more, depending on its size.
  • If there is an ongoing log group export task within the Account, you must first complete the ongoing task before proceeding with the export.
  • On the Log Group Export List page, you can cancel an export operation for a log group that is in progress by clicking the More > Cancel Log Group Export button.

Delete Log Group

You can delete unused log groups.

Caution
  • Log Group Export does not delete files stored in Object Storage. However, the Log Group Export history is deleted together.
  • If you delete a log group while log group export is in progress, the export operation will not complete successfully.

To delete a log group, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. You will be taken to the Service Home page.
  2. On the Service Home page, click the Log > Log Group menu. You will be taken to the Log Group List page.
  3. On the Log Group List page, select the checkbox of the log group you want to delete, then click the Delete button. A popup notifying the log group deletion will appear.
    • You can delete multiple log groups simultaneously.
    • You can delete individually by clicking the Delete button at the far right of each log group, or by clicking the Delete Log Group button on the Log Group Details page.
  4. Click the Confirm button. The log group will be deleted.

2.5 - Event

You can view and handle events generated by the Samsung Cloud Platform service in ServiceWatch.

Create Event Rule

You can create an event rule to receive notifications when an event occurs. To create an event rule, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. You will be taken to the Service Home page.

  2. On the Service Home page, click the Event Rules menu. You will be taken to the Event Rules List page.

  3. Event Rule List page, click the Create Event Rule button. You will be taken to the Create Event Rule page.

  4. Enter the name and description of the event rule in the Basic Information Input area.

  5. Set the required information in the Event Pattern Configuration area. The configured event pattern is entered in Event Pattern Configuration Status as JSON code.

    Category
    Required status
    Detailed description
    Event sourceRequiredSelect the service name of the event you want to receive in ServiceWatch
    Event typeRequiredSelect the event type of the event source to use in the event rule
    • Classify the same as the resource type
    Apply EventRequiredSelect events to apply the event pattern from events generated by the event type
    • All events: Apply all events generated by the event type
    • Individual events: Choose events from those generated by the event type to set as the event pattern
    Applied resourceRequiredSelect the resource to apply the event pattern
    • All resources: Set the event pattern for events that occur in all resources
    • Individual resource: Set the event pattern for the specific event that occurs in a particular resource
      • When an individual resource is selected, display the event resource selection area
      • Add resource button can be clicked to select resources
      • Added resources can be removed by selecting the resource in the resource list and clicking the Delete button
    Event Pattern Configuration Status-Convert and display in JSON code format according to the event pattern settings
    • Changing the event pattern settings will reset
    • Copy code item can be clicked to copy the source code
    Table. Event pattern configuration items

  6. In the Notification Settings area, select the users who will receive notifications when an event occurs.

    • Only users with a login history (users who have registered an email or mobile phone number) can be added as notification recipients.
    • You can add up to 100 notification recipients.
Reference
  • If there is no user to add, you can create a user on the User Creation page of the IAM service. For more details on creating users, see Create User.
  • The notification delivery method (E-mail or SMS) can be changed on the Notification Settings page after selecting the notification target as Service > Event Rule. For detailed information about notification settings, refer to 알림 설정 확인하기.
  1. Add tag information in the Additional Information Input area.
  2. After checking the summary information, click the Create button. A popup notifying the creation of an event rule will open.
  3. Click the Confirm button. Event rule creation is complete.

Check detailed event rule information

You can view and manage detailed information about event rules. Follow the steps below to view detailed information about the event rules.

  1. Click the All Services > Management > ServiceWatch menu. You will be taken to the Service Home page.
  2. On the Service Home page, click the Event Rules menu. You will be taken to the Event Rules List page.
  3. Event Rules List page, click the event name to view detailed information. You will be taken to the Event Rules Detail page.
    CategoryDetailed description
    Event rule statusEvent rule status
    • Active: The event rule is in an active state
    • Inactive: The event rule is in an inactive state
    • You can change it by clicking the Activate or Deactivate button
    Delete event ruleDelete the corresponding event rule
    Information Category TabInformation tabs for alert policies
    • Details, notifications, tags, activity history
    • Click each tab to view the corresponding information.
    Table. Event rule details

Detailed Information

Event Rule List page lets you view the basic information and event rule details of the selected rule.

CategoryDetailed description
ServiceService name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In ServiceWatch, it refers to the SRN of the resource type
Resource nameResource name
  • In ServiceWatch, it refers to the name of the event rule
Resource IDUnique resource ID in the service
constructorUser who created the service
Creation date and timeService creation date and time
EditorUser who edited the service information
Modification date and timeDate and time the service information was modified
Event rule nameEvent rule name
Event Pattern Configuration StatusDisplay event pattern settings in JSON code format
  • Edit button can be clicked to modify the event pattern
  • Copy Code item can be clicked to copy the source code
descriptionDescription of event rules
  • Click the Edit button to edit the description
Table. Alert Policy Details – Details Tab Items

Notification

Event Rule List page allows you to view the notification recipients of the selected event rule.

CategoryDetailed description
Notification recipient listUser ID, creation date and time, last login, status information
  • Click the More button to change the notification status (enabled/disabled) for the user or delete the user
DeleteDelete all selected users from the notification recipient list
  • Enabled when you check the users to delete from the notification recipient list
MoreChange the notification status (enable/disable) for the selected user in the notification recipient list
  • When you check the user whose status you want to change in the notification recipient list, it becomes enabled
Add notification recipientAbility to add new notification recipients
  • Add Notification Recipient Select users to add in the popup window
Table. Event rule details - Notification tab items
Reference
  • Only users with a login history (users who have registered an email or mobile phone number) can be added as notification recipients.
  • You can add up to 100 notification recipients.
  • If there is no user to add, you can create a user on the IAM service’s User Creation page. For detailed information on creating users, refer to Create User.
  • The notification reception method (E-mail or SMS) can be changed on the Notification Settings page after selecting the notification target as Service > Event Rule. For detailed information about notification settings, refer to 알림 설정 확인하기.

tag

Event Rules page allows you to view the tag information of the selected event rule, and add, modify, or delete it.

CategoryDetailed description
Tag listTag’s Key and Value information
Edit tagYou can modify or delete existing tag information, or add new tags
  • Up to 50 tags can be added per resource
  • When adding a tag, entering the Key and Value allows you to select from the list of previously created tag Keys and Values
Table. Event Rule Details – Tag Tab Items

Job History

You can view the operation history of the event rule selected on the Alert Policy List page.

CategoryDetailed description
Task History ListResource Change History
  • You can view the task details, task date and time, resource type, resource name, task result, and operator information
    • Click the Settings button to modify information items
  • Filtering is possible using Period Selection, User Time Zone, entering operator information, and Detailed Search
  • Clicking a task entry in the Task History List navigates to the Task Activity Details page for that task
Table. Event Rule Details - Work History Tab Items

Modify event pattern

You can modify the event pattern. To modify the event pattern, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. You will be taken to the Service Home page.
  2. On the Service Home page, click the Event Rules menu. You will be taken to the Event Rules List page.
  3. Event Rule List page, click the event name to edit the event pattern. You will be taken to the Event Rule Details page.
  4. Click the Edit button in the Event Pattern Configuration Status on the Event Rule Details page. The Edit Event Pattern popup opens.
  5. After modifying the event pattern settings, click the Confirm button. A popup notifying the event pattern modification will appear.
  6. Click the Confirm button. The event pattern modification is complete.

Delete Event Rule

You can delete unused event rules. To delete an event rule, follow these steps.

  1. Click the All Services > Management > ServiceWatch menu. You will be taken to the Service Home page.
  2. On the Service Home page, click the Event Rules menu. You will be taken to the Event Rules List page.
  3. On the Event Rule List page, select the checkbox of the event rule you want to delete, then click the Delete button. A popup notifying the deletion of the event rule will appear.
    • You can delete multiple event rules simultaneously.
    • You can also delete individually by clicking the More > Delete button at the far right of each alert policy, or by clicking the Delete Event Rule button on the Event Rule Details page.
  4. Click the Confirm button. The event rule will be deleted.

2.6 - Using ServiceWatch Agent

Users can install the ServiceWatch Agent on Virtual Server/GPU Server/Bare Metal Server, etc., to collect custom metrics and logs.

Reference
Collecting custom metrics/logs via the ServiceWatch Agent is currently available only on Samsung Cloud Platform For Enterprise. It will be offered in other offerings in the future.
Caution
Metric collection through the ServiceWatch Agent is classified as custom metrics and, unlike the default metrics collected from each service, incurs charges, so you must be careful not to configure unnecessary metric collection. Ensure that only the metrics that need to be collected are collected.

ServiceWatch Agent

The agents that need to be installed on the server to collect custom metrics and logs for ServiceWatch can be divided into two main types. It is a Prometheus Exporter and Open Telemetry Collector.

CategoryDetailed description
Prometheus ExporterProvide metrics of a specific application or service in a format that Prometheus can scrape
  • To collect OS metrics from servers, you can use Node Exporter for Linux servers and Windows Exporter for Windows servers, depending on the OS type.
    • Target
      • Virtual Server
      • GPU Server
      • Bare Metal Server
      • Multi-node GPU Cluster > GPU Node
  • You can use the DCGM (NVIDIA Data Center GPU Manager) Exporter for GPU metrics.
    • Target
      • GPU Server
      • Multi-node GPU Cluster > GPU Node
Open Telemetry CollectorActs as a centralized collector that gathers telemetry data such as metrics and logs from distributed systems, processes (filtering, sampling, etc.) it, and exports it to various backends (e.g., Prometheus, Jaeger, Elasticsearch, etc.)
  • Exports data to the ServiceWatch Gateway so that ServiceWatch can collect metric and log data.
  • This guide provides instructions on how to use the OpenTelemetry Collector provided by ServiceWatch.
Table. Explanation of Prometheus Exporter and Open Telemetry Collector
Reference

To link a server’s log files to ServiceWatch via the ServiceWatch Agent, you must first create a log group and a log stream within that log group.

  • For detailed information on creating log groups and log streams, refer to the 로그.

Pre-configuration for ServiceWatch Agent

You need to add a Security Group and firewall rules to enable communication between the ServiceWatch Agent and ServiceWatch.

Reference
Bare Metal Server does not support Security Groups.
  1. Add Security Group rule

    • To transmit the data collected by ServiceWatch from the ServiceWatch Agent installed on Virtual Server/GPU Server to ServiceWatch, you need to add a rule to the Security Group as follows.
      DirectiontypePortTarget address
      OutboundCustom TCP443ServiceWatch OpenAPI Endpoint IP Address
      Table. Security Group rules for ServiceWatch Agent communication
  2. Add firewall rule

    • If you configure the VPC’s Internet Gateway to use a firewall, you must add firewall rules as shown below.
      DirectiontypePortOperationSource addressDestination address
      OutboundTCP443AllowWhen creating a Virtual Server, the assigned Private IP address. The Virtual Server Private IP address can be found in Check Virtual Server Details.ServiceWatch OpenAPI Endpoint IP Address
      Table. Internet Gateway firewall rules for ServiceWatch Agent communication

ServiceWatch OpenAPI Endpoint IP address

The Endpoint IP address required for the ServiceWatch Agent to send the data collected to ServiceWatch is as follows.

OfferingRegionURLIP address
For Enterprisekr-west1https://servicewatch.kr-west1.e.samsungsdscloud.com112.107.105.24
For Enterprisekr-east1https://servicewatch.kr-east1.e.samsungsdscloud.com112.107.105.68
Table. ServiceWatch OpenAPI Endpoint Information

Open Telemetry Collector configuration for ServiceWatch

Install the OpenTelemetry Collector on the server following the steps below to collect ServiceWatch metrics and logs.

  1. Download the Agent file from the URL that provides the Agent file for ServiceWatch.
information
The file download link for installing the Agent for ServiceWatch can be found in ServiceWatch’s Service Home > Start Widget.
Also, you can verify it using ServiceWatch’s ShowAgentDownloadLink API. For more information, see the ServiceWatch API Reference.
Color mode
wget [ServiceWatch Agent file download URL]
wget [ServiceWatch Agent file download URL]
Code block. Command to download the Agent installation file for ServiceWatch
  1. The Open Telemetry Collector Agent file for ServiceWatch can be found as follows.
    • Extract the Agent file for ServiceWatch.
      Color mode
      unzip ServiceWatch_Agent.zip
      unzip ServiceWatch_Agent.zip
      Code block. Extract the Agent file for ServiceWatch
    • When using the ServiceWatch Agent on a Linux OS, you must grant execution permission as shown below.
      Color mode
      chmod +x agent/otelcontribcol_linux_amd64
      chmod +x agent/servicewatch-agent-manager-linux-amd64
      chmod +x agent/otelcontribcol_linux_amd64
      chmod +x agent/servicewatch-agent-manager-linux-amd64
      Code block. Grant execution permission to the Agent file for ServiceWatch
      CategoryDetailed description
      examplesExample configuration file folder. Each folder contains agent.json, log.json, metric.json example files
      • os-metrics-min-examples: Minimal metric configuration example using Node Exporter
      • os-metrics-all-examples: Example of memory/filesystem Collector metric configuration using Node Exporter
      • gpu-metrics-min-examples: Minimal metric configuration example using DCGM Exporter
      • gpu-metrics-all-examples: Example of major metric configuration using DCGM Exporter
      otelcontribcol_linux_amd64Open Telemetry Collector for Linux for ServiceWatch
      otelcontribcol_windows_amd64.exeOpen Telemetry Collector for Windows for ServiceWatch
      servicewatch-agent-manager-linux-amd64ServiceWatch Agent Manager for Linux
      servicewatch-agent-manager-windows-amd64.exeServiceWatch Agent Manager for Windows
      Table. Agent file configuration for ServiceWatch
Reference
ServiceWatch Agent Manager is a tool that integrates with ServiceWatch to assist in configuring the OpenTelemetry Collector for efficiently transmitting custom metrics and logs. Through this, various custom metrics and log data can be delivered to ServiceWatch.
  1. Define the Agent configuration file in ServiceWatch Agent Manager for the ServiceWatch Open Telemetry Collector.

    CategoryDetailed description
    namespaceCustom namespace for custom metrics
    • A namespace is a logical separation used to distinguish and group metrics, designated as a custom metric for separating custom metrics
    • A namespace must be 3 to 128 characters long, may include letters, numbers, spaces, and special characters (-_/), and must start with a letter.
    accessKeyIAM authentication key Access Key
    accessSecretIAM authentication key Secret Key
    resourceIdResource ID of the server on Samsung Cloud Platform
    • Example: Resource ID of a Virtual Server
    openApiEndpointServiceWatch OpenAPI endpoint per region/offering
    • Example: https://servicewatch.region.offering.samsungsdscloud.com
    • region and offering information can be found in the Samsung Cloud Platform Console access URL
    telemetryPortServiceWatch Agent’s Telemetry Port
    • is typically used on port 8888. If port 8888 is in use, it needs to be changed
    Table. agent.json configuration file entries
    Color mode
    {
       "namespace": "swagent-windows",     # Custom namespace for user-defined metrics
       "accessKey": "testKey",             # IAM authentication key Access Key
       "accessSecret": "testSecret",       # IAM authentication key Secret Key
       "resourceId": "resourceID",         # Resource ID on the server's Samsung Cloud Platform
       "openApiEndpoint": "https://servicewatch.kr-west1.e.samsungsdscloud.com",    # Region/Environment-specific ServiceWatch OpenAPI Endpoint
       "telemetryPort": 8889               # ServiceWatch Agent's Telemetry Port (usually uses port 8888. If port 8888 is in use, change it)
    }
    {
       "namespace": "swagent-windows",     # Custom namespace for user-defined metrics
       "accessKey": "testKey",             # IAM authentication key Access Key
       "accessSecret": "testSecret",       # IAM authentication key Secret Key
       "resourceId": "resourceID",         # Resource ID on the server's Samsung Cloud Platform
       "openApiEndpoint": "https://servicewatch.kr-west1.e.samsungsdscloud.com",    # Region/Environment-specific ServiceWatch OpenAPI Endpoint
       "telemetryPort": 8889               # ServiceWatch Agent's Telemetry Port (usually uses port 8888. If port 8888 is in use, change it)
    }
    Code block. Example of agent.json configuration

  2. Defines the metric configuration file for collecting metrics for ServiceWatch.

    • If you want to collect metrics through the Agent, set up metric.json.
      CategoryDetailed description
      prometheus > scrape_configs > targetsEndpoint of the metric collection target
      • For servers, because the Prometheus Exporter is installed on the same machine, set it to that endpoint
      • Example: localhost:9100
      prometheus > scrape_configs > jobNameSet the Job Name. Usually set it to the type of Prometheus Exporter used for metric collection
      • Example: node-exporter
      metricMetas > metricNameSet the name of the metric to be collected. The metric name must be 3 to 128 characters long, include letters, numbers, and special characters (_), and start with a letter.
      • Example: node_cpu_seconds_total
      metricMetas > dimensionsSet the label of the Collector, among those provided to identify the source of the Exporter’s metric data, for visualization in the Console. When visualizing the collected metrics in the Console, combine them according to the dimensions setting.
      • Example: For metrics like the Memory Collector of Node Exporter that do not provide a special label, set it to resource_id.
      • Example: The Filesystem Collector metrics of Node Exporter can have the mountpoint, which represents the path where the filesystem is mounted on the system, set as a dimension.
      metricMetas > unitMetric unit can be set
      • Example: Bytes, Count, etc.
      metricMetas > aggregationMethodMethod to aggregate based on specified dimensions(dimensions)
      • Example: select from SUM, MAX, MIN, COUNT
      metricMetas > descriptionKoKorean description of the metrics being collected
      metricMetas > descriptionEnEnglish description of the metrics being collected
      Table. metric.json configuration file entries
      Color mode
      {
         "prometheus": {
            "scrape_configs": {
               "targets": [
                  "localhost:9100" # Endpoint of the Prometheus Exporter installed on the server
               ],
               "jobName": "node-exporter" # Usually set to the name of the installed Exporter
            }
         },
         "metricMetas": [
            {
               "metricName": "node_memory_MemTotal_bytes",    # Set the metric name to be linked with ServiceWatch among the metrics collected from the Prometheus Exporter
               "dimensions": [
                  [
                     "resource_id"        # Set the label used for visualizing in the Console among the Collector's labels provided to identify the source of Node Exporter's metric data
                                          # If no specific label is provided, such as for the Memory-related metric, set it to **resource_id**.
                  ]
               ],
               "unit": "Bytes",           # unit of the collected metric data
               "aggregationMethod": "SUM",    # aggregation method
               "descriptionKo": "Total physical memory size of the server",    # Korean description of the metric
               "descriptionEn": "node memory total bytes"      # English description of the metric
            },
            {
               "metricName": "node_filesystem_size_bytes",    # Set the metric name to be linked with ServiceWatch among the metrics collected from the Prometheus Exporter
               "dimensions": [
                  [
                     "mountpoint"        # Set the label for visualizing in the Console among the Collector labels provided to identify the source of Node Exporter's metric data.
                                         # Set the dimension (dimensions) of the Filesystem-related metric to the mountpoint, which indicates the path where the filesystem is mounted on the system.
                  ]
               ],
               "unit": "Bytes"
               "aggregationMethod": "SUM"
               "descriptionKo": "node filesystem size bytes"
               "descriptionEn": "node filesystem size bytes"
            },
            {
               "metricName": "node_memory_MemAvailable_bytes"
               "dimensions": [
                  [
                     resource_id
                  ]
               ],
               "unit": "Bytes"
               "aggregationMethod": "SUM"
               "descriptionKo": "node memory available bytes"
               "descriptionEn": "node memory available bytes"
            },
            {
               "metricName": "node_filesystem_avail_bytes"
               "dimensions": [
                  [
                     mountpoint
                  ]
               ],
               "unit": "Bytes"
               "aggregationMethod": "SUM"
               "descriptionKo": "node filesystem available bytes"
               "descriptionEn": "node filesystem available bytes"
            }
         ]
      }
      {
         "prometheus": {
            "scrape_configs": {
               "targets": [
                  "localhost:9100" # Endpoint of the Prometheus Exporter installed on the server
               ],
               "jobName": "node-exporter" # Usually set to the name of the installed Exporter
            }
         },
         "metricMetas": [
            {
               "metricName": "node_memory_MemTotal_bytes",    # Set the metric name to be linked with ServiceWatch among the metrics collected from the Prometheus Exporter
               "dimensions": [
                  [
                     "resource_id"        # Set the label used for visualizing in the Console among the Collector's labels provided to identify the source of Node Exporter's metric data
                                          # If no specific label is provided, such as for the Memory-related metric, set it to **resource_id**.
                  ]
               ],
               "unit": "Bytes",           # unit of the collected metric data
               "aggregationMethod": "SUM",    # aggregation method
               "descriptionKo": "Total physical memory size of the server",    # Korean description of the metric
               "descriptionEn": "node memory total bytes"      # English description of the metric
            },
            {
               "metricName": "node_filesystem_size_bytes",    # Set the metric name to be linked with ServiceWatch among the metrics collected from the Prometheus Exporter
               "dimensions": [
                  [
                     "mountpoint"        # Set the label for visualizing in the Console among the Collector labels provided to identify the source of Node Exporter's metric data.
                                         # Set the dimension (dimensions) of the Filesystem-related metric to the mountpoint, which indicates the path where the filesystem is mounted on the system.
                  ]
               ],
               "unit": "Bytes"
               "aggregationMethod": "SUM"
               "descriptionKo": "node filesystem size bytes"
               "descriptionEn": "node filesystem size bytes"
            },
            {
               "metricName": "node_memory_MemAvailable_bytes"
               "dimensions": [
                  [
                     resource_id
                  ]
               ],
               "unit": "Bytes"
               "aggregationMethod": "SUM"
               "descriptionKo": "node memory available bytes"
               "descriptionEn": "node memory available bytes"
            },
            {
               "metricName": "node_filesystem_avail_bytes"
               "dimensions": [
                  [
                     mountpoint
                  ]
               ],
               "unit": "Bytes"
               "aggregationMethod": "SUM"
               "descriptionKo": "node filesystem available bytes"
               "descriptionEn": "node filesystem available bytes"
            }
         ]
      }
      Code block. metric.json configuration example
    • To display the resource name, set resource_name in commonLabels as shown below, and also set resource_name in metricMetas.dimensions; then ServiceWatch can retrieve the metric along with the resource name.
      Color mode
         "commonLabels": {
            "resource_name": "ResourceName" # Resource name visible in the User Console
         },
         "metricMetas": [
            {
               "metricName": "metric_name"
               "dimensions": [
                  [
                     "resource_id"
                     "resource_name"        # Add the resource_name set in commonLabels to the dimensions of each metric
      
                  ]
               ],
               "unit": "Bytes"
               "aggregationMethod": "SUM"
               "descriptionKo": "metric_name description"
               "descriptionEn": "metric_name description"
            },
         ...
         ]
         "commonLabels": {
            "resource_name": "ResourceName" # Resource name visible in the User Console
         },
         "metricMetas": [
            {
               "metricName": "metric_name"
               "dimensions": [
                  [
                     "resource_id"
                     "resource_name"        # Add the resource_name set in commonLabels to the dimensions of each metric
      
                  ]
               ],
               "unit": "Bytes"
               "aggregationMethod": "SUM"
               "descriptionKo": "metric_name description"
               "descriptionEn": "metric_name description"
            },
         ...
         ]
      Code block. metric.json - Resource name setting
  3. Defines the log configuration file for collecting logs for ServiceWatch.

    • If you want to collect logs, you must configure log.json.
      CategoryDetailed description
      fileLog > includeLocation of log files to collect
      fileLog > operatorsDefinition for parsing log messages to be collected
      fileLog > operators > regexExpress the log message format as a regular expression
      fileLog > operators > timestampThe format of the Time Stamp of log messages to be sent to ServiceWatch
      logMetas > log_group_valueLog group name created for sending logs to ServiceWatch
      logMetas > log_stream_valueLog stream name in ServiceWatch log group
      Table. log.json configuration file entries
      Color mode
      {
         "fileLog": {
            "include": [
               "/var/log/syslog",        # Log file to be collected by ServiceWatch
               /var/log/auth.log
            ],
            "operators": {
               "regex": "^(?P<timestamp>\\S+)\\s+(?P<hostname>\\S+)\\s+(?P<process>[^:]+):\\s+(?P<message>.*)$",    # Represent log file format with a regular expression
               "timestamp": {            # Set the format of the log message's Time Stamp
                  "layout_type": "gotime"
                  "layout": "2006-01-02T15:04:05.000000Z07:00"
               }
            }
         },
         "logMetas": {
            "log_group_value": "custom-log-group",    # Log group name of ServiceWatch created in advance
            "log_stream_value": "custom-log-stream"   # Log stream name within the pre‑created ServiceWatch log group
         }
      }
      {
         "fileLog": {
            "include": [
               "/var/log/syslog",        # Log file to be collected by ServiceWatch
               /var/log/auth.log
            ],
            "operators": {
               "regex": "^(?P<timestamp>\\S+)\\s+(?P<hostname>\\S+)\\s+(?P<process>[^:]+):\\s+(?P<message>.*)$",    # Represent log file format with a regular expression
               "timestamp": {            # Set the format of the log message's Time Stamp
                  "layout_type": "gotime"
                  "layout": "2006-01-02T15:04:05.000000Z07:00"
               }
            }
         },
         "logMetas": {
            "log_group_value": "custom-log-group",    # Log group name of ServiceWatch created in advance
            "log_stream_value": "custom-log-stream"   # Log stream name within the pre‑created ServiceWatch log group
         }
      }
      Code block. log.json configuration example
Reference

To link a server’s log files to ServiceWatch via the ServiceWatch Agent, you must first create a log group and a log stream within that log group.

  • For detailed information on creating log groups and log streams, refer to Log.

Running Open Telemetry Collector for ServiceWatch

How to Run ServiceWatch Agent
[ServiceWatch Agent executable] -action [run|stop] - dir [configuration file location] -collector [Open Telemetry Collector executable location]
Execution optionsDetailed description
-actionAction setting (run or stop)
-dirthe location of ServiceWatch Agent configuration files such as agent.json, metric.json, log.json
-collectorOpen Telemetry Collector executable file location
Table. log.json configuration file entries

ServiceWatch Agent execution (for Linux)

Reference
agent.json, metric.json, log.json files are in current location/agent/examples/os-metrics-min-examples, and the otelcontribcol_linux_amd64 file is in current location/agent. Execute as shown below.
  1. Run the ServiceWatch Agent.

    • Check the locations of agent.json, metric.json, log.json files and the locations of servicewatch-agent-manager-linux-amd64, otelcontribcol_linux_amd64 files, and start the ServiceWatch Agent.
      Color mode
      ./agent/servicewatch-agent-manager-linux-amd64 -action run -dir ./agent/examples/os-metrics-min-examples -collector ./agent/otelcontribcol_linux_amd64
      ./agent/servicewatch-agent-manager-linux-amd64 -action run -dir ./agent/examples/os-metrics-min-examples -collector ./agent/otelcontribcol_linux_amd64
      Code block. ServiceWatch Agent start - collect all metrics/logs
    • If you only want to collect metrics, rename the log.json file to a different name or move it so that it is not in the same directory as agent.json, metric.json, and then run as shown below.
      Color mode
      ./agent/servicewatch-agent-manager-linux-amd64 -action run -dir ./agent/examples/os-metrics-min-examples -collector ./agent/otelcontribcol_linux_amd64
      ./agent/servicewatch-agent-manager-linux-amd64 -action run -dir ./agent/examples/os-metrics-min-examples -collector ./agent/otelcontribcol_linux_amd64
      Code block. ServiceWatch Agent start - collect metrics only
    • If you only want to collect logs, rename the metric.json file to a different name or move it so that it is not in the same directory as agent.json, log.json, and run as shown below.
      Color mode
      ./agent/servicewatch-agent-manager-linux-amd64 -action run -dir ./agent/examples/os-metrics-min-examples -collector ./agent/otelcontribcol_linux_amd64
      ./agent/servicewatch-agent-manager-linux-amd64 -action run -dir ./agent/examples/os-metrics-min-examples -collector ./agent/otelcontribcol_linux_amd64
      Code block. ServiceWatch Agent start - collect logs only
  2. Stop the ServiceWatch Agent.

    Color mode
    ./agent/servicewatch-agent-manager-linux-amd64 -action stop -dir ./agent/examples/os-metrics-min-examples
    ./agent/servicewatch-agent-manager-linux-amd64 -action stop -dir ./agent/examples/os-metrics-min-examples
    code block. Stop ServiceWatch Agent

Running ServiceWatch Agent (for Windows)

  1. Run the ServiceWatch Agent.

    Color mode
    servicewatch-agent-manager-windows-amd64.exe -action run -dir ./examples -collector otelcontribcol_windows_amd64.exe
    servicewatch-agent-manager-windows-amd64.exe -action run -dir ./examples -collector otelcontribcol_windows_amd64.exe
    code block. Start ServiceWatch Agent

  2. Stop the ServiceWatch Agent.

    Color mode
    servicewatch-agent-manager-windows-amd64.exe -action stop -dir ./examples
    servicewatch-agent-manager-windows-amd64.exe -action stop -dir ./examples
    code block. Stop ServiceWatch Agent

3 - API Reference

API Reference

4 - CLI Reference

CLI Reference

5 - ServiceWatch Event Reference

Events represent changes in the environment in the Samsung Cloud Platform service. Below are examples of events.

  • Generates an event when the status of a Virtual Server changes from Stopped to Running.
  • Generates an event when a new bucket is created in Object Storage.
  • Generates an event when an IAM user is removed from a user group.
Reference
Refer to the list of Samsung Cloud Platform services that generate events and the events in ServiceWatch Event.

5.1 - ServiceWatch Event

Reference
Events for the Samsung Cloud Platform service may differ across regions.
Service CategoryServiceEvent source
ComputeVirtual ServerVirtual Server
ComputeGPU ServerGPU Server
ComputeBare Metal ServerBare Metal Server
ComputeMulti-node GPU ClusterMulti-node GPU Cluster
ComputeCloud FunctionsCloud Functions
StorageBlock Storage(BM)Block Storage(BM)
StorageFile StoragefiFile Storagelestorage
StorageObject StorageObject Storage
StorageArchive StorageArchive Storage
StorageBackupBackup
ContainerKubernetes EngineKubernetes Engine
ContainerContainer RegistryContainer Registry
NetworkingVPCVPC
NetworkingSecurity GroupSecurity Group
NetworkingLoad BalancerLoad Balancer
NetworkingDNSPrivate DNS
Hosted Zone
Public Domain Name
NetworkingVPNVPN
NetworkingFirewallFirewall
NetworkingDirect ConnectDirect Connect
NetworkingCloud LAN-CampusCloud LAN - Campus (Network)
NetworkingCloud LAN-DatacenterCloud LAN Network
NetworkingCloud WANCloud WAN
NetworkingGlobal CDNGlobal CDN
NetworkingGSLBGSLB
DatabaseEPAS(DBaaS)EPAS
DatabasePostreSQL(DBaaS)PostreSQL
DatabaseMariaDB(DBaaS)MariaDB
DatabaseMySQL(DBaaS)MySQL
DatabaseMicrosoft SQL Server(DBaaS)Microsoft SQL Server
DatabaseCacheStore(DBaaS)CacheStore
DatabaseScalable DB(DBaaS)Scalable DB
Data AnalyticsEvent StreamsEvent Streams
Data AnalyticsSearch EngineSearch Engine
Data AnalyticsVertica(DBaaS)Vertica
Data AnalyticsData FlowData Flow
Data AnalyticsData OpsData Ops
Data AnalyticsQuick QueryQuick Query
Application ServiceAPI GatewayAPI Gateway
Application ServiceQueue ServiceQueue
SecurityKey Management ServiceKey Management Service
SecurityConfig InspectionConfig Inspection
SecurityCertificate ManagerCertificate Manager
SecuritySecrets ManagerSecret
SecuritySecret VaultSecret Vault
ManagementCloud ControlCloud Control
ManagementIAMIdentity and Access Management
ManagementID CenterIdentity Center
ManagementLogging&AuditLogging&Audit
ManagementOrganizationOrganization
ManagementResource GroupsResource Group
ManagementServiceWatchServiceWatch
ManagementSupport CenterSupport
AI-MLCloudMLCloud ML
AI-MLAI&MLOps PlatformAI&MLOps Platform
Table. ServiceWatch event source

5.1.1 - Multi-node GPU Cluster

Multi-node GPU Cluster event

This is the list of events that the Multi-node GPU Cluster service sends to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
ComputeMulti-node GPU ClusterGPU NodeMulti-node GPU ClusterGPU Node
ComputeMulti-node GPU ClusterCluster FabricMulti-node GPU ClusterCluster Fabric
Table. Multi-node GPU Cluster Event Types

GPU Node

Event sourceEvent typeEvent
Multi-node GPU ClusterGPU Node
  • Multi-node GPU Cluster GPU Node creation started
  • Multi-node GPU Cluster GPU Node creation completed
  • Multi-node GPU Cluster GPU Node creation failed
  • Multi-node GPU Cluster GPU Node termination started
  • Multi-node GPU Cluster GPU Node termination completed
  • Multi-node GPU Cluster GPU Node termination failed
  • Multi-node GPU Cluster GPU Node start started
  • Multi-node GPU Cluster GPU Node start completed
  • Multi-node GPU Cluster GPU Node start failed
  • Multi-node GPU Cluster GPU Node stop started
  • Multi-node GPU Cluster GPU Node stop completed
  • Multi-node GPU Cluster GPU Node stop failed
  • Multi-node GPU Cluster GPU Node lock modification started
  • Multi-node GPU Cluster GPU Node lock modification completed
  • Multi-node GPU Cluster GPU Node lock modification failed
  • Multi-node GPU Cluster GPU Node NAT IP allocation started
  • Multi-node GPU Cluster GPU Node NAT IP allocation completed
  • Multi-node GPU Cluster GPU Node NAT IP allocation failed
  • Multi-node GPU Cluster GPU Node NAT IP release started
  • Multi-node GPU Cluster GPU Node NAT IP release completed
  • Multi-node GPU Cluster GPU Node NAT IP release failed
  • Multi-node GPU Cluster GPU Node member change started
  • Multi-node GPU Cluster GPU Node member change completed
  • Multi-node GPU Cluster GPU Node member change failed
Table. Multi-node GPU Cluster - GPU Node event type events

Cluster Fabric

Event sourceEvent typeevent
Multi-node GPU ClusterCluster Fabric
  • Multi-node GPU Cluster Cluster Fabric creation started
  • Multi-node GPU Cluster Cluster Fabric creation completed
  • Multi-node GPU Cluster Cluster Fabric creation failed
  • Multi-node GPU Cluster Cluster Fabric deletion started
  • Multi-node GPU Cluster Cluster Fabric deletion completed
  • Multi-node GPU Cluster Cluster Fabric deletion failed
  • Multi-node GPU Cluster Cluster Fabric member change started
  • Multi-node GPU Cluster Cluster Fabric member change completed
  • Multi-node GPU Cluster Cluster Fabric member change failed
  • Multi-node GPU Cluster Cluster Fabric member addition started
  • Multi-node GPU Cluster Cluster Fabric member addition completed
  • Multi-node GPU Cluster Cluster Fabric member addition failed
  • Multi-node GPU Cluster Cluster Fabric member removal started
  • Multi-node GPU Cluster Cluster Fabric member removal completed
  • Multi-node GPU Cluster Cluster Fabric member removal failed
Table. Multi-node GPU Cluster – Cluster Fabric event type

5.1.2 - MySQL(DBaaS)

MySQL(DBaaS) event

This is the list of events that the MySQL (DBaaS) service sends to ServiceWatch.

Service CategoryserviceSubserviceEvent sourceEvent type
DatabaseMySQL(DBaaS)MySQL(DBaaS)MySQLMySQL
Table. MySQL(DBaaS) Event Types

MySQL

Event sourceEvent typeevent
MySQLMySQL
  • MySQL Create Start
  • MySQL Create Error
  • MySQL Create End
  • MySQL Delete Start
  • MySQL Delete Error
  • MySQL Delete End
  • MySQL Start Start
  • MySQL Start Error
  • MySQL Start End
  • MySQL Stop Start
  • MySQL Stop Error
  • MySQL Stop End
  • MySQL Restart Start
  • MySQL Restart Error
  • MySQL Restart End
  • MySQL Sync Start
  • MySQL Sync Error
  • MySQL Sync End
  • MySQL Maintenance Modify Start
  • MySQL Maintenance Modify Error
  • MySQL Maintenance Modify End
  • MySQL Maintenance Delete Start
  • MySQL Maintenance Delete Error
  • MySQL Maintenance Delete End
  • MySQL Security Group Rule Modify Start
  • MySQL Security Group Rule Modify Error
  • MySQL Security Group Rule Modify End
  • MySQL Instance Resize Start
  • MySQL Instance Resize Error
  • MySQL Instance Resize End
  • MySQL Block Storage Create Start
  • MySQL Block Storage Create Error
  • MySQL Block Storage Create End
  • MySQL Block Storage Resize Start
  • MySQL Block Storage Resize Error
  • MySQL Block Storage Resize End
  • MySQL Parameter Sync Start
  • MySQL Parameter Sync Error
  • MySQL Parameter Sync End
  • MySQL Parameter Modify Start
  • MySQL Parameter Modify Error
  • MySQL Parameter Modify End
  • MySQL Patch Start
  • MySQL Patch Error
  • MySQL Patch End
  • MySQL Backup Config Create Start
  • MySQL Backup Config Create Error
  • MySQL Backup Config Create End
  • MySQL Backup Config Modify Start
  • MySQL Backup Config Modify Error
  • MySQL Backup Config Modify End
  • MySQL Backup Config Delete Start
  • MySQL Backup Config Delete Error
  • MySQL Backup Config Delete End
  • MySQL Backup Recover Start
  • MySQL Backup Recover Error
  • MySQL Backup Recover End
  • MySQL Backup History Delete Start
  • MySQL Backup History Delete Error
  • MySQL Backup History Delete End
  • MySQL Replica Create Start
  • MySQL Replica Create Error
  • MySQL Replica Create End
  • MySQL Replica Reset Start
  • MySQL Replica Reset Error
  • MySQL Replica Reset End
  • MySQL Replica Sync Start
  • MySQL Replica Sync Error
  • MySQL Replica Sync End
  • MySQL Switchover Start
  • MySQL Switchover Error
  • MySQL Switchover End
  • MySQL Log Export Config Create Start
  • MySQL Log Export Config Create Error
  • MySQL Log Export Config Create End
  • MySQL Log Export Config Delete Start
  • MySQL Log Export Config Delete Error
  • MySQL Log Export Config Delete End
  • MySQL Log Export Config Modify Start
  • MySQL Log Export Config Modify Error
  • MySQL Log Export Config Modify End
  • MySQL Log Export Start
  • MySQL Log Export Error
  • MySQL Log Export End
  • MySQL Archive Config Modify Start
  • MySQL Archive Config Modify Error
  • MySQL Archive Config Modify End
  • MySQL Archive Config Sync Start
  • MySQL Archive Config Sync Error
  • MySQL Archive Config Sync End
  • MySQL Database Users Modify Start
  • MySQL Database Users Modify Error
  • MySQL Database Users Modify End
  • MySQL Database Users Sync Start
  • MySQL Database Users Sync Error
  • MySQL Database Users Sync End
  • MySQL Access Control Modify Start
  • MySQL Access Control Modify Error
  • MySQL Access Control Modify End
  • MySQL Access Control Sync Start
  • MySQL Access Control Sync Error
  • MySQL Access Control Sync End
  • MySQL Replica Cluster Promote Start
  • MySQL Replica Cluster Promote Error
  • MySQL Replica Cluster Promote End
  • MySQL Db Connection Check Start
  • MySQL Db Connection Check Error
  • MySQL Db Connection Check End
  • MySQL Cluster Migrate Start
  • MySQL Cluster Migrate Error
  • MySQL Cluster Migrate End
  • MySQL Migration Cluster Promote Start
  • MySQL Migration Cluster Promote Error
  • MySQL Migration Cluster Promote End
Table. MySQL - Event of MySQL event type

5.1.3 - Global CDN

Global CDN event

This is the list of events delivered from the Global CDN service to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
NetworkingGlobal CDNGlobal CDNGlobal CDNGlobal CDN
Table. Global CDN Event Types

Global CDN

Event sourceEvent typeevent
Global CDNGlobal CDN
  • Network CDN creation start
  • Network CDN creation error
  • Network CDN creation complete
  • Network CDN update start
  • Network CDN update error
  • Network CDN update complete
  • Network CDN deletion complete
Table. Global CDN - Event of Global CDN event type

5.1.4 - Data Flow

Data Flow event

This is the list of events delivered from the Data Flow service to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
Data AnalyticsData FlowData FlowData FlowData Flow
Data AnalyticsData FlowData Flow ServicesData FlowData Flow Service
Table. Data Flow Event Types

Data Flow

Event sourceEvent typeevent
Data FlowData Flow
  • Data Flow Create Start
  • Data Flow Create End
  • Data Flow Create Error
  • Data Flow Delete Start
  • Data Flow Delete End
  • Data Flow Delete Error
  • Data Flow Modify Start
  • Data Flow Modify End
  • Data Flow Modify Error
Table. Data Flow - Event of the Data Flow event type

Data Flow Service

Event sourceEvent typeevent
Data Flow ServicesData Flow Service
  • Data Flow Service Create Start
  • Data Flow Service Create End
  • Data Flow Service Create Error
  • Data Flow Service Delete Start
  • Data Flow Service Delete End
  • Data Flow Service Delete Error
  • Data Flow Service Modify Start
  • Data Flow Service Modify End
  • Data Flow Service Modify Error
Table. Data Flow - Event of type Data Flow Service

5.1.5 - GSLB

GSLB event

This is the list of events that the GSLB service delivers to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
NetworkingGSLBGSLBGSLBGSLB
Table. GSLB Event Types

GSLB

Event sourceEvent typeevent
GSLBGSLB(cdn)
  • GSLB creation started
  • GSLB creation error
  • GSLB creation completed
  • GSLB update started
  • GSLB update completed
  • GSLB deletion completed
  • GSLB health check update started
  • GSLB health check update completed
  • GSLB resource update started
  • GSLB resource update completed
Table. GSLB - Event of GSLB event type

5.1.6 - Cloud Control

Cloud Control event

This is the list of events delivered from the Cloud Control service to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
ManagementCloud ControlCloud ControlCloud ControlCloud Control
Table. Cloud Control event types

Landing Zone

Event sourceEvent typeevent
Cloud ControlLanding zone
  • Landing zone creation completed
  • Landing zone deletion started
  • Landing zone deletion error
  • Landing zone deletion completed
Table. Cloud Control - Landing Zone event type events

5.1.7 - Cloud WAN

Cloud WAN event

This is the list of events delivered from the Cloud WAN service to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
NetworkingCloud WANCloud WAN NetworkCloud WANNetwork(WAN)
NetworkingCloud WANSegmentCloud WANSegment
NetworkingCloud WANSegmentCloud WANSegment Location
NetworkingCloud WANSegmentCloud WANSegment Sharing
NetworkingCloud WANAttachmentCloud WANAttachment
Table. Cloud WAN Event Types

Network(WAN)

Event sourceEvent typeevent
Cloud WANNetwork(WAN)
  • Network(WAN) creation started
  • Network(WAN) creation error
  • Network(WAN) creation completed
  • Network(WAN) modification started
  • Network(WAN) modification error
  • Network(WAN) modification completed
  • Network(WAN) deletion started
  • Network(WAN) deletion error
  • Network(WAN) deletion completed
Table. Cloud WAN - Network (WAN) event type events

Segment

Event sourceEvent typeevent
Cloud WANSegment
  • Segment creation started
  • Segment creation error
  • Segment creation completed
  • Segment modification started
  • Segment modification error
  • Segment modification completed
  • Segment deletion started
  • Segment deletion error
  • Segment deletion completed
Table. Event of the Cloud WAN - Segment type

Segment Location

Event sourceEvent typeEvent
Cloud WANSegment Location
  • Segment Location creation start
  • Segment Location creation error
  • Segment Location creation completed
  • Segment Location edit start
  • Segment Location edit error
  • Segment Location edit completed
  • Segment Location deletion start
  • Segment Location deletion error
  • Segment Location deletion completed
Table. Cloud WAN - Segment Location event type event

Segment Sharing

Event sourceEvent typeevent
Cloud WANSegment Sharing
  • Segment Sharing creation started
  • Segment Sharing creation error
  • Segment Sharing creation completed
  • Segment Sharing modification started
  • Segment Sharing modification error
  • Segment Sharing modification completed
  • Segment Sharing deletion started
  • Segment Sharing deletion error
  • Segment Sharing deletion completed
Table. Cloud WAN - Segment Sharing event type event

Attachment

Event sourceEvent typeEvent
Cloud WANAttachment
  • Attachment creation started
  • Attachment creation error
  • Attachment creation completed
  • Attachment modification started
  • Attachment modification error
  • Attachment modification completed
  • Attachment deletion started
  • Attachment deletion error
  • Attachment deletion completed
  • Attachment approval started
  • Attachment approval error
  • Attachment approval completed
  • Attachment cancellation started
  • Attachment cancellation error
  • Attachment cancellation completed
  • Attachment rejection started
  • Attachment rejection error
  • Attachment rejection completed
Table. Cloud WAN - Attachment event type events

5.1.8 - Object Storage

Object Storage event

This is the list of events delivered from the Object Storage service to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
StorageObject StorageObject StorageObject StorageBucket
Table. Object Storage Event Types

Bucket

Event sourceEvent typeevent
Object StorageBucket
  • Object Storage bucket creation started
  • Object Storage bucket creation completed
  • Object Storage bucket creation failed
  • Object Storage bucket deletion started
  • Object Storage bucket deletion completed
  • Object Storage bucket deletion failed
  • Object Storage bucket versioning update started
  • Object Storage bucket versioning update completed
  • Object Storage bucket versioning update failed
  • Object Storage bucket access control creation started
  • Object Storage bucket access control creation completed
  • Object Storage bucket access control creation failed
  • Object Storage bucket access control update started
  • Object Storage bucket access control update completed
  • Object Storage bucket access control update failed
  • Object Storage bucket access control deletion started
  • Object Storage bucket access control deletion completed
  • Object Storage bucket access control deletion failed
  • Object Storage bucket encryption creation started
  • Object Storage bucket encryption creation completed
  • Object Storage bucket encryption creation failed
  • Object Storage bucket encryption update started
  • Object Storage bucket encryption update completed
  • Object Storage bucket encryption update failed
  • Object Storage bucket encryption deletion started
  • Object Storage bucket encryption deletion completed
  • Object Storage bucket encryption deletion failed
  • Object Storage bucket replication policy update started
  • Object Storage bucket replication policy update completed
  • Object Storage bucket replication policy update failed
  • Object Storage bucket replication policy deletion started
  • Object Storage bucket replication policy deletion completed
  • Object Storage bucket replication policy deletion failed
Table. Object Storage - Bucket event type events

5.1.9 - VPC

VPC event

This is the list of events that the VPC service delivers to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
NetworkingVPCVPCVPCVPC
NetworkingVPCSubnetVPCSubnet
NetworkingVPCPortVPCPort
NetworkingVPCInternet GatewayVPCInternet Gateway
NetworkingVPCNAT GatewayVPCNAT Gateway
NetworkingVPCPublic IPVPCPublic IP
NetworkingVPCPrivate NATVPCPrivate NAT
NetworkingVPCVPC EndpointVPCVPC Endpoint
NetworkingVPCVPC PeeringVPCVPC Peering
NetworkingVPCPrivate Link ServiceVPCPrivate Link Service
NetworkingVPCPrivate Link EndpointVPCPrivate Link Endpoint
NetworkingVPCTransit GatewayVPCTransit Gateway
Table. VPC Event Types

VPC

Event sourceEvent typeevent
VPCVPC
  • VPC creation completed
  • VPC update completed
  • VPC deletion completed
Table. VPC - VPC event type events

Subnet

Event sourceEvent typeevent
VPCSubnet
  • Subnet creation started
  • Subnet creation error
  • Subnet creation completed
  • Subnet update completed
  • Subnet deletion started
  • Subnet deletion error
  • Subnet deletion completed
Table. VPC - Subnet event type events

Port

Event sourceEvent typeevent
VPCPort
  • Port creation completed
  • Port creation error
  • Port update completed
  • Port update error
  • Port deletion completed
  • Port deletion error
Table. VPC - Subnet event type events

Internet Gateway

Event sourceEvent typeEvent
VPCInternet Gateway
  • Internet Gateway creation started
  • Internet Gateway creation completed
  • Internet Gateway creation error
  • Internet Gateway update completed
  • Internet Gateway deletion started
  • Internet Gateway deletion error
  • Internet Gateway deletion completed
Table. VPC - Internet Gateway event type

NAT Gateway

Event sourceEvent typeevent
VPCNAT Gateway
  • Start NAT Gateway creation
  • NAT Gateway creation completed
  • NAT Gateway creation error
  • NAT Gateway update completed
  • Start NAT Gateway deletion
  • NAT Gateway deletion error
  • NAT Gateway deletion completed
Table. VPC - NAT Gateway event type events

Public IP

Event sourceEvent typeEvent
VPCPublic IP
  • Public IP creation completed
  • Public IP update completed
  • Public IP deletion completed
Table. Event of VPC - Public IP event type

Private NAT

Event sourceEvent typeevent
VPCPrivate NAT
  • Private NAT creation started
  • Private NAT creation completed
  • Private NAT creation error
  • Private NAT update completed
  • Private NAT deletion started
  • Private NAT deletion error
  • Private NAT deletion completed
  • Private NAT IP creation completed
  • Private NAT IP update completed
  • Private NAT IP deletion completed
Table. VPC - Private NAT event type events

VPC Endpoint

Event sourceEvent typeevent
VPCVPC Endpoint
  • VPC Endpoint creation started
  • VPC Endpoint creation completed
  • VPC Endpoint creation error
  • VPC Endpoint update completed
  • VPC Endpoint deletion started
  • VPC Endpoint deletion error
  • VPC Endpoint deletion completed
Table. VPC - VPC Endpoint event type events

VPC Peering

Event sourceEvent typeevent
VPCVPC Peering
  • VPC Peering creation started
  • VPC Peering creation error
  • VPC Peering creation completed
  • VPC Peering update completed
  • VPC Peering deletion started
  • VPC Peering deletion error
  • VPC Peering deletion completed
  • VPC Peering rule creation started
  • VPC Peering rule creation error
  • VPC Peering rule creation completed
  • VPC Peering rule deletion started
  • VPC Peering rule deletion error
  • VPC Peering rule deletion completed
  • VPC Peering creation approval requested
  • VPC Peering creation approval completed
  • VPC Peering creation approval rejected
  • VPC Peering creation approval canceled
  • VPC Peering creation approval re-requested
  • VPC Peering deletion approval requested
  • VPC Peering deletion approval completed
  • VPC Peering deletion approval rejected
  • VPC Peering deletion approval canceled
Table. VPC - VPC Peering event type
Event sourceEvent typeevent
VPCPrivate Link Service
  • PrivateLink Service creation started
  • PrivateLink Service creation completed
  • PrivateLink Service creation error
  • PrivateLink Service update completed
  • PrivateLink Service deletion started
  • PrivateLink Service deletion error
  • PrivateLink Service deletion completed
Table. VPC - Private Link Service event type events
Event sourceEvent typeevent
VPCPrivateLink Endpoint
  • PrivateLink Endpoint creation started
  • PrivateLink Endpoint creation approval request
  • PrivateLink Endpoint creation approval completed
  • PrivateLink Endpoint creation approval rejected
  • PrivateLink Endpoint creation approval canceled
  • PrivateLink Endpoint creation approval re-request
  • PrivateLink Endpoint creation error
  • PrivateLink Endpoint creation completed
  • PrivateLink Endpoint update completed
  • PrivateLink Endpoint disconnect completed
  • PrivateLink Endpoint disconnect completed
  • PrivateLink Endpoint deletion started
  • PrivateLink Endpoint deletion error
  • PrivateLink Endpoint deletion completed
Table. VPC - PrivateLink Endpoint event type events

Transit Gateway

Event sourceEvent typeevent
VPCTransit Gateway
  • Transit Gateway creation started
  • Transit Gateway creation error
  • Transit Gateway creation completed
  • Transit Gateway update completed
  • Transit Gateway uplink creation completed
  • Transit Gateway uplink deletion completed
  • Transit Gateway uplink update completed
  • Transit Gateway SNMP interface creation completed
  • Transit Gateway SNMP interface deletion completed
  • Transit Gateway deletion started
  • Transit Gateway deletion error
  • Transit Gateway deletion completed
  • Transit Gateway VPC attachment creation started
  • Transit Gateway VPC attachment creation error
  • Transit Gateway VPC attachment creation completed
  • Transit Gateway VPC attachment deletion started
  • Transit Gateway VPC attachment deletion error
  • Transit Gateway VPC attachment deletion completed
  • Transit Gateway rule creation started
  • Transit Gateway rule creation error
  • Transit Gateway rule creation completed
  • Transit Gateway rule deletion started
  • Transit Gateway rule deletion error
  • Transit Gateway rule deletion completed
Table. VPC - Transit Gateway event type events

5.1.10 - GPU Server

GPU Server Event

This is the list of events that the GPU Server service passes to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
ComputeGPU ServerGPU ServerGPU ServerServer
ComputeGPU ServerImageGPU Server
Table. GPU Server Event Types

Server

ServiceEvent typeevent
GPU ServerServer(server)
  • Compute GPU Server Create Start
  • Compute GPU Server Create End
  • Compute GPU Server Create Error
  • Compute GPU Server Delete Start
  • Compute GPU Server Delete End
  • Compute GPU Server Delete Error
  • Compute GPU Server Update End
  • Compute GPU Server Lock End
  • Compute GPU Server Unlock End
  • Compute GPU Server Reboot Start
  • Compute GPU Server Reboot End
  • Compute GPU Server Reboot Error
  • Compute GPU Server Power On Start
  • Compute GPU Server Power On End
  • Compute GPU Server Power On Error
  • Compute GPU Server Power Off Start
  • Compute GPU Server Power Off End
  • Compute GPU Server Power Off Error
  • Compute GPU Server Rebuild Start
  • Compute GPU Server Rebuild End
  • Compute GPU Server Rebuild Error
  • Compute GPU Server Resize Start
  • Compute GPU Server Resize End
  • Compute GPU Server Resize Error
  • Compute GPU Server Resize Revert Start
  • Compute GPU Server Resize Revert End
  • Compute GPU Server Resize Revert Error
  • Compute GPU Server Dump Start
  • Compute GPU Server Dump End
  • Compute GPU Server Dump Error
  • Compute GPU Server Volume Attach Start
  • Compute GPU Server Volume Attach End
  • Compute GPU Server Volume Attach Error
  • Compute GPU Server Volume Detach Start
  • Compute GPU Server Volume Detach End
  • Compute GPU Server Volume Detach Error
  • Compute GPU Server Volume Update End
  • Compute GPU Server Volume Update Error
  • Compute GPU Server Interface Attach End
  • Compute GPU Server Interface Attach Error
  • Compute GPU Server Interface Detach End
  • Compute GPU Server Interface Detach Error
  • Compute GPU Server Interface Change Start
  • Compute GPU Server Interface Change End
  • Compute GPU Server Interface Change Error
Table. GPU Server - Server event type events

Image

ServiceEvent typeEvent
GPU ServerImage
  • Compute Image Create Start
  • Compute Image Create End
  • Compute Image Import Start
  • Compute Image Update End
  • Compute Image Delete End
  • Compute Image Member Create End
  • Compute Image Member Update End
  • Compute Image Member Delete End
  • Compute Image Import End
  • Compute Image Import Error
  • Compute Sharing Image Create Start
  • Compute Sharing Image Create End
  • Compute Sharing Image Create Error
Table. GPU Server - Image event type event

5.1.11 - Virtual Server

Virtual Server event

This is the list of events that the Virtual Server service passes to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
ComputeVirtual ServerVirtual ServerVirtual ServerServer
ComputeVirtual ServerImageVirtual ServerImage
ComputeVirtual ServerKeypairVirtual ServerKeypair
ComputeVitual ServerServer GroupVirtual ServerServer Group
ComputeVirtual ServerLaunch ConfigurationVirtual ServerLaunch Configuration
ComputeVirtual ServerAuto-Scaling GroupVirtual ServerAuto-Scaling Group
ComputeVirtual ServerBlock StorageVirtual ServerVolume
ComputeVirtual ServerBlock StorageVirtual ServerSnapshot
Table. Virtual Server Event Types

Server

Event sourceEvent typeevent
Virtual ServerServer
  • Compute Virtual Server Create Start
  • Compute Virtual Server Create End
  • Compute Virtual Server Create Error
  • Compute Virtual Server Delete Start
  • Compute Virtual Server Delete End
  • Compute Virtual Server Delete Error
  • Compute Virtual Server Update End
  • Compute Virtual Server Lock End
  • Compute Virtual Server Unlock End
  • Compute Virtual Server Reboot Start
  • Compute Virtual Server Reboot End
  • Compute Virtual Server Reboot Error
  • Compute Virtual Server Power On Start
  • Compute Virtual Server Power On End
  • Compute Virtual Server Power On Error
  • Compute Virtual Server Power Off Start
  • Compute Virtual Server Power Off End
  • Compute Virtual Server Power Off Error
  • Compute Virtual Server Rebuild Start
  • Compute Virtual Server Rebuild End
  • Compute Virtual Server Rebuild Error
  • Compute Virtual Server Resize Start
  • Compute Virtual Server Resize End
  • Compute Virtual Server Resize Error
  • Compute Virtual Server Resize Revert Start
  • Compute Virtual Server Resize Revert End
  • Compute Virtual Server Resize Revert Error
  • Compute Virtual Server Dump Start
  • Compute Virtual Server Dump End
  • Compute Virtual Server Dump Error
  • Compute Virtual Server Volume Attach Start
  • Compute Virtual Server Volume Attach End
  • Compute Virtual Server Volume Attach Error
  • Compute Virtual Server Volume Detach Start
  • Compute Virtual Server Volume Detach End
  • Compute Virtual Server Volume Detach Error
  • Compute Virtual Server Volume Update End
  • Compute Virtual Server Volume Update Error
  • Compute Virtual Server Interface Attach End
  • Compute Virtual Server Interface Attach Error
  • Compute Virtual Server Interface Detach End
  • Compute Virtual Server Interface Detach Error
  • Compute Virtual Server Interface Change Start
  • Compute Virtual Server Interface Change End
  • Compute Virtual Server Interface Change Error
Table. Virtual Server - Server event type events

Image

Event sourceEvent typeevent
Virtual ServerImage
  • Compute Image Create Start
  • Compute Image Create End
  • Compute Image Import Start
  • Compute Image Update End
  • Compute Image Delete End
  • Compute Image Member Create End
  • Compute Image Member Update End
  • Compute Image Member Delete End
  • Compute Image Import End
  • Compute Image Import Error
  • Compute Sharing Image Create Start
  • Compute Sharing Image Create End
  • Compute Sharing Image Create Error
Table. Event of the Virtual Server - Image event type

Keypair

Event sourceEvent typeevent
Virtual ServerKeypair
  • Compute Keypair Create End
  • Compute Keypair Delete End
Table. Virtual Server - Keypair event type events

Server Group

Event sourceEvent typeevent
Virtual ServerServer Group
  • Compute Server Group Create End
  • Compute Server Group Delete End
Table. Virtual Server - Server Group event type.

Launch Configuration

Event sourceEvent typeevent
Virtual ServerLaunch Configuration
  • Compute Launch Configuration Create End
  • Compute Launch Configuration Delete End
Table. Event of the Virtual Server - Launch Configuration event type

Auto-Scaling Group

Event sourceEvent typeevent
Virtual ServerAuto-Scaling Group
  • Compute Auto-Scaling Group Create End
  • Compute Auto-Scaling Group Delete End
  • Compute Auto-Scaling Group Delete Error
  • Compute Auto-Scaling Group Policy Create End
  • Compute Auto-Scaling Group Policy Delete End
  • Compute Auto-Scaling Group Policy Update End
  • Compute Auto-Scaling Group Virtual Server Attach End
  • Compute Auto-Scaling Group Virtual Server Detach End
  • Compute Auto-Scaling Group LB Server Group Update Start
  • Compute Auto-Scaling Group LB Server Group Update End/li>
  • Compute Auto-Scaling Group LB Server Group Update Error
  • Compute Auto-Scaling Group Policy Receive Alarm End
  • Compute Auto-Scaling Group Server Count Update End
  • Compute Auto-Scaling Group Update End
  • Compute Auto-Scaling Group Schedule Execute End
  • Compute Auto-Scaling Group Scale Out Start
  • Compute Auto-Scaling Group Scale Out End
  • Compute Auto-Scaling Group Scale In Start
  • Compute Auto-Scaling Group Scale In End
  • Compute Auto-Scaling Group Scale Out Error
  • Compute Auto-Scaling Group Scale In Error
  • Compute Auto-Scaling Group Schedule Create End
  • Compute Auto-Scaling Group Schedule Delete End
  • Compute Auto-Scaling Group Schedule Update End
  • Compute Auto-Scaling Group Notification Create End
  • Compute Auto-Scaling Group Notification Delete End
  • Compute Auto-Scaling Group Notification Update End
  • Compute Auto-Scaling Group Scale Request End
Table. Virtual Server - Auto-Scaling Group event type

Volume

Event sourceEvent typeevent
Virtual ServerVolume
  • Block Storage Volume Create Start
  • Block Storage Volume Create Error
  • Block Storage Volume Create End
  • Block Storage Volume Delete Start
  • Block Storage Volume Delete Error
  • Block Storage Volume Delete End
  • Block Storage Volume Update End
  • Block Storage Volume Resize Start
  • Block Storage Volume Resize Error
  • Block Storage Volume Resize End
  • Block Storage Volume Attach Start
  • Block Storage Volume Attach Error
  • Block Storage Volume Attach End
  • Block Storage Volume Detach Start
  • Block Storage Volume Detach Error
  • Block Storage Volume Detach End
  • Block Storage Volume Transfer Create Start
  • Block Storage Volume Transfer Create Error
  • Block Storage Volume Transfer Create End
  • Block Storage Volume Transfer Delete Start
  • Block Storage Volume Transfer Delete Error
  • Block Storage Volume Transfer Delete End
  • Block Storage Volume Transfer Accept Start
  • Block Storage Volume Transfer Accept Error
  • Block Storage Volume Transfer Accept End
Table. Events of the Virtual Server - Volume event type

Snapshot

Event sourceEvent typeevent
Virtual ServerSnapshot
  • Block Storage Snapshot Revert Start
  • Block Storage Snapshot Revert Error
  • Block Storage Snapshot Revert End
  • Block Storage Snapshot Create Start
  • Block Storage Snapshot Create Error
  • Block Storage Snapshot Create End
  • Block Storage Snapshot Delete Start
  • Block Storage Snapshot Delete Error
  • Block Storage Snapshot Delete End
  • Block Storage Snapshot Update End
Table. Virtual Server - Snapshot event type

5.1.12 - Firewall

Firewall event

This is the list of events that the Firewall service passes to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
NetworkingFirewallfirewallFirewallFirewall
Table. Firewall Event Types

Firewall

Event sourceEvent typeevent
FirewallFirewall
  • Firewall creation error
  • Firewall creation completed
  • Firewall deletion error
  • Firewall deletion completed
  • Firewall resize completed
  • Firewall resize error
  • Firewall activation completed
  • Firewall activation error
  • Firewall deactivation completed
  • Firewall deactivation error
  • Firewall update completed
  • Firewall update error
  • Firewall Rule creation completed
  • Firewall Rule creation error
  • Firewall Rule deletion completed
  • Firewall Rule deletion error
  • Firewall Rule update completed
  • Firewall Rule update error
Table. Firewall - Event of firewall event type

5.1.13 - ID Center

ID Center Event

This is the list of events that the ID Center service sends to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
ManagementID CenterID CenterIdentity CenterID Center
ManagementID CenterPermission setIdentity CenterPermission Set
Table. ID Center Event Types

ID Center

Event sourceEvent typeevent
Identity CenterID Center
  • Identity Center ID Center creation started
  • Identity Center ID Center creation failed
  • Identity Center ID Center creation completed
  • Identity Center ID Center modification started
  • Identity Center ID Center modification failed
  • Identity Center ID Center modification completed
  • Identity Center ID Center deletion started
  • Identity Center ID Center deletion failed
  • Identity Center ID Center deletion completed
Table. ID Center - ID Center event of the event type

Permission Set

Event sourceEvent typeevent
Identity CenterPermission set
  • Identity Center permission set creation started
  • Identity Center permission set creation failed
  • Identity Center permission set creation completed
  • Identity Center permission set modification started
  • Identity Center permission set modification failed
  • Identity Center permission set modification completed
  • Identity Center permission set deletion started
  • Identity Center permission set deletion failed
  • Identity Center permission set deletion completed
Table. ID Center - Permission Set Event Type Event

5.1.14 - Microsoft SQL Server(DBaaS)

Microsoft SQL Server(DBaaS) Event

This is the list of events that the Microsoft SQL Server (DBaaS) service sends to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
DatabaseMicrosoft SQL Server(DBaaS)Microsoft SQL Server(DBaaS)Microsoft SQL ServerMicrosoft SQL Server
Table. Microsoft SQL Server(DBaaS) Event Types

Microsoft SQL Server

Event sourceEvent typeEvent
Microsoft SQL ServerMicrosoft SQL Server
  • SQL Server Create Start
  • SQL Server Create Error
  • SQL Server Create End
  • SQL Server Delete Start
  • SQL Server Delete Error
  • SQL Server Delete End
  • SQL Server Start Start
  • SQL Server Start Error
  • SQL Server Start End
  • SQL Server Stop Start
  • SQL Server Stop Error
  • SQL Server Stop End
  • SQL Server Restart Start
  • SQL Server Restart Error
  • SQL Server Restart End
  • SQL Server Sync Start
  • SQL Server Sync Error
  • SQL Server Sync End
  • SQL Server Audit Log Modify Start
  • SQL Server Audit Log Modify Error
  • SQL Server Audit Log Modify End
  • SQL Server Maintenance Modify Start
  • SQL Server Maintenance Modify Error
  • SQL Server Maintenance Modify End
  • SQL Server Maintenance Delete Start
  • SQL Server Maintenance Delete Error
  • SQL Server Maintenance Delete End
  • SQL Server Security Group Rule Modify Start
  • SQL Server Security Group Rule Modify Error
  • SQL Server Security Group Rule Modify End
  • SQL Server Instance Resize Start
  • SQL Server Instance Resize Error
  • SQL Server Instance Resize End
  • SQL Server Block Storage Create Start
  • SQL Server Block Storage Create Error
  • SQL Server Block Storage Create End
  • SQL Server Block Storage Resize Start
  • SQL Server Block Storage Resize Error
  • SQL Server Block Storage Resize End
  • SQL Server Parameter Sync Start
  • SQL Server Parameter Sync Error
  • SQL Server Parameter Sync End
  • SQL Server Parameter Modify Start
  • SQL Server Parameter Modify Error
  • SQL Server Parameter Modify End
  • SQL Server Patch Start
  • SQL Server Patch Error
  • SQL Server Patch End
  • SQL Server Backup Config Create Start
  • SQL Server Backup Config Create Error
  • SQL Server Backup Config Create End
  • SQL Server Backup Config Modify Start
  • SQL Server Backup Config Modify Error
  • SQL Server Backup Config Modify End
  • SQL Server Backup Config Delete Start
  • SQL Server Backup Config Delete Error
  • SQL Server Backup Config Delete End
  • SQL Server Backup Recover Start
  • SQL Server Backup Recover Error
  • SQL Server Backup Recover End
  • SQL Server Backup History Delete Start
  • SQL Server Backup History Delete Error
  • SQL Server Backup History Delete End
  • SQL Server Switchover Start
  • SQL Server Switchover Error
  • SQL Server Switchover End
  • SQL Server Database Modify Start
  • SQL Server Database Modify Error
  • SQL Server Database Modify End
  • SQL Server Log Export Config Create Start
  • SQL Server Log Export Config Create Error
  • SQL Server Log Export Config Create End
  • SQL Server Log Export Config Delete Start
  • SQL Server Log Export Config Delete Error
  • SQL Server Log Export Config Delete End
  • SQL Server Log Export Config Modify Start
  • SQL Server Log Export Config Modify Error
  • SQL Server Log Export Config Modify End
  • SQL Server Log Export Start
  • SQL Server Log Export Error
  • SQL Server Log Export End
  • SQL Server Database Users Modify Start
  • SQL Server Database Users Modify Error
  • SQL Server Database Users Modify End
  • SQL Server Database Users Sync Start
  • SQL Server Database Users Sync Error
  • SQL Server Database Users Sync End
  • SQL Server Secondary Add Start
  • SQL Server Secondary Add Error
  • SQL Server Secondary Add End
Table. Microsoft SQL Server - Event of Microsoft SQL Server event type

5.1.15 - Block Storage(BM)

Block Storage(BM) Event

List of events sent from the Block Storage (BM) service to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
StorageBlock Storage(BM)Block Storage(BM)Block Storage(BM)Volume
StorageBlock Storage(BM)Volume Group(BM)Block Storage(BM)Volume Group
Table. Block Storage(BM) Event Types

Volume

Event sourceEvent typeevent
Block Storage(BM)Volume
  • Block Storage(BM) Volume creation started
  • Block Storage(BM) Volume creation completed
  • Block Storage(BM) Volume creation failed
  • Block Storage(BM) Volume attachment server creation started
  • Block Storage(BM) Volume attachment server creation completed
  • Block Storage(BM) Volume attachment server creation failed
  • Block Storage(BM) Volume attachment server deletion started
  • Block Storage(BM) Volume attachment server deletion completed
  • Block Storage(BM) Volume attachment server deletion failed
  • Block Storage(BM) Volume deletion started
  • Block Storage(BM) Volume deletion completed
  • Block Storage(BM) Volume deletion failed
  • Block Storage(BM) Volume snapshot capacity creation started
  • Block Storage(BM) Volume snapshot capacity creation completed
  • Block Storage(BM) Volume snapshot capacity creation failed
  • Block Storage(BM) Volume snapshot capacity modification started
  • Block Storage(BM) Volume snapshot capacity modification completed
  • Block Storage(BM) Volume snapshot capacity modification failed
  • Block Storage(BM) Volume snapshot capacity deletion started
  • Block Storage(BM) Volume snapshot capacity deletion completed
  • Block Storage(BM) Volume snapshot capacity deletion failed
  • Block Storage(BM) Volume snapshot creation started
  • Block Storage(BM) Volume snapshot creation completed
  • Block Storage(BM) Volume snapshot creation failed
  • Block Storage(BM) Volume snapshot restore started
  • Block Storage(BM) Volume snapshot restore completed
  • Block Storage(BM) Volume snapshot restore failed
  • Block Storage(BM) Volume snapshot deletion started
  • Block Storage(BM) Volume snapshot deletion completed
  • Block Storage(BM) Volume snapshot deletion failed
  • Block Storage(BM) Volume snapshot schedule creation started
  • Block Storage(BM) Volume snapshot schedule creation completed
  • Block Storage(BM) Volume snapshot schedule creation failed
  • Block Storage(BM) Volume snapshot schedule modification started
  • Block Storage(BM) Volume snapshot schedule modification completed
  • Block Storage(BM) Volume snapshot schedule modification failed
  • Block Storage(BM) Volume snapshot schedule deletion started
  • Block Storage(BM) Volume snapshot schedule deletion completed
  • Block Storage(BM) Volume snapshot schedule deletion failed
  • Block Storage(BM) Volume name modification started
  • Block Storage(BM) Volume name modification completed
  • Block Storage(BM) Volume name modification failed
  • Block Storage(BM) Volume replication creation started
  • Block Storage(BM) Volume replication creation completed
  • Block Storage(BM) Volume replication creation failed
  • Block Storage(BM) Volume replication deletion started
  • Block Storage(BM) Volume replication deletion completed
  • Block Storage(BM) Volume replication deletion failed
  • Block Storage(BM) Volume replication policy creation started
  • Block Storage(BM) Volume replication policy creation completed
  • Block Storage(BM) Volume replication policy creation failed
  • Block Storage(BM) Volume replication policy modification started
  • Block Storage(BM) Volume replication policy modification completed
  • Block Storage(BM) Volume replication policy modification failed
  • Block Storage(BM) Volume replication policy deletion started
  • Block Storage(BM) Volume replication policy deletion completed
  • Block Storage(BM) Volume replication policy deletion failed
  • Block Storage(BM) Volume relationship creation started
  • Block Storage(BM) Volume relationship creation completed
  • Block Storage(BM) Volume relationship creation failed
  • Block Storage(BM) Volume relationship deletion started
  • Block Storage(BM) Volume relationship deletion completed
  • Block Storage(BM) Volume relationship deletion failed
  • Block Storage(BM) Volume replication cycle modification started
  • Block Storage(BM) Volume replication cycle modification completed
  • Block Storage(BM) Volume replication cycle modification failed
  • Block Storage(BM) Volume backup creation started
  • Block Storage(BM) Volume backup creation completed
  • Block Storage(BM) Volume backup creation failed
Table. Block Storage (BM) - Volume event type events

Volume Group

Event sourceEvent typeevent
Volume Group(BM)Volume Group
  • Block Storage(BM) Volume Group creation started
  • Block Storage(BM) Volume Group creation completed
  • Block Storage(BM) Volume Group creation failed
  • Block Storage(BM) Volume Group member addition started
  • Block Storage(BM) Volume Group member addition completed
  • Block Storage(BM) Volume Group member addition failed
  • Block Storage(BM) Volume Group member removal started
  • Block Storage(BM) Volume Group member removal completed
  • Block Storage(BM) Volume Group member removal failed
  • Block Storage(BM) Volume Group deletion started
  • Block Storage(BM) Volume Group deletion completed
  • Block Storage(BM) Volume Group deletion failed
  • Block Storage(BM) Volume Group snapshot creation started
  • Block Storage(BM) Volume Group snapshot creation completed
  • Block Storage(BM) Volume Group snapshot creation failed
  • Block Storage(BM) Volume Group snapshot restore started
  • Block Storage(BM) Volume Group snapshot restore completed
  • Block Storage(BM) Volume Group snapshot restore failed
  • Block Storage(BM) Volume Group snapshot deletion started
  • Block Storage(BM) Volume Group snapshot deletion completed
  • Block Storage(BM) Volume Group snapshot deletion failed
  • Block Storage(BM) Volume Group snapshot schedule creation started
  • Block Storage(BM) Volume Group snapshot schedule creation completed
  • Block Storage(BM) Volume Group snapshot schedule creation failed
  • Block Storage(BM) Volume Group snapshot schedule modification started
  • Block Storage(BM) Volume Group snapshot schedule modification completed
  • Block Storage(BM) Volume Group snapshot schedule modification failed
  • Block Storage(BM) Volume Group snapshot schedule deletion started
  • Block Storage(BM) Volume Group snapshot schedule deletion completed
  • Block Storage(BM) Volume Group snapshot schedule deletion failed
  • Block Storage(BM) Volume Group replication creation started
  • Block Storage(BM) Volume Group replication creation completed
  • Block Storage(BM) Volume Group replication creation failed
  • Block Storage(BM) Volume Group replication deletion started
  • Block Storage(BM) Volume Group replication deletion completed
  • Block Storage(BM) Volume Group replication deletion failed
  • Block Storage(BM) Volume Group replication policy creation started
  • Block Storage(BM) Volume Group replication policy creation completed
  • Block Storage(BM) Volume Group replication policy creation failed
  • Block Storage(BM) Volume Group replication policy modification started
  • Block Storage(BM) Volume Group replication policy modification completed
  • Block Storage(BM) Volume Group replication policy modification failed
  • Block Storage(BM) Volume Group replication policy deletion started
  • Block Storage(BM) Volume Group replication policy deletion completed
  • Block Storage(BM) Volume Group replication policy deletion failed
  • Block Storage(BM) Volume Group relationship creation started
  • Block Storage(BM) Volume Group relationship creation completed
  • Block Storage(BM) Volume Group relationship creation failed
  • Block Storage(BM) Volume Group relationship deletion started
  • Block Storage(BM) Volume Group relationship deletion completed
  • Block Storage(BM) Volume Group relationship deletion failed
  • Block Storage(BM) Volume Group replication interval modification started
  • Block Storage(BM) Volume Group replication interval modification completed
  • Block Storage(BM) Volume Group replication interval modification failed
  • Block Storage(BM) Volume Group recovery point creation started
  • Block Storage(BM) Volume Group recovery point creation completed
  • Block Storage(BM) Volume Group recovery point creation failed
Table. Block Storage (BM) - Volume Group event type events

5.1.16 - Resource Groups

Resource Groups event

This is the list of events that the Resource Groups service delivers to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
ManagementResource GroupsResource GroupsResource GroupsResource Group
Table. Resource Groups event types

Resource Group

Event sourceEvent typeevent
Resource GroupsResource Group
  • Resource Group creation completed
  • Resource Group modification completed
  • Resource Group deletion completed
Table. Resource Groups - Resource Group event type

5.1.17 - Cloud Functions

Cloud Functions event

This is a list of events delivered from the Cloud Functions service to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
ComputeCloud FunctionsFunctionCloud FunctionsCloud Functions
Table. Cloud Functions event types

Cloud Functions

Event sourceEvent typeevent
Cloud FunctionsCloud Functions
  • Function creation started
  • Function creation failed
  • Function creation completed
  • Function modification started
  • Function modification failed
  • Function modification completed
  • Function deletion started
  • Function deletion failed
Table. Cloud Functions - Event of the Cloud Functions event type

5.1.18 - AI&MLOps Platform

AI&MLOps Platform event

This is the list of events delivered from the AI&MLOps Platform service to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
AI-MLAI&MLOps PlatformAI&MLOps PlatformAI&MLOps PlatformAI&MLOps Platform
Table. AI&MLOps Platform Event Types

AI&MLOps Platform

Event sourceEvent typeevent
AI&MLOps PlatformAI&MLOps Platform
  • AI&MLOps Platform Create Start
  • AI&MLOps Platform Create End
  • AI&MLOps Platform Create Error
  • AI&MLOps Platform Delete Start
  • AI&MLOps Platform Delete End
  • AI&MLOps Platform Delete Error
  • AI&MLOps Platform Modify Start
  • AI&MLOps Platform Modify End
  • AI&MLOps Platform Modify Error
Table. AI&MLOps Platform – Event of the AI&MLOps Platform event type

5.1.19 - Event Streams

Event Streams event

This is the list of events delivered from the Event Streams service to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
Data AnalyticsEvent StreamsEvent StreamsEvent StreamsEvent Streams
Table. Event Streams Event Types

Event Streams

Event sourceEvent typeEvent
Event StreamsEvent Streams
  • Event Streams Create Start
  • Event Streams Create Error
  • Event Streams Create End
  • Event Streams Delete Start
  • Event Streams Delete Error
  • Event Streams Delete End
  • Event Streams Start Start
  • Event Streams Start Error
  • Event Streams Start End
  • Event Streams Stop Start
  • Event Streams Stop Error
  • Event Streams Stop End
  • Event Streams Restart Start
  • Event Streams Restart Error
  • Event Streams Restart End
  • Event Streams Sync Start
  • Event Streams Sync Error
  • Event Streams Sync End
  • Event Streams Maintenance Modify Start
  • Event Streams Maintenance Modify Error
  • Event Streams Maintenance Modify End
  • Event Streams Maintenance Delete Start
  • Event Streams Maintenance Delete Error
  • Event Streams Maintenance Delete End
  • Event Streams Security Group Rule Modify Start
  • Event Streams Security Group Rule Modify Error
  • Event Streams Security Group Rule Modify End
  • Event Streams Instance Resize Start
  • Event Streams Instance Resize Error
  • Event Streams Instance Resize End
  • Event Streams Instance Add Start
  • Event Streams Instance Add Error
  • Event Streams Instance Add End
  • Event Streams Block Storage Resize Start
  • Event Streams Block Storage Resize Error
  • Event Streams Block Storage Resize End
  • Event Streams Parameter Sync Start
  • Event Streams Parameter Sync Error
  • Event Streams Parameter Sync End
  • Event Streams Parameter Modify Start
  • Event Streams Parameter Modify Error
  • Event Streams Parameter Modify End
  • CacheStore Backup Config Modify Start
  • CacheStore Backup Config Modify Error
  • CacheStore Backup Config Modify End
  • CacheStore Backup Config Delete Start
  • CacheStore Backup Config Delete Error
  • CacheStore Backup Config Delete End
  • CacheStore Backup Recover Start
  • CacheStore Backup Recover Error
  • CacheStore Backup Recover End
  • CacheStore Backup History Delete Start
  • CacheStore Backup History Delete Error
  • CacheStore Backup History Delete End
  • CacheStore Command Sync Start
  • CacheStore Command Sync Error
  • CacheStore Command Sync End
  • CacheStore Command Modify Start
  • CacheStore Command Modify Error
  • CacheStore Command Modify End
  • CacheStore Switchover Start
  • CacheStore Switchover Error
  • CacheStore Switchover End
Table. Event Streams - Event type events

5.1.20 - Security Group

Security Group event

This is the list of events that the Security Group service delivers to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
NetworkingSecurity GroupSecurity GroupSecurity GroupSecurity Group
Table. Security Group event types

Security Group

Event sourceEvent typeevent
Security GroupSecurity Group
  • Security Group creation completed
  • Security Group deletion completed
  • Security Group modification completed
  • Security Group rule creation completed
  • Security Group rule deletion completed
Table. Security Group – Security Group event type events

5.1.21 - Archive Storage

Archive Storage event

This is the list of events delivered from the Archive Storage service to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
ComputeArchive StorageArchive StorageArchive StorageBucket
Table. Archive Storage Event Types

Bucket

Event sourceEvent typeEvent
Archive StorageBucket
  • Archive Storage bucket creation started
  • Archive Storage bucket creation completed
  • Archive Storage bucket creation failed
  • Archive Storage bucket deletion started
  • Archive Storage bucket deletion completed
  • Archive Storage bucket deletion failed
  • Archive Storage bucket archiving policy creation started
  • Archive Storage bucket archiving policy creation completed
  • Archive Storage bucket archiving policy creation failed
  • Archive Storage bucket archiving policy update started
  • Archive Storage bucket archiving policy update completed
  • Archive Storage bucket archiving policy update failed
  • Archive Storage bucket archiving policy deletion started
  • Archive Storage bucket archiving policy deletion completed
  • Archive Storage bucket archiving policy deletion failed
  • Archive Storage bucket recovery history cancellation started
  • Archive Storage bucket recovery history cancellation completed
  • Archive Storage bucket recovery history cancellation failed
  • Archive Storage bucket archiving history cancellation started
  • Archive Storage bucket archiving history cancellation completed
  • Archive Storage bucket archiving history cancellation failed
  • Archive Storage bucket versioning modification started
  • Archive Storage bucket versioning modification completed
  • Archive Storage bucket versioning modification failed
  • Archive Storage bucket encryption modification started
  • Archive Storage bucket encryption modification completed
  • Archive Storage bucket encryption modification failed
  • Archive Storage bucket archiving policy status modification started
  • Archive Storage bucket archiving policy status modification completed
  • Archive Storage bucket archiving policy status modification failed
Table. Archive Storage - Bucket event type event

5.1.22 - API Gateway

API Gateway event

This is the list of events that the API Gateway service passes to ServiceWatch.

Service CategoryserviceSubserviceEvent sourceEvent type
Application ServiceAPI GatewayAPI GatewayAPI GatewayAPI Gateway
Table. API Gateway event types

API Gateway

Event sourceEvent typeevent
API GatewayAPI Gateway
  • API Gateway API creation request
  • API Gateway API creation failed
  • API Gateway API creation succeeded
  • API Gateway API update failed
  • API Gateway API update succeeded
  • API Gateway API deletion request
  • API Gateway API deletion failed
  • API Gateway API deletion succeeded
  • API Gateway resource creation failed
  • API Gateway resource creation succeeded
  • API Gateway resource deletion failed
  • API Gateway resource deletion succeeded
  • API Gateway method creation failed
  • API Gateway method creation succeeded
  • API Gateway method update failed
  • API Gateway method update succeeded
  • API Gateway method deletion failed
  • API Gateway method deletion succeeded
  • API Gateway stage creation failed
  • API Gateway stage creation succeeded
  • API Gateway stage update failed
  • API Gateway stage update succeeded
  • API Gateway stage deletion failed
  • API Gateway stage deletion succeeded
  • API Gateway deployment creation failed
  • API Gateway deployment creation succeeded
  • API Gateway deployment update failed
  • API Gateway deployment update succeeded
  • API Gateway authorizer creation failed
  • API Gateway authorizer creation succeeded
  • API Gateway authorizer update failed
  • API Gateway authorizer update succeeded
  • API Gateway authorizer deletion failed
  • API Gateway authorizer deletion succeeded
  • API Gateway access control creation failed
  • API Gateway access control creation succeeded
  • API Gateway access control update failed
  • API Gateway access control update succeeded
  • API Gateway access control deletion failed
  • API Gateway access control deletion succeeded
  • API Gateway usage plan creation failed
  • API Gateway usage plan creation succeeded
  • API Gateway usage plan description update failed
  • API Gateway usage plan description update succeeded
  • API Gateway usage plan quota update failed
  • API Gateway usage plan quota update succeeded
  • API Gateway usage plan deletion failed
  • API Gateway usage plan deletion succeeded
  • API Gateway API Key creation failed
  • API Gateway API Key creation succeeded
  • API Gateway API Key update failed
  • API Gateway API Key update succeeded
  • API Gateway API Key deletion failed
  • API Gateway API Key deletion succeeded
Table. API Gateway - Event of API Gateway event type

5.1.23 - Load Balancer

Load Balancer event

This is the list of events delivered from the Load Balancer service to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
NetworkingLoad BalancerLoad BalancerLoad BalancerLoad Balancer
NetworkingLoad BalancerLoad BalancerLoad BalancerLB Listener
NetworkingLoad BalancerLB server groupLoad BalancerLB Server Group
NetworkingLoad BalancerLB health checkLoad BalancerLB Health Check
Table. Load Balancer Event Types

Load Balancer

Event sourceEvent typeevent
Load BalancerLoad Balancer(security-group)
  • Load Balancer creation completed
  • Load Balancer deletion completed
  • Load Balancer update completed
Table. Load Balancer - Load Balancer event type events

LB Listener

Event sourceEvent typeevent
LB ListenerLB Listener
  • LB Listener creation completed
  • LB Listener deletion completed
  • LB Listener update completed
Table. Load Balancer - LB Listener event type events

LB Server Group

Event sourceEvent typeevent
LB Server GroupLB Server Group
  • LB Server Group creation completed
  • LB Server Group deletion completed
  • LB Server Group update completed
  • LB Server Group deletion completed
  • LB Server Group member creation completed
  • LB Server Group member update completed
  • LB Server Group member deletion completed
Table. Load Balancer - LB Server Group event type events

LB Health Check

Event sourceEvent typeevent
LB Health CheckLB Health Check
  • LB Health Check creation completed
  • LB Health Check deletion completed
  • LB Health Check update completed
Table. Load Balancer - LB Health Check event type event

5.1.24 - Data Ops

Data Ops event

This is the list of events that the Data Ops service sends to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
Data AnalyticsData OpsData OpsData OpsData Ops
Data AnalyticsData OpsData Ops ServicesData OpsData Ops Service
Table. Data Ops Event Types

Data Ops

Event sourceEvent typeevent
Data OpsData Ops
  • Data Ops Create Start
  • Data Ops Create End
  • Data Ops Create Error
  • Data Ops Delete Start
  • Data Ops Delete End
  • Data Ops Delete Error
  • Data Ops Modify Start
  • Data Ops Modify End
  • Data Ops Modify Error
Table. Data Ops - Event of the Data Ops event type

Data Ops Service

Event sourceEvent typeevent
Data Ops ServicesData Ops Service
  • Data Ops Service Create Start
  • Data Ops Service Create End
  • Data Ops Service Create Error
  • Data Ops Service Delete Start
  • Data Ops Service Delete End
  • Data Ops Service Delete Error
  • Data Ops Service Modify Start
  • Data Ops Service Modify End
  • Data Ops Service Modify Error
Table. Data Ops - Data Ops Service event type events

5.1.25 - Scalable DB(DBaaS)

Scalable DB event

This is the list of events that the Scalable DB (DBaaS) service sends to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
Data AnalyticsScalable DB(DBaaS)Scalable DB(DBaaS)Scalable DBScalable DB
Table. Scalable DB Event Types

Scalable DB

Event sourceEvent typeevent
Scalable DBScalable DB
  • Scalable DB Create Start
  • Scalable DB Create Error
  • Scalable DB Create End
  • Scalable DB Delete Start
  • Scalable DB Delete Error
  • Scalable DB Delete End
  • Scalable DB Start Start
  • Scalable DB Start Error
  • Scalable DB Start End
  • Scalable DB Stop Start
  • Scalable DB Stop Error
  • Scalable DB Stop End
  • Scalable DB Sync Start
  • Scalable DB Sync Error
  • Scalable DB Sync End
  • Scalable DB Instance Group Restart Start
  • Scalable DB Instance Group Restart Error
  • Scalable DB Instance Group Restart End
  • Scalable DB Maintenance Modify Start
  • Scalable DB Maintenance Modify Error
  • Scalable DB Maintenance Modify End
  • Scalable DB Maintenance Delete Start
  • Scalable DB Maintenance Delete Error
  • Scalable DB Maintenance Delete End
  • Scalable DB Security Group Rule Modify Start
  • Scalable DB Security Group Rule Modify Error
  • Scalable DB Security Group Rule Modify End
  • Scalable DB Backup Config Create Start
  • Scalable DB Backup Config Create Error
  • Scalable DB Backup Config Create End
  • Scalable DB Backup Config Modify Start
  • Scalable DB Backup Config Modify Error
  • Scalable DB Backup Config Modify End
  • Scalable DB Backup Config Delete Start
  • Scalable DB Backup Config Delete Error
  • Scalable DB Backup Config Delete End
  • Scalable DB Backup History Delete Start
  • Scalable DB Backup History Delete Error
  • Scalable DB Backup History Delete End
  • Scalable DB Scale In Start
  • Scalable DB Scale In Error
  • Scalable DB Scale In End
  • Scalable DB Scale Out Start
  • Scalable DB Scale Out Error
  • Scalable DB Scale Out End
  • Scalable DB Proxy Parameter Modify Start
  • Scalable DB Proxy Parameter Modify Error
  • Scalable DB Proxy Parameter Modify End
  • Scalable DB Proxy Parameter Sync Start
  • Scalable DB Proxy Parameter Sync Error
  • Scalable DB Proxy Parameter Sync End
  • Scalable DB Auto Scaling Policy Create Start
  • Scalable DB Auto Scaling Policy Create Error
  • Scalable DB Auto Scaling Policy Create End
  • Scalable DB Auto Scaling Policy Modify Start
  • Scalable DB Auto Scaling Policy Modify Error
  • Scalable DB Auto Scaling Policy Modify End
  • Scalable DB Auto Scaling Policy Delete Start
  • Scalable DB Auto Scaling Policy Delete Error
  • Scalable DB Auto Scaling Policy Delete End
  • Scalable DB Server Count Modify Start
  • Scalable DB Server Count Modify Error
  • Scalable DB Server Count Modify End
  • Scalable DB Replica Sync Start
  • Scalable DB Replica Sync Error
  • Scalable DB Replica Sync End
  • Scalable DB Replica Sync End
Table. Scalable DB - Queue event type events

5.1.26 - Cloud LAN-Campus

Cloud LAN-Campus event

This is the list of events that the Cloud LAN-Campus service delivers to ServiceWatch.

Service CategoryserviceSubserviceEvent sourceEvent type
NetworkingCloud LAN-CampusCloud LAN-CampusCloud LAN - Campus (Network)Cloud LAN - Campus (Network)
Table. Cloud LAN-Campus Event Types

Cloud LAN - Campus (Network)

Event sourceEvent typeevent
Cloud LAN - Campus (Network)Cloud LAN - Campus (Network)
  • Cloud LAN - Campus Network creation started
  • Cloud LAN - Campus Network creation error
  • Cloud LAN - Campus Network creation completed
  • Cloud LAN - Campus Network modification started
  • Cloud LAN - Campus Network modification error
  • Cloud LAN - Campus Network modification completed
  • Cloud LAN - Campus Network deletion started
  • Cloud LAN - Campus Network deletion error
  • Cloud LAN - Campus Network deletion completed
Table. Cloud LAN-Campus - Cloud LAN - Campus (Network) event type

5.1.27 - EPAS(DBaaS)

EPAS(DBaaS) event

List of events sent from the EPAS (DBaaS) service to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
DatabaseEPAS(DBaaS)EPAS(DBaaS)EPASEPAS
Table. EPAS(DBaaS) Event Types

EPAS

Event sourceEvent typeevent
EPASEPAS
  • EPAS Create Start
  • EPAS Create Error
  • EPAS Create End
  • EPAS Delete Start
  • EPAS Delete Error
  • EPAS Delete End
  • EPAS Start Start
  • EPAS Start Error
  • EPAS Start End
  • EPAS Stop Start
  • EPAS Stop Error
  • EPAS Stop End
  • EPAS Restart Start
  • EPAS Restart Error
  • EPAS Restart End
  • EPAS Sync Start
  • EPAS Sync Error
  • EPAS Sync End
  • EPAS Audit Log Modify Start
  • EPAS Audit Log Modify Error
  • EPAS Audit Log Modify End
  • EPAS Maintenance Modify Start
  • EPAS Maintenance Modify Error
  • EPAS Maintenance Modify End
  • EPAS Maintenance Delete Start
  • EPAS Maintenance Delete Error
  • EPAS Maintenance Delete End
  • EPAS Security Group Rule Modify Start
  • EPAS Security Group Rule Modify Error
  • EPAS Security Group Rule Modify End
  • EPAS Instance Resize Start
  • EPAS Instance Resize Error
  • EPAS Instance Resize End
  • EPAS Block Storage Create Start
  • EPAS Block Storage Create Error
  • EPAS Block Storage Create End
  • EPAS Block Storage Resize Start
  • EPAS Block Storage Resize Error
  • EPAS Block Storage Resize End
  • EPAS Parameter Sync Start
  • EPAS Parameter Sync Error
  • EPAS Parameter Sync End
  • EPAS Parameter Modify Start
  • EPAS Parameter Modify Error
  • EPAS Parameter Modify End
  • EPAS Patch Start
  • EPAS Patch Error
  • EPAS Patch End
  • EPAS Backup Config Create Start
  • EPAS Backup Config Create Error
  • EPAS Backup Config Create End
  • EPAS Backup Config Modify Start
  • EPAS Backup Config Modify Error
  • EPAS Backup Config Modify End
  • EPAS Backup Config Delete Start
  • EPAS Backup Config Delete Error
  • EPAS Backup Config Delete End
  • EPAS Backup Recover Start
  • EPAS Backup Recover Error
  • EPAS Backup Recover End
  • EPAS Backup History Delete Start
  • EPAS Backup History Delete Error
  • EPAS Backup History Delete End
  • EPAS Replica Create Start
  • EPAS Replica Create Error
  • EPAS Replica Create End
  • EPAS Replica Reset Start
  • EPAS Replica Reset Error
  • EPAS Replica Reset End
  • EPAS Replica Sync Start
  • EPAS Replica Sync Error
  • EPAS Replica Sync End
  • EPAS Switchover Start
  • EPAS Switchover Error
  • EPAS Switchover End
  • EPAS Log Export Config Create Start
  • EPAS Log Export Config Create Error
  • EPAS Log Export Config Create End
  • EPAS Log Export Config Delete Start
  • EPAS Log Export Config Delete Error
  • EPAS Log Export Config Delete End
  • EPAS Log Export Config Modify Start
  • EPAS Log Export Config Modify Error
  • EPAS Log Export Config Modify End
  • EPAS Log Export Start
  • EPAS Log Export Error
  • EPAS Log Export End
  • EPAS Archive Config Modify Start
  • EPAS Archive Config Modify Error
  • EPAS Archive Config Modify End
  • EPAS Archive Config Sync Start
  • EPAS Archive Config Sync Error
  • EPAS Archive Config Sync End
  • EPAS Archive Log Delete Start
  • EPAS Archive Log Delete Error
  • EPAS Archive Log Delete End
  • EPAS Database Users Modify Start
  • EPAS Database Users Modify Error
  • EPAS Database Users Modify End
  • EPAS Database Users Sync Start
  • EPAS Database Users Sync Error
  • EPAS Database Users Sync End
  • EPAS Access Control Modify Start
  • EPAS Access Control Modify Error
  • EPAS Access Control Modify End
  • EPAS Access Control Sync Start
  • EPAS Access Control Sync Error
  • EPAS Access Control Sync End
  • EPAS Replica Cluster Promote Start
  • EPAS Replica Cluster Promote Error
  • EPAS Replica Cluster Promote End
  • EPAS DB Connection Check Start
  • EPAS DB Connection Check Error
  • EPAS DB Connection Check End
  • EPAS Cluster Migrate Start
  • EPAS Cluster Migrate Error
  • EPAS Cluster Migrate End
  • EPAS Migration Cluster Promote Start
  • EPAS Migration Cluster Promote Error
  • EPAS Migration Cluster Promote End
Table. EPAS – Event of EPAS event type

5.1.28 - PostreSQL(DBaaS)

PostreSQL(DBaaS) event

This is the list of events that the PostreSQL (DBaaS) service sends to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
DatabasePostreSQL(DBaaS)PostreSQL(DBaaS)PostreSQLPostgreSQL
Table. PostreSQL(DBaaS) Event Types

PostreSQL

Event sourceEvent typeEvent
PostreSQLPostgreSQL
  • PostgreSQL Create Start
  • PostgreSQL Create Error
  • PostgreSQL Create End
  • PostgreSQL Delete Start
  • PostgreSQL Delete Error
  • PostgreSQL Delete End
  • PostgreSQL Start Start
  • PostgreSQL Start Error
  • PostgreSQL Start End
  • PostgreSQL Stop Start
  • PostgreSQL Stop Error
  • PostgreSQL Stop End
  • PostgreSQL Restart Start
  • PostgreSQL Restart Error
  • PostgreSQL Restart End
  • PostgreSQL Sync Start
  • PostgreSQL Sync Error
  • PostgreSQL Sync End
  • PostgreSQL Audit Log Modify Start
  • PostgreSQL Audit Log Modify Error
  • PostgreSQL Audit Log Modify End
  • PostgreSQL Maintenance Modify Start
  • PostgreSQL Maintenance Modify Error
  • PostgreSQL Maintenance Modify End
  • PostgreSQL Maintenance Delete Start
  • PostgreSQL Maintenance Delete Error
  • PostgreSQL Maintenance Delete End
  • PostgreSQL Security Group Rule Modify Start
  • PostgreSQL Security Group Rule Modify Error
  • PostgreSQL Security Group Rule Modify End
  • PostgreSQL Instance Resize Start
  • PostgreSQL Instance Resize Error
  • PostgreSQL Instance Resize End
  • PostgreSQL Block Storage Create Start
  • PostgreSQL Block Storage Create Error
  • PostgreSQL Block Storage Create End
  • PostgreSQL Block Storage Resize Start
  • PostgreSQL Block Storage Resize Error
  • PostgreSQL Block Storage Resize End
  • PostgreSQL Parameter Sync Start
  • PostgreSQL Parameter Sync Error
  • PostgreSQL Parameter Sync End
  • PostgreSQL Parameter Modify Start
  • PostgreSQL Parameter Modify Error
  • PostgreSQL Parameter Modify End
  • PostgreSQL Patch Start
  • PostgreSQL Patch Error
  • PostgreSQL Patch End
  • PostgreSQL Backup Config Create Start
  • PostgreSQL Backup Config Create Error
  • PostgreSQL Backup Config Create End
  • PostgreSQL Backup Config Modify Start
  • PostgreSQL Backup Config Modify Error
  • PostgreSQL Backup Config Modify End
  • PostgreSQL Backup Config Delete Start
  • PostgreSQL Backup Config Delete Error
  • PostgreSQL Backup Config Delete End
  • PostgreSQL Backup Recover Start
  • PostgreSQL Backup Recover Error
  • PostgreSQL Backup Recover End
  • PostgreSQL Backup History Delete Start
  • PostgreSQL Backup History Delete Error
  • PostgreSQL Backup History Delete End
  • PostgreSQL Replica Create Start
  • PostgreSQL Replica Create Error
  • PostgreSQL Replica Create End
  • PostgreSQL Replica Reset Start
  • PostgreSQL Replica Reset Error
  • PostgreSQL Replica Reset End
  • PostgreSQL Replica Sync Start
  • PostgreSQL Replica Sync Error
  • PostgreSQL Replica Sync End
  • PostgreSQL Switchover Start
  • PostgreSQL Switchover Error
  • PostgreSQL Switchover End
  • PostgreSQL Log Export Config Create Start
  • PostgreSQL Log Export Config Create Error
  • PostgreSQL Log Export Config Create End
  • PostgreSQL Log Export Config Delete Start
  • PostgreSQL Log Export Config Delete Error
  • PostgreSQL Log Export Config Delete End
  • PostgreSQL Log Export Config Modify Start
  • PostgreSQL Log Export Config Modify Error
  • PostgreSQL Log Export Config Modify End
  • PostgreSQL Log Export Start
  • PostgreSQL Log Export Error
  • PostgreSQL Log Export End
  • PostgreSQL Archive Config Modify Start
  • PostgreSQL Archive Config Modify Error
  • PostgreSQL Archive Config Modify End
  • PostgreSQL Archive Config Sync Start
  • PostgreSQL Archive Config Sync Error
  • PostgreSQL Archive Config Sync End
  • PostgreSQL Archive Log Delete Start
  • PostgreSQL Archive Log Delete Error
  • PostgreSQL Archive Log Delete End
  • PostgreSQL Database Users Modify Start
  • PostgreSQL Database Users Modify Error
  • PostgreSQL Database Users Modify End
  • PostgreSQL Database Users Sync Start
  • PostgreSQL Database Users Sync Error
  • PostgreSQL Database Users Sync End
  • PostgreSQL Access Control Modify Start
  • PostgreSQL Access Control Modify Error
  • PostgreSQL Access Control Modify End
  • PostgreSQL Access Control Sync Start
  • PostgreSQL Access Control Sync Error
  • PostgreSQL Access Control Sync End
  • PostgreSQL Replica Cluster Promote Start
  • PostgreSQL Replica Cluster Promote Error
  • PostgreSQL Replica Cluster Promote End
  • PostgreSQL Db Connection Check Start
  • PostgreSQL Db Connection Check Error
  • PostgreSQL Db Connection Check End
  • PostgreSQL Cluster Migrate Start
  • PostgreSQL Cluster Migrate Error
  • PostgreSQL Cluster Migrate End
  • PostgreSQL Migration Cluster Promote Start
  • PostgreSQL Migration Cluster Promote Error
  • PostgreSQL Migration Cluster Promote End
Table. PostgreSQL - Event of PostgreSQL event type

5.1.29 - Logging&Audit

Logging&Audit event

This is the list of events that the Logging&Audit service delivers to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
ManagementLogging&AuditTrailLogging&AuditTrail
Table. Logging&Audit event types

Trail

Event sourceEvent typeevent
Logging&AuditTrail
  • Logging&Audit Trail creation start
  • Logging&Audit Trail creation complete
  • Logging&Audit Trail deletion start
  • Logging&Audit Trail deletion complete
  • Logging&Audit Trail update start
  • Logging&Audit Trail update complete
  • Logging&Audit Trail start
  • Logging&Audit Trail stop
  • Logging&Audit Trail batch start
  • Logging&Audit Trail batch complete
  • Logging&Audit Trail batch count
Table. Logging&Audit - Trail event type event

5.1.30 - Search Engine

Search Engine event

This is the list of events passed from the Search Engine service to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
Data AnalyticsSearch EngineSearch EngineSearch EngineSearch Engine
Table. Search Engine Event Types

Search Engine

Event sourceEvent typeevent
Search EngineSearch Engine
  • Search Engine Create Start
  • Search Engine Create Error
  • Search Engine Create End
  • Search Engine Delete Start
  • Search Engine Delete Error
  • Search Engine Delete End
  • Search Engine Start Start
  • Search Engine Start Error
  • Search Engine Start End
  • Search Engine Stop Start
  • Search Engine Stop Error
  • Search Engine Stop End
  • Search Engine Restart Start
  • Search Engine Restart Error
  • Search Engine Restart End
  • Search Engine Sync Start
  • Search Engine Sync Error
  • Search Engine Sync End
  • Search Engine Patch Start
  • Search Engine Patch Error
  • Search Engine Patch End
  • Search Engine Maintenance Modify Start
  • Search Engine Maintenance Modify Error
  • Search Engine Maintenance Modify End
  • Search Engine Maintenance Delete Start
  • Search Engine Maintenance Delete Error
  • Search Engine Maintenance Delete End
  • Search Engine Security Group Rule Modify Start
  • Search Engine Security Group Rule Modify Error
  • Search Engine Security Group Rule Modify End
  • Search Engine Instance Resize Start
  • Search Engine Instance Resize Error
  • Search Engine Instance Resize End
  • Search Engine Instance Add Start
  • Search Engine Instance Add Error
  • Search Engine Instance Add End
  • Search Engine Block Storage Create Start
  • Search Engine Block Storage Create Error
  • Search Engine Block Storage Create End
  • Search Engine Block Storage Resize Start
  • Search Engine Block Storage Resize Error
  • Search Engine Block Storage Resize End
  • Search Engine Backup Config Create Start
  • Search Engine Backup Config Create Error
  • Search Engine Backup Config Create End
  • Search Engine Backup Config Modify Start
  • Search Engine Backup Config Modify Error
  • Search Engine Backup Config Modify End
  • Search Engine Backup Config Delete Start
  • Search Engine Backup Config Delete Error
  • Search Engine Backup Config Delete End
  • Search Engine Backup Recover Start
  • Search Engine Backup Recover Error
  • Search Engine Backup Recover End
  • Search Engine Backup History Delete Start
  • Search Engine Backup History Delete Error
  • Search Engine Backup History Delete End
Table. Search Engine - Event of the Search Engine event type

5.1.31 - DNS

DNS event

This is the list of events passed from the DNS service to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
NetworkingDNSPrivate DNSPrivate DNSPrivate DNS
NetworkingDNSHosted DNSHosted DNSHosted DNS
NetworkingDNSPublic Domain NamePublic Domain NamePublic Domain Name
Table. DNS Event Types

Private DNS

Event sourceEvent typeEvent
Private DNSPrivate DNS
  • Private DNS creation start
  • Private DNS creation completed
  • Private DNS modification start
  • Private DNS modification completed
  • Private DNS deletion completed
Table. Private DNS - Event of Private DNS event type

Hosted DNS

Event sourceEvent typeEvent
Hosted DNSHosted DNS
  • Hosted Zone creation started
  • Hosted Zone update completed
  • Hosted Zone record creation completed
  • Hosted Zone record update completed
  • Hosted Zone record deletion completed
  • Hosted Zone deletion completed
Table. Hosted DNS - Event of Hosted DNS event type

Public Domain Name

Event sourceEvent typeevent
Public Domain NamePublic Domain Name
  • Public Domain Name creation completed
  • Public Domain Name modification completed
  • Public Domain Name deletion completed
Table. Public Domain Name - Public Domain Name event of the event type

5.1.32 - VPN

VPN Event

This is the list of events transmitted from the VPN service to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
NetworkingVPNVPNVPNVPN Gateway
NetworkingVPNVPNVPNVPN Tunnel
Table. VPN Event Types

VPN Gateway

Event sourceEvent typeevent
VPNVPN Gateway
  • VPN Gateway creation started
  • VPN Gateway creation error
  • VPN Gateway creation completed
  • VPN Gateway modification completed
  • VPN Gateway deletion started
  • VPN Gateway deletion error
  • VPN Gateway deletion completed
Table. VPN - VPN Gateway event type events

VPN Tunnel

Event sourceEvent typeEvent
VPNVPN Tunnel
  • VPN Tunnel creation started
  • VPN Tunnel creation error
  • VPN Tunnel creation completed
  • VPN Tunnel modification completed
  • VPN Tunnel deletion started
  • VPN Tunnel deletion error
  • VPN Tunnel deletion completed
Table. Events of the VPN - VPN Tunnel event type

5.1.33 - Secrets Manager

Secret event

This is the list of events that the Secrets Manager service delivers to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
Data AnalyticsSecrets ManagerSecrets ManagerSecrets ManagerSecret
Table. Secret event type

Secret

Event sourceEvent typeEvent
Secrets ManagerSecret
  • Secret creation started
  • Secret creation completed
  • Secret creation error
  • Secret update completed
  • Secret deletion error
  • Secret deletion completed
Table. Secrets Manager - Secret event type event

5.1.34 - Quick Query

Quick Query event

This is the list of events that the Quick Query service delivers to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
Data AnalyticsQuick QueryQuick QueryQuick QueryQuick Query
Table. Quick Query Event Types

Quick Query

Event sourceEvent typeevent
Quick QueryQuick Query
  • Quick Query Create Start
  • Quick Query Create End
  • Quick Query Create Error
  • Quick Query Delete Start
  • Quick Query Delete End
  • Quick Query Delete Error
  • Quick Query Modify Start
  • Quick Query Modify End
  • Quick Query Modify Error
Table. Quick Query - Event of type Quick Query

5.1.35 - File Storage

File Storage Event

This is the list of events delivered from the File Storage service to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
StorageFile StorageFile StorageFile StorageVolume
Table. File Storage event types

Volume

Event sourceEvent typeevent
File StorageVolume
  • File Storage volume creation started
  • File Storage volume creation completed
  • File Storage volume creation failed
  • File Storage volume deletion started
  • File Storage volume deletion completed
  • File Storage volume deletion failed
  • File Storage snapshot creation started
  • File Storage snapshot creation completed
  • File Storage snapshot creation failed
  • File Storage snapshot deletion started
  • File Storage snapshot deletion completed
  • File Storage snapshot deletion failed
  • File Storage snapshot recovery started
  • File Storage snapshot recovery completed
  • File Storage snapshot recovery failed
  • File Storage snapshot schedule creation started
  • File Storage snapshot schedule creation completed
  • File Storage snapshot schedule creation failed
  • File Storage snapshot schedule modification started
  • File Storage snapshot schedule modification completed
  • File Storage snapshot schedule modification failed
  • File Storage snapshot schedule deletion started
  • File Storage snapshot schedule deletion completed
  • File Storage snapshot schedule deletion failed
  • File Storage volume modification started
  • File Storage volume modification completed
  • File Storage volume modification failed
  • File Storage access control modification started
  • File Storage access control modification completed
  • File Storage access control modification failed
  • File Storage access control (Bulk) modification started
  • File Storage access control (Bulk) modification completed
  • File Storage access control (Bulk) modification failed
  • File Storage replication creation started
  • File Storage replication creation completed
  • File Storage replication creation failed
  • File Storage replication relationship creation started
  • File Storage replication relationship creation completed
  • File Storage replication relationship creation failed
  • File Storage replication deletion started
  • File Storage replication deletion completed
  • File Storage replication deletion failed
  • File Storage replication modification started
  • File Storage replication modification completed
  • File Storage replication modification failed
Table. File Storage - Volume event type events

5.1.36 - CacheStore(DBaaS)

CacheStore (DBaaS) event

This is the list of events delivered from the CacheStore (DBaaS) service to ServiceWatch.

Service CategoryserviceSubserviceEvent sourceEvent type
DatabaseCacheStore(DBaaS)CacheStore(DBaaS)CacheStoreCacheStore
Table. CacheStore(DBaaS) Event Types

CacheStore

Event sourceEvent typeevent
CacheStore(DBaaS)CacheStore
  • CacheStore Create Start
  • CacheStore Create Error
  • CacheStore Create End
  • CacheStore Delete Start
  • CacheStore Delete Error
  • CacheStore Delete End
  • CacheStore Start Start
  • CacheStore Start Error
  • CacheStore Start End
  • CacheStore Stop Start
  • CacheStore Stop Error
  • CacheStore Stop End
  • CacheStore Restart Start
  • CacheStore Restart Error
  • CacheStore Restart End
  • CacheStore Sync Start
  • CacheStore Sync Error
  • CacheStore Sync End
  • CacheStore Maintenance Modify Start
  • CacheStore Maintenance Modify Error
  • CacheStore Maintenance Modify End
  • CacheStore Maintenance Delete Start
  • CacheStore Maintenance Delete Error
  • CacheStore Maintenance Delete End
  • CacheStore Security Group Rule Modify Start
  • CacheStore Security Group Rule Modify Error
  • CacheStore Security Group Rule Modify End
  • CacheStore Instance Resize Start
  • CacheStore Instance Resize Error
  • CacheStore Instance Resize End
  • CacheStore Block Storage Resize Start
  • CacheStore Block Storage Resize Error
  • CacheStore Block Storage Resize End
  • CacheStore Parameter Sync Start
  • CacheStore Parameter Sync Error
  • CacheStore Parameter Sync End
  • CacheStore Parameter Modify Start
  • CacheStore Parameter Modify Error
  • CacheStore Parameter Modify End
  • CacheStore Backup Config Create Start
  • CacheStore Backup Config Create Error
  • CacheStore Backup Config Create End
  • CacheStore Backup Config Modify Start
  • CacheStore Backup Config Modify Error
  • CacheStore Backup Config Modify End
  • CacheStore Backup Config Delete Start
  • CacheStore Backup Config Delete Error
  • CacheStore Backup Config Delete End
  • CacheStore Backup Recover Start
  • CacheStore Backup Recover Error
  • CacheStore Backup Recover End
  • CacheStore Backup History Delete Start
  • CacheStore Backup History Delete Error
  • CacheStore Backup History Delete End
  • CacheStore Command Sync Start
  • CacheStore Command Sync Error
  • CacheStore Command Sync End
  • CacheStore Command Modify Start
  • CacheStore Command Modify Error
  • CacheStore Command Modify End
  • CacheStore Switchover Start
  • CacheStore Switchover Error
  • CacheStore Switchover End
  • SQL Server Switchover Start
  • SQL Server Switchover Error
  • SQL Server Switchover End
  • SQL Server Database Modify Start
  • SQL Server Database Modify Error
  • SQL Server Database Modify End
  • SQL Server Log Export Config Create Start
  • SQL Server Log Export Config Create Error
  • SQL Server Log Export Config Create End
  • SQL Server Log Export Config Delete Start
  • SQL Server Log Export Config Delete Error
  • SQL Server Log Export Config Delete End
  • SQL Server Log Export Config Modify Start
  • SQL Server Log Export Config Modify Error
  • SQL Server Log Export Config Modify End
  • SQL Server Log Export Start
  • SQL Server Log Export Error
  • SQL Server Log Export End
  • SQL Server Database Users Modify Start
  • SQL Server Database Users Modify Error
  • SQL Server Database Users Modify End
  • SQL Server Database Users Sync Start
  • SQL Server Database Users Sync Error
  • SQL Server Database Users Sync End
  • SQL Server Secondary Add Start
  • SQL Server Secondary Add Error
  • SQL Server Secondary Add End
Table. CacheStore (DBaaS) - Event of CacheStore event type

5.1.37 - Secret Vault

Secret Vault event

This is the list of events that the Secret Vault service delivers to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
SecuritySecret VaultSecret VaultSecret VaultSecret Vault
Table. Secret Vault event types

Secret Vault

Event sourceEvent typeEvent
Secret VaultSecret Vault
  • Secret Vault creation started
  • Secret Vault creation completed
  • Secret Vault creation error
  • Secret Vault update started
  • Secret Vault update completed
  • Secret Vault update error
  • Secret Vault deletion started
  • Secret Vault deletion error
  • Secret Vault deletion completed
  • Secret Vault temporary key generation error
  • Secret Vault temporary key generation completed
Table. Secret Vault - Event of type Secret Vault

5.1.38 - Queue Service

Queue Service event

This is the list of events that the Queue Service delivers to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
Data AnalyticsQueue ServiceQueueQueueQueue
Table. Queue Service Event Types

Queue

Event sourceEvent typeevent
QueueQueue
  • Queue creation started
  • Queue creation failed
  • Queue creation completed
  • Queue deletion started
  • Queue deletion failed
  • Queue deletion completed
  • Queue modification started
  • Queue modification failed
  • Queue modification completed
Table. Queue Service - Queue event type events

5.1.39 - Kubernetes Engine

Kubernetes Engine event

List of events passed from the Kubernetes Engine service to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
ContainerKubernetes EngineClusterKubernetes EngineCluster
ContainerKubernetes EngineNodeKubernetes EngineNodepool
Table. Kubernetes Engine Event Types

Cluster

Event sourceEvent typeEvent
Kubernetes EngineCluster
  • Cluster creation request completed
  • Cluster creation completed
  • Cluster creation failed
  • Cluster deletion completed
  • Cluster deletion failed
  • Cluster modification request completed
  • Cluster modification completed
  • Cluster creation failed
Table. Kubernetes Engine - Cluster event type events

Nodepool

Event sourceEvent typeEvent
Kubernetes EngineNodepool
  • Nodepool creation completed
  • Nodepool creation failed
  • Nodepool deletion request completed
  • Nodepool deletion completed
  • Nodepool deletion failed
Table. Kubernetes Engine - Nodepool event type

5.1.40 - Config Inspection

Config Inspection event

This is the list of events that the Config Inspection service delivers to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
SecurityConfig InspectionConfig InspectionConfig InspectionConfig Inspection
Table. Config Inspection Event Types

Config Inspection

Event sourceEvent typeevent
Config InspectionConfig Inspection
  • Config Inspection creation started
  • Config Inspection creation completed
  • Config Inspection monthly creation completed
  • Config Inspection creation error
  • Config Inspection modification started
  • Config Inspection modification completed
  • Config Inspection modification error
  • Config Inspection deletion started
  • Config Inspection deletion error
  • Config Inspection monthly deletion completed
  • Config Inspection deletion completed
  • Config Inspection request started
  • Config Inspection request completed
  • Config Inspection request error
  • Config Inspection reservation request error
  • Config Inspection response started
  • Config Inspection response completed
  • Config Inspection response error
Table. Config Inspection - Event of the Config Inspection event type

5.1.41 - Cloud LAN-Datacenter

Cloud LAN-Datacenter event

This is the list of events that the Cloud LAN-Datacenter service delivers to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
NetworkingCloud LAN-DatacenterCloud LAN NetworkCloud LAN NetworkCloud LAN Network
NetworkingCloud LAN-DatacenterInterfaceCloud LAN NetworkInterface
NetworkingCloud LAN-DatacentervCableCloud LAN NetworkvCable
NetworkingCloud LAN-DatacentervDeviceCloud LAN NetworkvDevice
Table. Cloud LAN Network Event Types

Cloud LAN Network

Event sourceEvent typeevent
Cloud LAN NetworkCloud LAN Network(cloud-lan-network)
  • Cloud LAN Network creation started
  • Cloud LAN Network creation error
  • Cloud LAN Network creation completed
  • Cloud LAN Network modification started
  • Cloud LAN Network modification error
  • Cloud LAN Network modification completed
  • Cloud LAN Network deletion started
  • Cloud LAN Network deletion error
  • Cloud LAN Network deletion completed
Table. Cloud LAN Network – Event of type Cloud LAN Network

Interface

Event sourceEvent typeevent
Cloud LAN NetworkInterface(interface)
  • Interface creation start
  • Interface creation error
  • Interface creation complete
  • Interface modification start
  • Interface modification error
  • Interface modification complete
  • Interface deletion start
  • Interface deletion error
  • Interface deletion complete
Table. Cloud LAN Network - Interface event type events

vCable

Event sourceEvent typeEvent
Cloud LAN NetworkvCable(vcable)
  • vCable creation started
  • vCable creation error
  • vCable creation completed
  • vCable modification started
  • vCable modification error
  • vCable modification completed
  • vCable deletion started
  • vCable deletion error
  • vCable deletion completed
Table. Cloud LAN Network - vCable event type events

vDevice

Event sourceEvent typeEvent
Cloud LAN NetworkvDevice(vdevice)
  • vDevice creation started
  • vDevice creation error
  • vDevice creation completed
  • vDevice modification started
  • vDevice modification error
  • vDevice modification completed
  • vDevice deletion started
  • vDevice deletion error
  • vDevice deletion completed
Table. Cloud LAN Network - vDevice event type events

5.1.42 - Identity Access Management

Identity Access Management event

This is the list of events that the Identity Access Management service delivers to ServiceWatch.

Service CategoryserviceSubserviceEvent sourceEvent type
ManagementIdentity Access Management(IAM)User groupIdentity Access ManagementGroup
ManagementIdentity Access Management(IAM)UserIdentity Access ManagementUser
ManagementIdentity Access Management(IAM)policyIdentity Access ManagementPolicy
ManagementIdentity Access Management(IAM)roleIdentity Access Managementrole
ManagementIdentity Access Management(IAM)Credential ProviderIdentity Access ManagementCredential Provider
ManagementIdentity Access Management(IAM)My Info.Identity Access ManagementAccess Key
Table. Identity Access Management Event Types

Group

Event sourceEvent typeevent
Identity Access ManagementGroup
  • Group creation completed
  • Group creation started
  • Group creation error
  • Group modification completed
  • Group deletion started
  • Group deletion error
  • Group deletion completed
  • Group member addition completed
  • Group member deletion started
  • Group member deletion error
  • Group member deletion completed
Table. Identity Access Management - Group Event Type Events

User

Event sourceEvent typeevent
Identity Access ManagementUser
  • User creation completed
  • User login completed
  • User deletion completed
Table. Identity Access Management – User Event Type Events

Policy

Event sourceEvent typeevent
Identity Access Managementpolicy
  • Policy creation completed
  • Policy modification started
  • Policy modification error
  • Policy modification completed
  • Policy deletion started
  • Policy deletion error
  • Policy deletion completed
Table. Identity Access Management - Policy Event Type Events

role

Event sourceEvent typeEvent
Identity Access Managementrole
  • Role creation completed
  • Role modification completed
  • Role deletion completed
Table. Identity Access Management - Role Event Type Events

Credential Provider

Event sourceEvent typeevent
Identity Access ManagementCredential Provider
  • Credential provider creation started
  • Credential provider creation error
  • Credential provider creation completed
  • Credential provider update started
  • Credential provider update error
  • Credential provider update completed
  • Credential provider deletion started
  • Credential provider deletion error
  • Credential provider deletion completed
Table. Identity Access Management - Events of Credential Provider Event Types

Access Key

Event sourceEvent typeEvent
Identity Access ManagementAccess Key
  • Access Key creation started
  • Access Key creation error
  • Access Key creation completed
  • Access Key deletion started
  • Access Key deletion error
  • Access Key deletion completed
Table. Identity Access Management - Access Key event type events

5.1.43 - Bare Metal Server

Bare Metal Server Event

This is the list of events that the Bare Metal Server service delivers to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
ComputeBare Metal ServerBare Metal ServerBare Metal ServerBare Metal Server
Table. GPU Server Event Types

Bare Metal Server

Event sourceEvent typeevent
Bare Metal ServerBare Metal Server
  • Bare Metal Server Create started
  • Bare Metal Server Create completed
  • Bare Metal Server Create error
  • Bare Metal Server Delete started
  • Bare Metal Server Delete completed
  • Bare Metal Server Delete error
  • Bare Metal Server Start started
  • Bare Metal Server Start completed
  • Bare Metal Server Start error
  • Bare Metal Server Stop started
  • Bare Metal Server Stop completed
  • Bare Metal Server Stop error
  • Bare Metal Server Lock Update started
  • Bare Metal Server Lock Update completed
  • Bare Metal Server Lock Update error
  • Bare Metal Server ISCSI IP allocation started
  • Bare Metal Server ISCSI IP allocation completed
  • Bare Metal Server ISCSI IP allocation error
  • Bare Metal Server Backup Agent IP allocation started
  • Bare Metal Server Backup Agent IP allocation completed
  • Bare Metal Server Backup Agent IP allocation error
  • Bare Metal Server IP allocation started
  • Bare Metal Server IP allocation completed
  • Bare Metal Server IP allocation error
  • Bare Metal Server Local Subnet IP allocation started
  • Bare Metal Server Local Subnet IP allocation completed
  • Bare Metal Server Local Subnet IP allocation error
  • Bare Metal Server ISCSI IP release started
  • Bare Metal Server ISCSI IP release completed
  • Bare Metal Server ISCSI IP release error
  • Bare Metal Server Backup Agent IP release started
  • Bare Metal Server Backup Agent IP release completed
  • Bare Metal Server Backup Agent IP release error
  • Bare Metal Server IP release started
  • Bare Metal Server IP release completed
  • Bare Metal Server IP release error
  • Bare Metal Server Local Subnet IP release started
  • Bare Metal Server Local Subnet IP release completed
  • Bare Metal Server Local Subnet IP release error
  • Bare Metal Server Public NAT IP allocation started
  • Bare Metal Server Public NAT IP allocation completed
  • Bare Metal Server Public NAT IP allocation error
  • Bare Metal Server Public NAT IP release started
  • Bare Metal Server Public NAT IP release completed
  • Bare Metal Server Public NAT IP release error
  • Bare Metal Server IP change started
  • Bare Metal Server IP change completed
  • Bare Metal Server IP change error
  • Bare Metal Server IP change Step1 started
  • Bare Metal Server IP change Step1 completed
  • Bare Metal Server IP change Step1 error
  • Bare Metal Server IP change Step2 started
  • Bare Metal Server IP change Step2 completed
  • Bare Metal Server IP change Step2 error
  • Bare Metal Server IP change Step3 started
  • Bare Metal Server IP change Step3 completed
  • Bare Metal Server IP change Step3 error
  • Bare Metal Server Private NAT IP allocation started
  • Bare Metal Server Private NAT IP allocation completed
  • Bare Metal Server Private NAT IP allocation error
  • Bare Metal Server Private NAT IP release started
  • Bare Metal Server Private NAT IP release completed
  • Bare Metal Server Private NAT IP release error
Table. Bare Metal Server - Bare Metal Server event type

5.1.44 - ServiceWatch

ServiceWatch event

This is a list of events delivered from the ServiceWatch service to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
ManagementServiceWatchDashboardServiceWatchDashboard
ManagementServiceWatchAlertServiceWatchAlert
ManagementServiceWatchLogServiceWatchLog Group
ManagementServiceWatchEvent RulesServiceWatchEvent Rules
Table. ServiceWatch Event Types

Dashboard

Event sourceEvent typeEvent
ServiceWatchDashboard
  • ServiceWatch dashboard creation completed
  • ServiceWatch dashboard modification completed
  • ServiceWatch dashboard deletion completed
Table. ServiceWatch - Dashboard event type events

Alert

Event sourceEvent typeEvent
ServiceWatchAlert
  • ServiceWatch alert creation completed
  • ServiceWatch alert modification completed
  • ServiceWatch alert deletion completed
  • ServiceWatch alert status change completed
Table. ServiceWatch - event of alarm event type

Log group

Event sourceEvent typeEvent
ServiceWatchLog group
  • ServiceWatch log group creation completed
  • ServiceWatch log group modification completed
  • ServiceWatch log group deletion started
  • ServiceWatch log group deletion completed
  • ServiceWatch log group log events bulk deletion started
  • ServiceWatch log group log events bulk deletion completed
  • ServiceWatch log group log stream creation completed
  • ServiceWatch log group log stream deletion completed
  • ServiceWatch log group log stream log events bulk deletion completed
Table. ServiceWatch - Event of log group event type

Event Rules

Event sourceEvent typeEvent
ServiceWatchEvent Rules
  • ServiceWatch event rule creation completed
  • ServiceWatch event rule modification completed
  • ServiceWatch event rule deletion completed
Table. ServiceWatch - Event rule events of the event type

5.1.45 - MariaDB(DBaaS)

MariaDB(DBaaS) Event

List of events sent from the MariaDB (DBaaS) service to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
DatabaseMariaDB(DBaaS)MariaDB(DBaaS)MariaDBMariaDB
Table. MariaDB(DBaaS) Event Types

MariaDB

Event sourceEvent typeEvent
MariaDBMariaDB
  • MariaDB Create Start
  • MariaDB Create Error
  • MariaDB Create End
  • MariaDB Delete Start
  • MariaDB Delete Error
  • MariaDB Delete End
  • MariaDB Start Start
  • MariaDB Start Error
  • MariaDB Start End
  • MariaDB Stop Start
  • MariaDB Stop Error
  • MariaDB Stop End
  • MariaDB Restart Start
  • MariaDB Restart Error
  • MariaDB Restart End
  • MariaDB Sync Start
  • MariaDB Sync Error
  • MariaDB Sync End
  • MariaDB Audit Log Modify Start
  • MariaDB Audit Log Modify Error
  • MariaDB Audit Log Modify End
  • MariaDB Maintenance Modify Start
  • MariaDB Maintenance Modify Error
  • MariaDB Maintenance Modify End
  • MariaDB Maintenance Delete Start
  • MariaDB Maintenance Delete Error
  • MariaDB Maintenance Delete End
  • MariaDB Security Group Rule Modify Start
  • MariaDB Security Group Rule Modify Error
  • MariaDB Security Group Rule Modify End
  • MariaDB Instance Resize Start
  • MariaDB Instance Resize Error
  • MariaDB Instance Resize End
  • MariaDB Block Storage Create Start
  • MariaDB Block Storage Create Error
  • MariaDB Block Storage Create End
  • MariaDB Block Storage Resize Start
  • MariaDB Block Storage Resize Error
  • MariaDB Block Storage Resize End
  • MariaDB Parameter Sync Start
  • MariaDB Parameter Sync Error
  • MariaDB Parameter Sync End
  • MariaDB Parameter Modify Start
  • MariaDB Parameter Modify Error
  • MariaDB Parameter Modify End
  • MariaDB Patch Start
  • MariaDB Patch Error
  • MariaDB Patch End
  • MariaDB Backup Config Create Start
  • MariaDB Backup Config Create Error
  • MariaDB Backup Config Create End
  • MariaDB Backup Config Modify Start
  • MariaDB Backup Config Modify Error
  • MariaDB Backup Config Modify End
  • MariaDB Backup Config Delete Start
  • MariaDB Backup Config Delete Error
  • MariaDB Backup Config Delete End
  • MariaDB Backup Recover Start
  • MariaDB Backup Recover Error
  • MariaDB Backup Recover End
  • MariaDB Backup History Delete Start
  • MariaDB Backup History Delete Error
  • MariaDB Backup History Delete End
  • MariaDB Replica Create Start
  • MariaDB Replica Create Error
  • MariaDB Replica Create End
  • MariaDB Replica Reset Start
  • MariaDB Replica Reset Error
  • MariaDB Replica Reset End
  • MariaDB Replica Sync Start
  • MariaDB Replica Sync Error
  • MariaDB Replica Sync End
  • MariaDB Switchover Start
  • MariaDB Switchover Error
  • MariaDB Switchover End
  • MariaDB Log Export Config Create Start
  • MariaDB Log Export Config Create Error
  • MariaDB Log Export Config Create End
  • MariaDB Log Export Config Delete Start
  • MariaDB Log Export Config Delete Error
  • MariaDB Log Export Config Delete End
  • MariaDB Log Export Config Modify Start
  • MariaDB Log Export Config Modify Error
  • MariaDB Log Export Config Modify End
  • MariaDB Log Export Start
  • MariaDB Log Export Error
  • MariaDB Log Export End
  • MariaDB Archive Config Modify Start
  • MariaDB Archive Config Modify Error
  • MariaDB Archive Config Modify End
  • MariaDB Archive Config Sync Start
  • MariaDB Archive Config Sync Error
  • MariaDB Archive Config Sync End
  • MariaDB Database Users Modify Start
  • MariaDB Database Users Modify Error
  • MariaDB Database Users Modify End
  • MariaDB Database Users Sync Start
  • MariaDB Database Users Sync Error
  • MariaDB Database Users Sync End
  • MariaDB Access Control Modify Start
  • MariaDB Access Control Modify Error
  • MariaDB Access Control Modify End
  • MariaDB Access Control Sync Start
  • MariaDB Access Control Sync Error
  • MariaDB Access Control Sync End
  • MariaDB Replica Cluster Promote Start
  • MariaDB Replica Cluster Promote Error
  • MariaDB Replica Cluster Promote End
  • MariaDB Db Connection Check Start
  • MariaDB Db Connection Check Error
  • MariaDB Db Connection Check End
  • MariaDB Cluster Migrate Start
  • MariaDB Cluster Migrate Error
  • MariaDB Cluster Migrate End
  • MariaDB Migration Cluster Promote Start
  • MariaDB Migration Cluster Promote Error
  • MariaDB Migration Cluster Promote End
Table. MariaDB - Event of MariaDB event type

5.1.46 - Container Registry

Container Registry event

This is the list of events passed from the Container Registry service to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
ContainerContainer RegistryRegistryContainer RegistryContainer Registry
ContainerContainer RegistryNodeContainer RegistryRepository
Table. Container Registry event types

Container Registry

Event sourceEvent typeevent
Container RegistryContainer Registry
  • Start creating Container Registry
  • Failed to create Container Registry
  • Container Registry creation completed
  • Start creating Container Registry bucket
  • Failed to create Container Registry bucket
  • Container Registry bucket creation completed
  • Start updating Container Registry
  • Failed to update Container Registry
  • Container Registry update completed
  • Start deleting Container Registry
  • Failed to delete Container Registry
  • Container Registry deletion completed
  • Start deleting Container Registry bucket
  • Failed to delete Container Registry bucket
  • Container Registry bucket deletion completed
  • Start rollback after Container Registry create/delete failure
  • Rollback after Container Registry create/delete failure failed
  • Rollback after Container Registry create/delete failure completed
  • Container Registry login failed
  • Container Registry login completed
  • Failed to retrieve Container Registry catalog
  • Container Registry catalog retrieval completed
Table. Container Registry – events of the Container Registry event type

Repository

Event sourceEvent typeevent
Container RegistryRepository
  • Repository creation started
  • Repository creation failed
  • Repository creation completed
  • Repository modification started
  • Repository modification failed
  • Repository modification completed
  • Repository deletion started
  • Repository deletion failed
  • Repository deletion completed
  • Repository push failed
  • Repository push completed
  • Repository pull failed
  • Repository pull completed
  • Image creation failed
  • Image creation completed
  • Image modification started
  • Image modification failed
  • Image modification completed
  • Image deletion started
  • Image deletion failed
  • Image deletion completed
  • Image deletion policy test started
  • Image deletion policy test failed
  • Image deletion policy test completed
  • Tags creation failed
  • Tags creation completed
  • Tags modification started
  • Tags modification failed
  • Tags modification completed
  • Tags deletion started
  • Tags deletion failed
  • Tags deletion completed
  • Tags vulnerability scan started
  • Tags vulnerability scan failed
  • Tags vulnerability scan completed
Table. Container Registry - Repository event type events

5.1.47 - Vertica(DBaaS)

Vertica(DBaaS) Event

This is the list of events that the Vertica (DBaaS) service delivers to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
DatabaseVertica(DBaaS)Vertica(DBaaS)VerticaVertica
Table. Vertica(DBaaS) Event Types

Vertica

Event sourceEvent typeevent
VerticaVertica
  • Vertica Create Start
  • Vertica Create Error
  • Vertica Create End
  • Vertica Delete Start
  • Vertica Delete Error
  • Vertica Delete End
  • Vertica Start Start
  • Vertica Start Error
  • Vertica Start End
  • Vertica Stop Start
  • Vertica Stop Error
  • Vertica Stop End
  • Vertica Restart Start
  • Vertica Restart Error
  • Vertica Restart End
  • Vertica Sync Start
  • Vertica Sync Error
  • Vertica Sync End
  • Verticat Maintenance Modify Start
  • Verticat Maintenance Modify Error
  • Verticat Maintenance Modify End
  • Verticat Maintenance Delete Start
  • Verticat Maintenance Delete Error
  • Verticat Maintenance Delete End
  • Vertica Security Group Rule Modify Start
  • Vertica Security Group Rule Modify Error
  • Vertica Security Group Rule Modify End
  • Verticat Instance Resize Start
  • Verticat Instance Resize Error
  • Verticat Instance Resize End
  • Vertica Block Storage Create Start
  • Vertica Block Storage Create Error
  • Vertica Block Storage Create End
  • Vertica Block Storage Resize Start
  • Vertica Block Storage Resize Error
  • Vertica Block Storage Resize End
  • Vertica Backup Config Create Start
  • Vertica Backup Config Create Error
  • Vertica Backup Config Create End
  • Vertica Backup Config Modify Start
  • Vertica Backup Config Modify Error
  • Vertica Backup Config Modify End
  • Vertica Backup Config Delete Start
  • Vertica Backup Config Delete Error
  • Vertica Backup Config Delete End
  • Verticat Backup Recover Start
  • Verticat Backup Recover Error
  • Verticat Backup Recover End
  • Vertica Backup History Delete Start
  • Vertica Backup History Delete Error
  • Vertica Backup History Delete End
Table. Vertica - Event of Vertica event type

5.1.48 - Backup

Backup event

This is the list of events that the Backup service sends to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
StorageBackupBackupBackupBackup
Table. Backup Event Types

Backup

Event sourceEvent typeEvent
BackupBucket
  • Backup Create Start
  • Backup Create End
  • Backup Create Error
  • Backup Modify Start
  • Backup Modify End
  • Backup Modify Error
  • Backup Delete Start
  • Backup Delete End
  • Backup Delete Error
  • Backup Restore Create Start
  • Backup Restore Create End
  • Backup Restore Create Error
  • Backup Cancel Start
  • Backup Cancel End
  • Backup Cancel Error
  • Backup Manual Backup Request Start
  • Backup Manual Backup Request End
  • Backup Manual Backup Request Error
  • Backup Restore Target Delete Start
  • Backup Restore Target Delete End
  • Backup Restore Target Delete Error
  • Backup Restore Target Delete Cancel Start
  • Backup Restore Target Delete Cancel End
  • Backup Restore Target Delete Cancel Error
  • Backup Filesystem Path Modify Start
  • Backup Filesystem Path Modify End
  • Backup Filesystem Path Modify Error
  • Backup Filesystem Restore Request Start
  • Backup Filesystem Restore Request End
  • Backup Filesystem Restore Request Error
  • Backup Fail
Table. Backup - Event of type Backup

5.1.49 - Organization

Organization event

List of events delivered from the Organization service to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
ManagementOrganizationOrganizational StructureOrganizationorganization
ManagementOrganizationOrganizational StructureOrganizationOrganization Account
ManagementOrganizationOrganizational StructureOrganizationOrganization Invitation
ManagementOrganizationOrganizational StructureOrganizationOrganizational Unit
ManagementOrganizationControl PolicyOrganizationControl Policy
ManagementOrganizationOrganization SettingsOrganizationDelegation Policy
Table. Organization Event Types

organization

Event sourceEvent typeevent
Organizationorganization
  • Organization creation completed
  • Organization modification started
  • Organization modification error
  • Organization deletion started
  • Organization deletion error
  • Organization deletion completed
  • Organization withdrawal started (admin account)
  • Organization withdrawal error (admin account)
  • Organization withdrawal completed (admin account)
  • Organization withdrawal completed (member account)
Table. Organization - Event of organization event type

Organization account

Event sourceEvent typeevent
OrganizationOrganization account
  • Organization account creation completed
  • Organization account migration started
  • Organization account migration error
  • Organization account deletion started
  • Organization account deletion error
  • Organization account deletion completed
Table. Organization - Event of organization account event type

Organization Invitation

Event sourceEvent typeEvent
OrganizationOrganization invitation
  • Organization invitation creation completed
  • Organization invitation acceptance started
  • Organization invitation acceptance error
  • Organization invitation rejection started
  • Organization invitation rejection error
  • Organization invitation rejection completed
  • Organization invitation cancellation started
  • Organization invitation cancellation error
  • Organization invitation cancellation completed
Table. Organization - Event of organization invitation type

organizational unit

Event sourceEvent typeEvent
Organizationorganizational unit
  • Organization unit creation completed
  • Organization unit modification started
  • Organization unit modification error
  • Organization unit deletion started
  • Organization unit deletion error
  • Organization unit deletion completed
Table. Organization - Event of organization unit event type

Control Policy

Event sourceEvent typeevent
OrganizationControl Policy
  • Control policy creation completed
  • Control policy modification started
  • Control policy modification error
  • Control policy deletion started
  • Control policy deletion error
  • Control policy deletion completed
Table. Organization - Event of control policy event type

Delegation Policy

Event sourceEvent typeevent
OrganizationDelegation Policy
  • Delegation policy creation completed
  • Delegation policy modification started
  • Delegation policy modification error
  • Delegation policy deletion started
  • Delegation policy deletion error
  • Delegation policy deletion completed
Table. Organization - Delegated policy event type events

5.1.50 - Cloud ML

Cloud ML Event

This is the list of events sent from the Cloud ML service to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
AI-MLCloudMLCloudMLCloud MLCloud ML
Table. Cloud ML Event Types

Cloud ML

Event sourceEvent typeevent
Cloud MLCloud ML
  • Cloud ML Create Start
  • Cloud ML Create End
  • Cloud ML Create Error
  • Cloud ML Delete Start
  • Cloud ML Delete End
  • Cloud ML Delete Error
  • Cloud ML Modify Start
  • Cloud ML Modify End
  • Cloud ML Modify Error
Table. Cloud ML - Event of Cloud ML event type

5.1.51 - Certificate Manager

Certificate Manager event

This is the list of events that the Certificate Manager service passes to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
SecurityCertificate ManagerCertificate ManagerCertificate ManagerCertificate Manager
Table. Certificate Manager Event Types

Certificate Manager

Event sourceEvent typeevent
Certificate ManagerCertificate Manager
  • Security certificate creation started
  • Security certificate creation completed
  • Security certificate expiration alert
  • Security certificate deletion completed
  • Security certificate alarm recipient registration started
  • Security certificate alarm recipient registration completed
  • Security certificate alarm recipient registration error
  • Security certificate alarm recipient deletion started
  • Security certificate alarm recipient deletion completed
  • Security certificate alarm recipient deletion error
Table. Certificate Manager - Event of the Certificate Manager event type

5.1.52 - Key Management Service

Key Management Service event

This is the list of events that the Key Management Service delivers to ServiceWatch.

Service CategoryserviceSubserviceEvent sourceEvent type
SecurityKey Management ServiceKey Management ServiceKey Management ServiceKey
Table. Key Management Service event types

Key

Event sourceEvent typeevent
Key Management ServiceKey
  • KMS creation started
  • KMS creation completed
  • KMS creation error
  • KMS update completed
  • KMS update error
  • KMS deletion started
  • KMS deletion error
  • KMS deletion completed
  • KMS encryption error
  • KMS encryption completed
  • KMS decryption error
  • KMS decryption completed
  • KMS signing error
  • KMS signing completed
  • KMS verification error
  • KMS verification completed
  • KMS data key error
  • KMS data key completed
  • KMS rewrapping error
  • KMS rewrapping completed
  • KMS HMAC generation error
  • KMS HMAC generation completed
  • KMS HMAC verification error
  • KMS HMAC verification completed
Table. Key Management Service – Key event type events

5.1.53 - Direct Connect

Direct Connect event

This is the list of events delivered from the Direct Connect service to ServiceWatch.

Service CategoryServiceSubserviceEvent sourceEvent type
NetworkingDirect ConnectDirect ConnectDirect ConnectDirect Connect
Table. Direct Connect event types

Direct Connect

Event sourceEvent typeEvent
Direct ConnectDirect Connect
  • Direct Connect creation started
  • Direct Connect creation error
  • Direct Connect creation completed
  • Direct Connect update completed
  • Direct Connect deletion started
  • Direct Connect deletion completed
  • Direct Connect deletion error
  • Routing rule creation started
  • Routing rule creation error
  • Routing rule creation completed
  • Routing rule deletion started
  • Routing rule deletion error
  • Routing rule deletion completed
Table. Direct Connect - Direct Connect event type event

5.1.54 - Support Center

Support Center event

This is a list of events that the Support Center service forwards to the Support Center.

Service CategoryServiceSubserviceEvent sourceEvent type
ManagementSupport CenterService requestSupportService Request
ManagementSupport CenterContactSupportContact
Table. Support Center Event Types

Service Request

Event sourceEvent typeevent
Support CenterService request
  • Service Request Create End
  • Service Request Set End
  • Service Request Iops Result Set End
Table. Support Center – Service Request Event Type Event

Contact

Event sourceEvent typeEvent
Support CenterContact
  • Inquiry Create End
  • Inquiry Operator Create End
Table. Support Center - Inquiry event type

6 - Release Note

ServiceWatch

2026.05.21
CHANGED Improved date-wise metric comparison feature and Copliot alert search improvement
  • When comparing metrics by date, you can select a period to compare.
    • When viewing the chart of metric comparison results by date, you can select a specific period for comparison.
  • You can easily view the alarm occurrence status through Copilot.
    • You can enter a specific alarm name (or ID) or view the list of recently triggered alarms.
2026.03.19
FEATURE Release of new ServiceWatch features and improvement of existing functions
  • ServiceWatch Service Dashboard Release
    • We provide a service dashboard composed of key metrics for each service.
    • When the service’s resources are created and metric data is collected by ServiceWatch, the service dashboard is automatically generated and can be viewed.
  • Improved ServiceWatch metric search functionality
    • Enhance the indicator search to display results that contain the search term.
    • When searching for indicators, you can specify a period for a particular indicator to see how the indicator’s data changes over multiple periods.
  • ServiceWatch log pattern feature release
    • You can create a log pattern to filter log data collected in ServiceWatch that matches the pattern.
    • For detailed information, refer to the 로그 패턴.
2025.12.16
FEATURE ServiceWatch custom metric feature release
  • Release of ServiceWatch custom metric feature
    • Collecting custom metrics via ServiceWatch Agent
    • Collecting custom metrics via the ServiceWatch API
  • ServiceWatch custom log feature released
    • Collecting custom metrics via ServiceWatch Agent
  • Provide a feature to select the missing data handling method during alarm evaluation.
2025.10.23
NEW ServiceWatch service official version release
  • The official version of ServiceWatch has been released.
    • You can collect and monitor metrics, logs, events, and other data for resources created on the Samsung Cloud Platform.
      • Dashboard: You can check the status of resources through various dashboards provided by ServiceWatch.
      • Notification: You can receive a notification when specific conditions are met.
      • Log: You can view logs collected by ServiceWatch.
      • Event: By using ServiceWatch, you can analyze resource events to quickly identify and resolve issues.
    • The Samsung Cloud Platform services that integrate with ServiceWatch are as follows.
      • Metric Monitoring: Virtual Server, GPU Server, File Storage, Kubernetes Engine, Container Registry, VPC - Internet Gateway, Direct Connect
      • Log Monitoring: Kubernetes Engine
      • Event: Multiple services such as Virtual Server
      • For more details, please refer to ServiceWatch Integrated Service.