ServiceWatch

• 1: Overview
• 1.1: Indicator
• 1.2: Alert
• 1.3: Log
• 1.4: event
• 1.5: ServiceWatch linked service
• 1.6: Custom Metrics and Logs
• 2: How-to guides
• 2.1: Managing Dashboard and Widgets
• 2.2: Alert
• 2.3: Metric
• 2.4: Log
• 2.5: Event
• 2.6: ServiceWatch Agent Using
• 3: API Reference
• 4: CLI Reference
• 5: ServiceWatch Event Reference
• 5.1: ServiceWatch Event
• 5.1.1: Multi-node GPU Cluster
• 5.1.2: MySQL(DBaaS)
• 5.1.3: Global CDN
• 5.1.4: Data Flow
• 5.1.5: GSLB
• 5.1.6: Cloud Control
• 5.1.7: Cloud WAN
• 5.1.8: Object Storage
• 5.1.9: VPC
• 5.1.10: GPU Server
• 5.1.11: Virtual Server
• 5.1.12: Firewall
• 5.1.13: ID Center
• 5.1.14: Microsoft SQL Server(DBaaS)
• 5.1.15: Block Storage(BM)
• 5.1.16: Resource Groups
• 5.1.17: Cloud Functions
• 5.1.18: AI&MLOps Platform
• 5.1.19: Event Streams
• 5.1.20: Security Group
• 5.1.21: Archive Storage
• 5.1.22: API Gateway
• 5.1.23: Load Balancer
• 5.1.24: Data Ops
• 5.1.25: Scalable DB(DBaaS)
• 5.1.26: Cloud LAN-Campus
• 5.1.27: EPAS(DBaaS)
• 5.1.28: PostgreSQL(DBaaS)
• 5.1.29: Logging&Audit
• 5.1.30: Search Engine
• 5.1.31: DNS
• 5.1.32: VPN
• 5.1.33: Secrets Manager
• 5.1.34: Quick Query
• 5.1.35: File Storage
• 5.1.36: CacheStore(DBaaS)
• 5.1.37: Secret Vault
• 5.1.38: Queue Service
• 5.1.39: Kubernetes Engine
• 5.1.40: Config Inspection
• 5.1.41: Cloud LAN-Datacenter
• 5.1.42: Identity Access Management
• 5.1.43: Bare Metal Server
• 5.1.44: ServiceWatch
• 5.1.45: MariaDB(DBaaS)
• 5.1.46: Container Registry
• 5.1.47: Vertica(DBaaS)
• 5.1.48: Backup
• 5.1.49: Organization
• 5.1.50: Cloud ML
• 5.1.51: Certificate Manager
• 5.1.52: Key Management Service
• 5.1.53: Direct Connect
• 5.1.54: Support Center
• 6: Release Note

1 - Overview

Service Overview

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

Features

We provide the following special features.

• Resource Monitoring: Collects and visualizes resource performance metrics (e.g., CPU Usage). 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 an alert policy by setting pre-defined conditions and thresholds, and when the threshold is exceeded, you can receive notifications, allowing you to quickly check and respond to the resource’s 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 need separate management.
• Cost Efficiency: ServiceWatch provides a flexible pricing plan where you pay only for what you use, allowing cost-effective usage. It also offers a free usage tier, so you can try it for free and then expand to paid 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.
  • Alert: Provides an alert function that allows you to check changes in indicators according to user-defined thresholds and provides notifications when thresholds are exceeded.
• Log Monitoring
  • ServiceWatch provides log management functionality. Logs collected from Samsung Cloud Platform services can be stored in log groups for management. You can set log retention policies to manage the log retention period. Additionally, you can view and search log data through the console, and it provides the ability to store log groups in Object Storage.
• ServiceWatch Agent
  • Through ServiceWatch Agent, you can collect detailed metrics on processes, CPU, memory, disk usage, and network performance from Virtual Server, GPU Server, Bare Metal Server, etc. You can also collect GPU performance metrics. Additionally, you can collect logs generated from resources via the Agent. (Scheduled for Dec 2025)
• Event Monitoring
• ServiceWatch can create event rules from system events about changes to resources created in Samsung Cloud Platform, allowing receipt of notifications under specific conditions.

Components

Indicator

Metrics refer to system performance data. By default, basic monitoring is provided on a free metric basis for resources of services linked 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 the systems, applications, and services used in Samsung Cloud Platform services such as Virtual Server resources, Kubernetes Engine, etc.

For detailed information related to logs, see Log.

Event

The event represents a change in the environment in the Samsung Cloud Platform service. The following is an example of an event.

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

For detailed information about the event, please refer to Event.

Dashboard

ServiceWatch will provide pre-built dashboards automatically for each service, and you can also create dashboards manually.

ServiceWatch Agent

ServiceWatch Agent is a software component that collects metrics and logs from Virtual Server, GPU Server, and On-Premises servers, etc. Through this, you can monitor infrastructure and applications more finely than the basic monitoring provided by default.

Constraints

The constraints of ServiceWatch are as follows.

The following is ServiceWatch’s monthly free offering details.

Region-specific provision status

ServiceWatch is available in the following environments.

Preceding Service

There is no preceding service for ServiceWatch.

1.1 - Indicator

Indicator

Metrics are data about system performance. By default, many services provide free metrics for resources (e.g., Virtual Server, File Storage, etc.), which are provided as basic monitoring through ServiceWatch. Detailed monitoring can be used for some 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.

Namespace

A namespace is a logical division used to distinguish and group ServiceWatch metrics. Samsung Cloud Platform service namespaces are mostly used the same as the service name, and can be found in the ServiceWatch Integrated Service List.

For custom metrics, users can define a namespace that distinguishes them from other metrics in ServiceWatch, and can define it via ServiceWatch Agent settings or OpenAPI. Detailed information about custom metrics and logs can be found in Custom Metrics and Logs.

Metric (Metric)

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

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

Basically, the Samsung Cloud Platform service linked with ServiceWatch provides metrics for resources for free. Detailed monitoring for some resources is provided 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 time information indicating the time at which the data point was recorded. Each metric data point consists of a timestamp (time) and data.

The timestamp consists of hours, minutes, seconds, and date.

Metric Retention Period

ServiceWatch metric data is maintained as follows.

• Data points with a collection interval set to 60 seconds (1 minute) can be used until the 15th
• Data points with a collection interval set to 300 seconds (5 minutes) are usable up to day 63
• Data points with a collection interval set to 3600 seconds (1 hour) are usable up to 455 days (15 months).

The data points that were initially collected at a short collection 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 store them separately via the File Download or Export to Object Storage functions.

Dimensions(Dimensions)

Key-value pair that serves as a unique identifier for the metric, allowing classification and filtering of data points.

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

Collection Cycle

It refers to the cycle of collecting data points for each service’s metrics, and is provided at the collection cycle predefined by each service.

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

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

Statistics

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

The provided statistics are total, 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 period. The aggregation period can be chosen from 1 minute, 5 minutes, 15 minutes, 30 minutes, 1 hour, 3 hours, 6 hours, 12 hours, or 1 day, and the default is 5 minutes. The aggregation period is closely related to the collection interval of metric data points, and to obtain correct aggregation results, the aggregation period must be longer than or equal to the collection interval.

For example, if you select average for the statistic, choose an aggregation period of 5 minutes, and select a metric with a collection interval of 1 minute, data points are collected at 1‑minute intervals 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 that a normal 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 this 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 is because aggregating the metric data after downsampling takes time, which can cause aggregation delays.

Alert

When creating an alert policy, you can evaluate a single metric over the entered evaluation range, and if it meets the condition set based on the threshold, you can provide the user with an alert notification.

The alert status is classified as Alert(Alert), Normal(Normal), Insufficient data(No data).

• Alert(Alert): when the indicator meets the set conditions
• 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, if the alarm evaluation deviates from the condition, the alarm status changes back to Normal.

For detailed information about alerts, please refer to the Alert item.

Basic Monitoring and Detailed Monitoring

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

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

Detailed monitoring is only available for some 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 of Virtual Server has a collection interval of 5 minutes. When detailed monitoring is enabled, the metrics provided by default monitoring are collected at a 1‑minute interval instead of 5 minutes.

The following includes services and guides that provide detailed monitoring.

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 increased load.

• Alert Policy
  • Alarm Status
  • Alert Evaluation
    • Evaluation Scope
    • Condition
  • Alert Notification
  • How to handle missing data during alarm evaluation
• Alarm History

Alert Policy

Alert policies can monitor metrics of the same Account and evaluate alerts for a single metric. These alert policies compare the specified threshold and metric conditions, and send notifications when the conditions are met.

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

When you enable the alert policy, evaluation of the alert policy begins, and according to the set conditions, the alert status changes to Alert, and a notification is sent each time the alert status changes.

The alarm policy status allows you to check whether the alarm policy is enabled/disabled.

You can set alert levels for the alert policy. Depending on the alert level, the alert color (red/pink/purple) is expressed differently so that the levels can be visually distinguished by color. You can filter according to the alert policy’s alert level and retrieve the alert policy by each alert level.

Alarm Status

Alert status changes according to the alert evaluation of the alert policy. Alert status is divided into three states: Normal (Normal), Insufficient data (Insufficient data), Alert (Alert).

Alert Evaluation

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 counts, 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 counts, the evaluation interval is 30 minutes.

Evaluation Scope

The evaluation scope of the alarm policy is the evaluation time range for alarm evaluation.

• It is recommended to set it to the indicator’s collection interval or a multiple of the collection interval.
• You can input up to 604,800 (7 days) seconds.

Condition

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

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

Alarm Notification

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

Method for handling missing data during alarm evaluation

Some resources may not be able to send metric data to ServiceWatch under certain conditions. For example, if a specific resource is inactive or does not exist, it will not be sent to ServiceWatch. If metrics are not collected for a certain period, the alarm state will be changed to Insufficient data by the alarm evaluation.

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

• Ignore: Maintain the current alarm state. (default)
• Missing: Treat missing data points as missing. If all data points within the evaluation range are missing, the alarm state switches to Insufficient data state.
• Breaching: Treat as satisfying the threshold condition for missing data points.
• Not breaching: Process as normal for missing data points that do not satisfy the threshold condition.

Alert History

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

1.3 - Log

Log

ServiceWatch logs allow you to monitor, store, and access log files collected from the resources of the services that provide logs.

Log Group

A log group is a container for log streams that share the same retention policy settings, each log stream must belong to one log group, for example, if there are separate log streams for the logs of each Kubernetes Engine cluster, the log streams can be bundled into one log group named /scp/ske/{cluster name}.

Log Retention Policy

The log retention policy allows you to set the period during which log events are stored in ServiceWatch. Log events that have 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, and it is set in units of days.

Log Stream

A log stream is a collection of log events that are ordered by the time they occurred, from the same source, for example, all log events occurring in a specific Kubernetes Engine cluster can constitute one log stream.

Log Event

A log event is an individual record of a log that occurs from a resource. The log event record includes two properties: a timestamp of when the event occurred and a log message. Each message must be encoded in UTF-8.

Export log group

You can export log data from the log group to Object Storage for log archiving and log analysis, and you can also export log data within the same account to the log group.

To start logging group export, you must create an Object Storage bucket to store log data.

Exporting a log group can take a long time depending on the amount of log, when exporting a log group, you can specify a specific stream within the log group, or specify a time range to reduce the time it takes to export the log group.

Exporting a log group can only be executed once at a time for the same Account. To run another log group export, the current export task in progress must be completed.

1.4 - event

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

Most events generated in Samsung Cloud Platform services are received by ServiceWatch. Events of each service can be viewed and processed in the ServiceWatch of the same Account.

Refer to the list of services that send events via ServiceWatch and the events those services send in the ServiceWatch Event Reference.

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 set 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 specifies which events are delivered to which targets.

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

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

• Event rules basically allow you to specify a notification recipient to receive alerts when an event occurs.
• The event rules are planned to be expanded to include multiple services of the Samsung Cloud Platform as targets for receiving events when events occur. (Planned for 2026)

To create an event rule, please refer to How-to Guides > Creating Event Rules.

Event Source

ServiceWatch can select the event source as the Samsung Cloud Platform service name. You can select the service name of the event you want to receive as the event source.

Event Type

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

The following are the event types of Virtual Server.

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

Event

The event can select all events that occur from the event type of the event source, and can select specific events.

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

For other events available in ServiceWatch, see ServiceWatch Event.

Applied Resources

Set the event pattern for selected events on all resources or specific resources.

Event Pattern

If you select all event sources, event types, events, and applied resources, the event pattern setting for the event rule will be completed.

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

{
	"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}"
	]
}

To create an event rule, please refer to How-to Guides > Creating Event Rules.

Event Notification

If the event pattern is satisfied, an alert is sent to the notification recipient set in the event rule.

1.5 - ServiceWatch linked service

You can check the services linked with ServiceWatch.

Metrics and Log Monitoring

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

Event

Below you can check the service that links ServiceWatch with events.

1.6 - Custom Metrics and Logs

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

There are two ways to collect custom metrics and logs.

First, you can install the ServiceWatch Agent directly on the resource, set the resources to be collected, and collect them.
The second is that you can collect custom metrics and logs through the OpenAPI/CLI provided by ServiceWatch.

ServiceWatch Agent

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

ServiceWatch Agent Constraints

ServiceWatch Agent Network Environment

ServiceWatch Agent is designed to collect data using OpenAPI by default, so to install and use it on server resources, external communication via the Internet must be possible. Please create an Internet Gateway in the VPC where the resources are located and set a NAT IP on the server resources so that they can communicate with the outside.

ServiceWatch Agent Supported OS Image

The OS images available for ServiceWatch Agent are as follows.

Provides the same as the OS Image provided by Virtual Server. Please refer to Virtual Server > OS Image provided version.

Quick Guide for Using ServiceWatch Agent

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

Node Exporter Installation and Configuration

1. Refer to Node Exporter installation and install Node Exporter on the server for collecting custom metrics.
   • If you install Node Exporter, you can collect OS metrics through Node Exporter in addition to the metrics provided by ServiceWatch’s default monitoring.
2. ServiceWatch Agent Settings refer to and after downloading the ServiceWatch_Agent zip file, configure and run the ServiceWatch Manager.
   • Refer to the examples/os-metric-min-examples folder in the zip file to set at least two metrics and run the ServiceWatch Agent.

ServiceWatch Custom Metrics and Logs API

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

Custom metric data and custom logs can be delivered to ServiceWatch via ServiceWatch OpenAPI/CLI, allowing you to view visualized information in the Console.

Create Custom Metric Metadata

To collect metric data generated from user resources or applications, rather than metrics provided by Samsung Cloud Platform services (e.g., Virtual Server), into ServiceWatch, you need to create custom metric metadata.

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

Create Custom Metrics

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

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

For detailed information on creating custom metric data, refer to CreateCustomMetrics.

Indicator Data Query

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

For detailed information on metric data retrieval, refer to ListMetricInfos and ListMetricData.

Log Stream Creation

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 to be delivered to ServiceWatch.

For detailed information on creating a log stream, refer to CreateCustomLogStream.

Log Event Creation

To collect custom logs, after creating log groups and log streams, 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

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

Using the Dashboard

You can monitor resources from the ServiceWatch dashboard detailed information screen.

To check the detailed information of the dashboard, follow the next procedure.

1. All services > Management > ServiceWatch menu is clicked. It moves to the Service Home page.
2. Service Home page, click the Dashboard > Dashboard List menu. Move to the Dashboard List page.
3. Dashboard List page, click the dashboard for the resource you want to monitor. It moves to the Dashboard Detail page.
4. Dashboard Details page where you can select the period and time zone to monitor, and monitor resources through widgets.

Setting up dashboard favorites

You can bookmark frequently used dashboards to easily move to the corresponding dashboard from the Service Home page of ServiceWatch.

To bookmark the dashboard, follow the following procedure.

1. All services > Management > ServiceWatch menu is clicked. It moves to the Service Home page.
2. Service Home page, click the Dashboard > Dashboard List menu. Move to the Dashboard List page.
3. Dashboard List page, check the favorite icon of the dashboard to be bookmarked. Click the dashboard to check the detailed information. It moves to the Dashboard Details page.

• Bookmarked dashboards will be added to the bottom of the Dashboard > Dashboard Bookmark menu and the Dashboard Bookmark section of the Service Home page.

Widget Details View

You can expand the widgets in the dashboard to check them individually.

To view individual widgets enlarged, follow the next procedure.

1. All services > Management > ServiceWatch menu is clicked. It moves to the Service Home page.
2. Service Home page, click the Dashboard > Dashboard List menu. Move to the Dashboard List page.
3. Dashboard List page, click the dashboard for the resource you want to monitor. It moves to the Dashboard Details page.
4. Dashboard Details page, click the Widget Enlarged View button to enlarge and check the widget. A Metric Details popup window for the corresponding widget will be opened.

Check Alert History

You can check the alert history for the metrics registered on the ServiceWatch dashboard.

To check the alert history, follow the following procedure.

1. All services > Management > ServiceWatch menu is clicked. It moves to the Service Home page.
2. Service Home page, click the Alert > Alert History menu. It moves to the Alert History page.
3. Alert History page where you can check the alert history.

Monitoring metrics

You can check and monitor the metrics available on ServiceWatch.

To check the metrics, follow the next procedure.

1. All services > Management > ServiceWatch menu is clicked. It moves to the Service Home page.
2. Service Home page, click the metric menu. It moves to the metric page.
3. Metric page, select the metrics to be monitored from the list of metrics. The monitoring chart for the selected metric will be displayed in the Selected Metric area at the bottom.

4. Selected metric area, check the monitoring chart.

Log Monitoring

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

To check the log monitoring data, follow the following procedure.

1. All services > Management > ServiceWatch menu is clicked. It moves to the Service Home page.
2. Service Home page, click the Log > Log Group menu. It moves to the Log Group List page.
3. Log Group List page, click the log group name to check the detailed information. It moves to the Log Group Details page.
4. Log Group Details page, click the Log Stream tab. The Log Stream list will be displayed.
5. Log Stream Click the log stream name to check the detailed information in the Log Stream list. It moves to the Log Stream Details page.

• Clicking the All Log Streams Query button at the top of the log stream list moves to the All Log Streams Detail page.

Event notification reception

You can create system event rules for changes to resources created on the Samsung Cloud Platform and receive them as notifications.

2.1 - Managing Dashboard and Widgets

You can create and manage a dashboard to monitor the resources of the services being used in the Samsung Cloud Platform Console.

Creating a dashboard

You can create a dashboard of ServiceWatch.

To create a dashboard, follow the next procedure.

1. All services > Management > ServiceWatch menu is clicked. It moves to the Service Home page.
2. Service Home page, click the Dashboard > Dashboard List menu. Move to the Dashboard List page.
3. Dashboard List page, click the Create Dashboard button.
4. Please enter the name of the dashboard.

• The name of the dashboard should be entered within 34 characters using English, numbers, and special characters (-_).

5. Add a widget to compose the dashboard. A corresponding popup window opens according to the method of adding a widget.

• Add individual widgets: You can add a single widget combined with metrics and resources. When you click the button, the Add individual widgets popup window opens.

• Multiple Widget Addition: You can add multiple widgets at once by selecting the desired resources by metric unit. When you click the button, the Multiple Widget Addition popup window opens.

• Dashboard Import: You can import widgets from the dashboard registered in ServiceWatch. When you click the button, the Dashboard Import popup window opens.

5. Click the Complete button on the widget add popup window. The widget will be added to the dashboard on the dashboard creation page.
6. After checking the added widget, click the Complete button. A pop-up window announcing the creation of the dashboard will open.
7. Confirm button should be clicked. Dashboard creation will be completed.

Check the dashboard

Dashboard List page where you can check the information of the selected dashboard.

To check the dashboard, follow the next procedure.

1. All services > Management > ServiceWatch menu is clicked. It moves to the Service Home page.
2. Service Home page, click the Dashboard > Dashboard List menu. Move to the Dashboard List page.
3. Dashboard List page, click the dashboard to check the detailed information. It moves to the Dashboard Details page.

Managing Dashboard

Dashboard Details page where you can modify or manage dashboard information and widgets.

Modifying the dashboard

You can modify the name of the dashboard or change the widget composition.

To modify the dashboard, follow the following procedure.

1. All services > Management > ServiceWatch menu is clicked. It moves to the Service Home page.
2. Service Home page, click the Dashboard > Dashboard List menu. Move to the Dashboard List page.
3. Dashboard List page, click the dashboard to check the detailed information. It moves to the Dashboard Details page.
4. Dashboard Details page’s top right Edit button is clicked. It moves to the Dashboard Edit page.
5. After modifying the information or widgets on the dashboard, click the Save button.

   Classification	Detailed Description
   Dashboard Name	The name of the dashboard can be modified Enter within 3~40 characters using English, numbers, and special characters (-_) Cannot use the existing registered dashboard name
   Widget Name	Widget Name Editable Use English, numbers, spaces, and special characters (-_.|) to enter within 3 ~ 255 characters
   Widget Management	When the mouse cursor is placed on the widget, the management button is displayed on the right side of the widget border Edit: Widget modification is possible in the Widget Edit popup window, where you can modify the widget’s metrics and resources For more information on widget editing, see Individual Widget Editing in Widget Management Duplicate: Duplicate the current widget and add it to the dashboard Delete: Delete the current widget from the dashboard Expand: Expand the size of the current widget to display Shrink: If expanded, clicking again will shrink the widget size
   Add Widget	Add a new widget to the dashboard Add Individual Widget: Add a single widget combined with metrics and resources Add Multiple Widgets: Select the desired resources by metric unit to add multiple widgets at once Load Dashboard: Load widgets from other dashboards and add them For more information on how to add widgets, see Create a Widget

   Table. Dashboard Modification Items

Check detailed dashboard information

You can check detailed information about the dashboard.

To check the detailed information of the dashboard, please follow the following procedure.

1. All services > Management > ServiceWatch menu is clicked. It moves to the Service Home page.
2. Service Home page, click the Dashboard > Dashboard List menu. It moves to the Dashboard List page.
3. Dashboard List page, click the dashboard to check the detailed information. It moves to the Dashboard Details page.
4. Dashboard Details page’s upper right corner More > Details button click. Dashboard Details popup window opens.

Check the dashboard source code

You can check the source code of the dashboard.

To check the source code of the dashboard, follow the next procedure.

1. All services > Management > ServiceWatch menu is clicked. It moves to the Service Home page.
2. Service Home page, click the Dashboard > Dashboard List menu. It moves to the Dashboard List page.
3. Dashboard List page, click the dashboard to check the detailed information. It moves to the Dashboard Details page.
4. Dashboard Details page’s upper right corner click the More > View Source button. Dashboard Source View popup window opens.

Dashboard duplication

You can currently replicate a widget on the dashboard and add it to another dashboard.

To replicate the dashboard, follow the following procedure.

1. All services > Management > ServiceWatch menu is clicked. It moves to the Service Home page.
2. Service Home page, click the Dashboard > Dashboard List menu. It moves to the Dashboard List page.
3. Dashboard List page, click the dashboard to check the detailed information. It moves to the Dashboard Details page.
4. Dashboard Details page’s upper right corner More > Duplicate button, click. Dashboard Duplicate popup window opens.
5. Select the dashboard replication method and enter the required information. The required information varies depending on the replication method.

6. When the essential information input is complete, click the completed button. A popup window announcing the dashboard replication will open.
7. Click the Confirm button on the popup window. The dashboard replication task will be completed.

Delete Dashboard

You can delete the dashboard that is not used.

To delete the dashboard, follow the following procedure.

1. All services > Management > ServiceWatch menu is clicked. It moves to the Service Home page.
2. Service Home page, click the Dashboard > Dashboard List menu. Move to the Dashboard List page.
3. Dashboard List page, select the checkbox of the dashboard to be deleted, and then click the Delete button. A popup window announcing the deletion of the dashboard will open.

• You can delete multiple dashboards at the same time.
• Dashboard Details page’s top right corner has More > Delete button to delete individually.

4. Enter delete in the delete confirmation input area, then click the confirm button. The dashboard will be deleted.

Managing widgets

Dashboard Details page where you can modify or manage widgets.

Modifying widgets

You can modify the widget’s metrics and resources.

To modify the widget, follow the following procedure.

1. All services > Management > ServiceWatch menu, click. It moves to the Service Home page.
2. Service Home page, click the Dashboard > Dashboard List menu. Move to the Dashboard List page.
3. Dashboard List page, click the dashboard you want to modify the widget. It moves to the Dashboard Details page.
4. Dashboard Details page, click the More > Edit Widget button located at the top right of the widget you want to modify. The Edit Widget popup window opens.
5. After modifying the widget’s metrics and resources, click the Confirm button. The widget modification will be completed.

Widget duplication

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

To replicate a widget, follow the following procedure.

1. All services > Management > ServiceWatch menu is clicked. It moves to the Service Home page.
2. Service Home page, click the Dashboard > Dashboard List menu. Move to the Dashboard List page.
3. Dashboard List page, click the dashboard to replicate. It moves to the Dashboard Details page.
4. Dashboard Details page, click the More > Widget Duplicate button located at the top right of the widget to be duplicated. The Widget Duplicate popup window opens.
5. Select the widget replication method and enter the required information. The required information varies depending on the replication method.

6. When the required information input is complete, click the completed button. A popup window announcing the addition of a widget will open.
7. Click the Confirm button on the popup window. The widget will be replicated and added to the corresponding dashboard.

Downloading widget files

You can download widget information in the form of a file.

To download widget information, follow the next procedure.

1. All services > Management > ServiceWatch menu, click. It moves to the Service Home page.
2. Service Home page, click the Dashboard > Dashboard List menu. Move to the Dashboard List page.
3. Dashboard List page, click the dashboard to download widget information. It moves to the Dashboard Details page.
4. Dashboard Details page, click the More > File Download button located at the top right of the widget to download the widget information. The File Download popup window opens.
5. Select the file download method, then click the Confirm button. The download will start.

• The download methods can be selected simultaneously.

Widget Metric Details

Widget’s resource and metric information can be checked on the metric page

To view the widget metrics on the metrics page, follow these procedures.

1. All services > Management > ServiceWatch menu is clicked. It moves to the Service Home page.
2. Service Home page, click the Dashboard > Dashboard List menu. Move to the Dashboard List page.
3. Dashboard List page, click the dashboard to check the widget metrics. It moves to the Dashboard Details page.
4. Dashboard Details page, click the More > View Metrics button located at the top right of the widget to be checked on the Metrics page. It moves to the Metrics page.

• The resource and metric information of the selected widget is automatically set and displayed on the Metrics page.

Widget source information

You can check the source code of the dashboard.

To check the source code of the dashboard, follow the following procedure.

1. All services > Management > ServiceWatch menu is clicked. It moves to the Service Home page.
2. Service Home page, click the Dashboard > Dashboard List menu. Move to the Dashboard List page.
3. Dashboard List page, click the dashboard to check the detailed information. It moves to the Dashboard Details page.
4. Dashboard Details page, click the More > View Source button located at the top right of the widget to check the source code. The Widget Source View popup window opens.

2.2 - Alert

In ServiceWatch, you can set threshold criteria for the metrics to be monitored, and create and manage alert policies so that an alert notification is generated when the set conditions are met.

Create Alert Policy

You can create an alert policy for a metric and set the alert triggering criteria.

To create an alert policy, follow these steps.

1. Click the All Services > Management > ServiceWatch menu. Go to the Service Home page.
2. Click the Alert > Alert Policy menu on the Service Home page. You will be taken to the Alert Policy List page.
3. Alert Policy List page, click the Create Alert Policy button. It navigates to the Create Alert Policy page.
4. Basic Information Input area, after entering the name and description of the alert policy, click the Select Metric button. The Select Metric popup opens.
5. After selecting the metric to create an alert policy in the Metric Selection popup, click the Confirm button. The Metric and Condition Settings area will be displayed.

6. Indicator and Condition Settings area, set the threshold values for alarm generation.

7. In the Notification Settings area, select the user who will receive notifications when an alarm occurs.
   • Only users with login history (users who have registered email or mobile phone number) can be added as notification recipients.
   • You can add up to 100 notification recipients.

8. In the Add Additional Information area, after adding tag information, click the Complete button. A popup window notifying the creation of the alert policy opens.
9. Confirm 버튼을 클릭하세요. 경보 정책 생성이 완료됩니다.

Check detailed alarm policy information

You can view and manage detailed information about the alarm policy.

To view detailed information about the alert policy, follow the steps below.

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. It navigates to the Alert Policy List page.

• Click the Alert Stage button displayed in the Alert Policy menu to filter and view only the list of alert policies for that stage.

3. Alert Policy List page, click the alert policy name to view detailed information. You will be taken to the Alert Policy Details page.

Detailed Information

Alarm Policy List page, you can view the basic information and metric information of the selected alarm policy.

Notification

You can check the notification recipients of the selected alert policy on the Alert Policy List page.

Alert History

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

Tag

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

Work History

Alert Policy List page allows you to view the operation history of the selected alert policy.

Edit Alarm Policy

You can modify the target metrics and policy settings of the alert policy.

To modify the alert policy, follow the steps below.

1. Click the All Services > Management > ServiceWatch menu. Go to the Service Home page.
2. Click the Alert > Alert Policy menu on the Service Home page. You will be taken to the Alert Policy List page.
3. Click the alert policy name on the Alert Policy List page to view detailed information. It moves to the Alert Policy Details page.
4. Alarm Policy Details page’s Detailed Information tab, click the Edit button of Metric Information. Edit Metric Information popup opens.
5. After modifying the indicator information and policy settings, click the Confirm button. A popup window notifying the indicator modification will open.
   • For detailed information about metric modification items, please refer to Create Alert Policy.
6. Confirm 버튼을 클릭하세요. 경보 정책 수정이 완료됩니다.

Delete alert policy

You can delete unused alarm policies.

To delete the alert policy, follow these steps.

1. All Services > Management > ServiceWatch Click the menu. Navigate to the Service Home page.
2. Service Home page, click the Alert > Alert Policy menu. Navigate to the Alert Policy List page.
3. Alert Policy List on the page, after selecting the checkbox of the alert policy to delete, click the Delete button. A popup notifying the alert policy deletion will open.
   • You can delete multiple alert policies at the same time.
   • 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. Confirm 버튼을 클릭하세요. 경보 정책이 삭제됩니다.

2.3 - Metric

The user can monitor and manage metrics for service resources in the Samsung Cloud Platform Console.

Check the metric

You can check the metrics available on ServiceWatch.

To check the metrics, follow the next procedure.

1. All services > Management > ServiceWatch menu is clicked. It moves to the Service Home page.
2. Service Home page, click the metric menu. It moves to the metric page.
3. Metric page’s metric list, please check the metric.

Managing Metric Charts

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

Add as a widget

To check the metric, follow the next procedure.

1. All services > Management > ServiceWatch menu is clicked. It moves to the Service Home page.
2. Service Home page, click the metric menu. It moves to the metric page.
3. Metric page, select the metric to be monitored from the list of metrics. The monitoring chart for the selected metric will be displayed in the Selected Metric area at the bottom.
4. Selected Metric area’s monitoring chart, set the table area, then click the More > Add Widget button. The Add Widget popup window opens.
5. Select the widget addition method and enter the required information. The required information varies depending on the addition method.

6. When the required information input is complete, click the completed button. A pop-up window announcing the addition of the widget will open.
7. Click the Confirm button on the popup window. A widget will be added to the corresponding dashboard.

Monitoring chart file download

You can download the monitoring chart information in the form of a file.

To download the monitoring chart information, follow the next procedure.

1. All services > Management > ServiceWatch menu is clicked. It moves to the Service Home page.
2. Service Home page, click the metric menu. It moves to the metric page.
3. Metric page, select the metrics to be monitored from the metric list. The monitoring chart for the selected metric will be displayed in the Selected Metric area below.
4. Selected metric area’s monitoring chart, set the table area, then click the More > File Download button. The File Download popup window will open.
5. Select the file download method, then click the Confirm button. The download will start.

• The download methods can be selected simultaneously.

Export to Object Storage

You can store monitoring chart data in Object Storage.

To store monitoring chart data in Object Storage, follow the next procedure.

1. All services > Management > ServiceWatch menu is clicked. It moves to the Service Home page.
2. Service Home page, click the Metrics menu. It moves to the Metrics page.
3. Metric page, select the metric to be monitored from the metric list. The monitoring chart for the selected metric will be displayed in the Selected Metric area at the bottom.
4. Selected metric area’s monitoring chart, set the table area, then click the More > Object Storage Export button. The Object Storage Export popup window will open.
5. After selecting a bucket to store the data, click the Complete button. A popup window announcing data storage will open.
6. Click the Confirm button in the popup window. Data export will begin.

Monitoring chart source view

You can check the source code of the monitoring chart.

To check the source code of the monitoring chart, follow the next procedure.

1. All services > Management > ServiceWatch menu, click. It moves to the Service Home page.
2. Service Home page, click the Metrics menu. It moves to the Metrics page.
3. Metric page, select the metrics to be monitored from the list of metrics. The monitoring chart for the selected metric will be displayed in the Selected Metric area below.
4. Selected Metric area’s monitoring chart, set the table area, then click the More > View Source button. The Widget Source View popup window opens.

2.4 - Log

ServiceWatch allows you to create and manage log groups to generate alert notifications when the set conditions are met by setting threshold criteria for the metrics to be monitored.

Create a log group

You can create a log group for the metric.

To create a log group, follow these procedures.

1. All services > Management > ServiceWatch menu is clicked. It moves to the Service Home page.
2. Service Home page, click the Log > Log Group menu. It moves to the Log Group List page.
3. Log Group List page, click the Create Log Group button. Move to the Create Log Group page.
4. Enter the basic information and tag information required for log group creation, and then click the Complete button. A pop-up window announcing the creation of the log group will open.

5. Confirm button will be clicked. Log group creation will be completed.

Log group detailed information check

You can check and manage detailed information about the log group.

To check detailed information about the log group, follow the next procedure.

1. All services > Management > ServiceWatch menu is clicked. It moves to the Service Home page.
2. Service Home page, click the Log > Log Group menu. It moves to the Log Group List page.
3. Log Group List page, click the log group name to check the detailed information. It moves to the Log Group Details page.

Detailed Information

Log Group List page where you can check the basic information and log group information of the selected log group.

Log Stream

Log Group List page where you can check the log stream of the selected log group.

Tag

Log Group List page where you can check the tag information of the selected log group, and add, change or delete it.

Work History

Log Group List page where you can check the operation history of the selected log group.

Managing log streams

You can create and manage log streams.

Creating a log stream

You can create a new log stream in the log group.

To create a hog stream, follow the next procedure.

1. All services > Management > ServiceWatch menu is clicked. It moves to the Service Home page.
2. Service Home page, click the Log > Log Group menu. It moves to the Log Group List page.
3. Log Group List page, click the log group name to check the detailed information. It moves to the Log Group Details page.
4. Log Group Details page, click the Log Stream tab. The list of log streams will be displayed.
5. Create Log Stream button, the Create Log Stream popup window opens.
6. Log Stream Name을 입력한 후, Confirm 버튼을 클릭하세요. Log stream creation will be completed.

• The name should be entered within 3 ~ 512 characters using English and numbers.

Log Stream Detailed Information Check

You can check and manage detailed information about the log stream.

To check detailed information about the log stream, follow the next procedure.

1. All services > Management > ServiceWatch menu is clicked. It moves to the Service Home page.
2. Service Home page, click the Log > Log Group menu. It moves to the Log Group List page.
3. Log Group List page, click the log group name to check the detailed information. It moves to the Log Group Details page.
4. Log Group Details page, click the Log Stream tab. The Log Stream list will be displayed.
5. Log Stream Click the log stream name to check the detailed information in the Log Stream list. It moves to the Log Stream Details page.

• Clicking the All Log Streams Query button at the top of the log stream list will move to the All Log Streams Details page.

  Classification	Detailed Description
  Excel Download	Possible to download log stream history as an Excel file
  Time Stamp List	Message List by Time Stamp Period Selection, User Time Zone, message input can be used for filtering

  Table. Log Group Details - Log Stream Details Item

Deleting log streams

You can delete unused log streams.

To delete a log stream, follow these procedures.

1. All services > Management > ServiceWatch menu is clicked. It moves to the Service Home page.
2. Service Home page, click the Log > Log Group menu. Move to the Log Group List page.
3. Log Group List page, click the log group name to check the detailed information. It moves to the Log Group Details page.
4. Log Group Details page, click the Log Stream tab. The list of log streams will be displayed.
5. Select the checkbox of the log stream to be deleted from the log stream list, then click the More > Delete button. A popup window notifying log stream deletion will be opened.

• You can delete multiple log streams at the same time.
• You can also delete them individually by clicking the delete button at the far right end of each log stream.

4. Confirm button will be clicked. The log group will be deleted.

Export log group

You can store log group data in Object Storage.

To store log group data in Object Storage, follow these procedures.

1. All services > Management > ServiceWatch menu is clicked. It moves to the Service Home page.
2. Service Home page, click the Log > Log Group Export menu. It moves to the Log Group Export List page.
3. Log Group Export List page, click the Log Group Export button. Move to the Log Group Export page.

5. After selecting a bucket to store the data, click the Complete button. A pop-up window notifying data storage will open.
6. Click the Confirm button in the popup window. Data export will begin.

• The progress can be checked on the log group export list page.

Delete log group

You can delete unused log groups.

To delete a log group, follow these procedures.

1. All services > Management > ServiceWatch menu is clicked. It moves to the Service Home page.
2. Service Home page, click the Log > Log Group menu. Move to the Log Group List page.
3. Log Group List page, select the checkbox of the log group to be deleted, and then click the Delete button. A popup window announcing the deletion of the log group will open.

• You can delete multiple log groups at the same time.
• You can also delete them individually by clicking the Delete button at the far right of each log group or the Delete Log Group button on the corresponding Log Group Details page.

4. Confirm button will be clicked. The log group will be deleted.

2.5 - Event

In ServiceWatch, you can check and process events generated by the Samsung Cloud Platform service.

Create Event Rules

You can create event rules to receive notifications when events occur.

To create an event rule, follow these steps.

1. Click the All Services > Management > ServiceWatch menu. Navigate to the Service Home page.
2. Service Home page, click the Event Rules menu. Navigate to the Event Rules List page.
3. Click the Create Event Rule button on the Event Rule List page. You will be taken to the Create Event Rule page.
4. Basic Information Input Enter the name and description of the event rule in the area.
5. Event Pattern Settings Please set the required information in the area. The configured event pattern is entered in JSON code format in Event Pattern Settings Status.

6. Notification Settings Select the user(s) to receive the notification when an event occurs in the area.
   • Only users with login history (users who have registered email or mobile phone number) can be added as notification recipients.
   • Notification recipients can be added up to a maximum of 100.

7. Additional Information Input area, after adding tag information, click the Complete button. A popup notifying the creation of an event rule will open.
8. 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. Navigate to the Service Home page.
2. Click the Event Rules menu on the Service Home page. Navigate 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.

Detailed Information

On the Event Rule List page, you can view the basic information and event rule information of the selected event rule.

Notification

You can check the notification recipients of the selected event rule on the Event Rule List page.

Tag

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

Work History

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

Edit event pattern

You can modify the event pattern.

To modify the event pattern, follow the steps below.

1. All Services > Management > ServiceWatch Click the menu. Service Home page will be displayed.
2. Service Home page, click the Event Rule menu. Navigate to the Event Rule List page.
3. Event Rule List page, click the event name to edit the event pattern. Event Rule Details page will be opened.
4. Click the Edit button in the Event Pattern Settings on the Event Rule Details page. The Edit Event Pattern popup window opens.
5. After modifying the event pattern settings, click the Confirm button. A popup notifying the event pattern modification will open.
   • For detailed information on event pattern modification items, refer to Create Event Rule.
6. Confirm Click the button. The event pattern modification is complete.

Delete event rules

You can delete unused event rules.

To delete the event rules, follow the steps below.

1. All Services > Management > ServiceWatch Click the menu. Service Home page will be displayed.
2. Click the Event Rules menu on the Service Home page. You will be taken to the Event Rules List page.
3. On the Event Rule List page, after selecting the checkbox of the event rule to delete, click the Delete button. A popup notifying the deletion of the event rule will open.
   • You can delete multiple event rules at the same time.
   • 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. Confirm Click the button. The event rule will be deleted.

2.6 - ServiceWatch Agent Using

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

ServiceWatch Agent

The agents that need to be installed on the server for collecting ServiceWatch’s custom metrics and logs can be broadly divided into two types. Prometheus Exporter and Open Telemetry Collector.

Open Telemetry Collector preset for ServiceWatch

Install according to the steps below to use the Open Telemetry Collector for collecting ServiceWatch metrics and logs on the server.

1. Download the Agent file from the URL where the Agent file can be downloaded for ServiceWatch.

wget [ServiceWatch Agent file download URL]

wget [ServiceWatch Agent file download URL]

2. The Open Telemetry Collector Agent file for ServiceWatch can be checked as follows.
   • Extract the Agent file for ServiceWatch.
     Sample Code Download

     Copy Code

     Color mode

     unzip ServiceWatch_Agent.zip

     unzip ServiceWatch_Agent.zip

   • If the environment using ServiceWatch Agent is Linux OS, you must grant execution permission as below.
     Sample Code Download

     Copy Code

     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

     Category	Detailed description
     examples	Example configuration file folder. Each folder contains example files agent.json, log.json, metric.json os-metrics-min-examples: Example of minimal metric configuration using Node Exporter os-metrics-all-examples: Example of memory/filesystem Collector metric configuration using Node Exporter gpu-metrics-min-examples: Example of minimal metric configuration using DCGM Exporter gpu-metrics-all-examples: Example of major metric configuration using DCGM Exporter
     otelcontribcol_linux_amd64	Open Telemetry Collector for Linux for ServiceWatch
     otelcontribcol_windows_amd64.exe	Open Telemetry Collector for Windows for ServiceWatch
     servicewatch-agent-manager-linux-amd64	ServiceWatch Agent Manager for Linux
     servicewatch-agent-manager-windows-amd64.exe	ServiceWatch Agent Manager for Windows

     Table. Agent file configuration for ServiceWatch

3. Define the Agent configuration file of ServiceWatch Agent Manager for the Open Telemetry Collector for ServiceWatch.

   Category	Detailed description
   namespace	Custom namespace for custom metrics A namespace is a logical separation used to distinguish and group metrics, designated as a custom metric to differentiate custom metrics. The namespace must be 3 to 128 characters long, consisting of letters, numbers, spaces, and special characters (_-/), and must start with a letter.
   accessKey	IAM authentication key Access Key
   accessSecret	IAM authentication key Secret Key
   resourceId	Resource ID of the server on Samsung Cloud Platform Example: Resource ID of Virtual Server
   openApiEndpoint	ServiceWatch OpenAPI Endpoint by region/offering Example: https://servicewatch.region.offering.samsungsdscloud.com The region and offering information can be found in the Samsung Cloud Platform Console access URL
   telemetryPort	ServiceWatch Agent’s Telemetry Port Usually uses port 8888. Change required if port 8888 is already in use

   Table. agent.json configuration file items
   Sample Code Download

   Copy Code

   Color mode

   {
      "namespace": "swagent-windows",     # Custom namespace for custom 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. Change if port 8888 is in use)
   "}

   {
      "namespace": "swagent-windows",     # Custom namespace for custom 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. Change if port 8888 is in use)
   "}

4. Define the metric configuration file for collecting metrics for ServiceWatch.

   • If you want to collect metrics through the Agent, set metric.json.

     Category	Detailed description
     prometheus > scrape_configs > targets	Endpoint of metric collection target For a server, install Prometheus Exporter on the same server, so set this endpoint Example: localhost:9100
     prometheus > scrape_configs > jobName	Job Name setting. Usually set to the type of Prometheus Exporter used for metric collection Example: node-exporter
     metricMetas > metricName	Set the name of the metric to be collected. The metric name must be 3 to 128 characters long, including English letters, numbers, and special characters (_), and must start with an English letter. Example: node_cpu_seconds_total
     metricMetas > dimensions	Set the label among the Collector’s labels provided to identify the source of the Exporter’s metric data, for visualizing on the Console. When visualizing the collected metrics on the Console, they are displayed in combinations according to the dimensions setting. Example: If no special label is provided, as with the metrics of Node Exporter’s Memory Collector, set it to resource_id Example: The metrics of Node Exporter’s Filesystem Collector can have the dimension set to mountpoint, which represents the path where the filesystem is mounted on the system
     metricMetas > unit	Metric unit can be set Example: Bytes, Count, etc.
     metricMetas > aggregationMethod	Method of aggregating based on the specified dimension(s) Example: Choose among SUM, MAX, MIN, COUNT
     metricMetas > descriptionKo	Korean description of the metric being collected
     metricMetas > descriptionEn	English description of the metric being collected

     Table. metric.json configuration file items
     Sample Code Download

     Copy Code

     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 for visualizing on the Console among the Collector's labels provided to identify the source of Node Exporter's metric data.
                                         # If there is no special label provided, such as the relevant Memory-related metric, set it to resource_id
                 ]
              ],
              "unit": "bytes",           # Collection metric data unit
              "aggregationMethod": "SUM",    # aggregation method
               "descriptionKo": "Total physical memory size of the server",    # Indicator's Korean description
              "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 visualization on the Console among the Collector's labels provided to identify the source of Node Exporter's metric data.
                                        # Set dimension (dimensions) as mountpoint indicating the path where the filesystem related to the Filesystem metric 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 for visualizing on the Console among the Collector's labels provided to identify the source of Node Exporter's metric data.
                                         # If there is no special label provided, such as the relevant Memory-related metric, set it to resource_id
                 ]
              ],
              "unit": "bytes",           # Collection metric data unit
              "aggregationMethod": "SUM",    # aggregation method
               "descriptionKo": "Total physical memory size of the server",    # Indicator's Korean description
              "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 visualization on the Console among the Collector's labels provided to identify the source of Node Exporter's metric data.
                                        # Set dimension (dimensions) as mountpoint indicating the path where the filesystem related to the Filesystem metric 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"
           }
        ]
     "}

5. Define the Log configuration file for log collection for ServiceWatch.

   • If you want to collect logs, you need to configure log.json.

     Category	Detailed description
     fileLog > include	Log file location to collect
     fileLog > operators	Definition for parsing log messages to be collected
     fileLog > operators > regex	Express log message format as a regular expression
     fileLog > operators > timestamp	The format of the Time Stamp of the log message to be sent to ServiceWatch
     logMetas > log_group_value	Log group name created to send logs to ServiceWatch
     logMetas > log_stream_value	ServiceWatch log group log stream name

     Table. log.json configuration file items
     Sample Code Download

     Copy Code

     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 regex
              "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"   # The 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 regex
              "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"   # The log stream name within the pre-created ServiceWatch log group
        }
     }

Running Open Telemetry Collector for ServiceWatch

ServiceWatch Agent Execution (for Linux)

1. Run the ServiceWatch Agent.

   • agent.json, metric.json, log.json file locations and servicewatch-agent-manager-linux-amd64,otelcontribcol_linux_amd64 file locations are checked to start the ServiceWatch Agent.
     Sample Code Download

     Copy Code

     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

   • 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 a directory such as agent.json, metric.json, and run as below.
     Sample Code Download

     Copy Code

     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

   • If you only want to collect logs, rename the metric.json file to a different filename or move it so that it is not in the same directory as agent.json, log.json, and then run as shown below.
     Sample Code Download

     Copy Code

     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

2. Stop the ServiceWatch Agent.

   Sample Code Download

   Copy Code

   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

ServiceWatch Agent Run (for Windows)

1. Run the ServiceWatch Agent.

   Sample Code Download

   Copy Code

   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

2. Stop the ServiceWatch Agent.

   Sample Code Download

   Copy Code

   Color mode

   servicewatch-agent-manager-windows-amd64.exe -action stop -dir ./examples

   servicewatch-agent-manager-windows-amd64.exe -action stop -dir ./examples

3 - API Reference

4 - CLI Reference

5 - ServiceWatch Event Reference

The event represents a change in the environment of the Samsung Cloud Platform service. The following is an example of the event.

• Virtual Server’s status changes from Stopped to Running when an event is created.
• Object Storage creates an event when a new bucket is created.
• It creates an event when the IAM user is excluded from the user group.

5.1 - ServiceWatch Event

5.1.1 - Multi-node GPU Cluster

Multi-node GPU Cluster event

Multi-node GPU Cluster service event list to be passed to ServiceWatch.

GPU Node

Cluster Fabric

5.1.2 - MySQL(DBaaS)

MySQL(DBaaS) event

MySQL(DBaaS) service event list to be passed to ServiceWatch.

MySQL