Indicator

metric

Metrics are data about system performance. By default, many services provide free metrics for resources (e.g., Virtual Server, File Storage, etc.), and these 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), allowing you to view both the latest and historical data.

Namespace

A namespace is a logical separation used to distinguish and group ServiceWatch metrics. The namespace of Samsung Cloud Platform services is 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 it can be defined via the ServiceWatch Agent settings or through the OpenAPI. For detailed information on custom metrics and logs, you can find it at 사용자 정의 지표 및 로그.

Metric (Metric)

The metric represents a set of data points sorted chronologically as collected by ServiceWatch. A 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. Data points themselves can arise from any application or activity that collects data.

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

Metrics can only be accessed in the region where they were created. Indicators cannot be deleted arbitrarily by the user. However, if new data is not posted to ServiceWatch, it 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) are 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 and data.

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

Metric retention period

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 of 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 initially collected at short intervals are downsampled and stored for long-term retention.

For example, if data is collected at a 1‑minute interval, it is retained for 15 days at 1‑minute granularity. Even after 15 days have passed, this data remains, but it can only be queried in 5‑minute intervals. After 63 days, this data is re‑aggregated and provided on an hourly basis. If you need to retain metric data points longer than the metric retention period, you can store them separately using the File Download or Export to Object Storage feature.

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’s metrics.

Collection period

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 of each service.

For example, Virtual Server provides a collection interval of 5 minutes during basic monitoring, and provides a 1‑minute interval 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 supplied to ServiceWatch from each service. Aggregation is performed using the namespace, metric name, dimensions, and data point units within the specified aggregation period.

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 pointer of the metric collected during the selected aggregation period. The aggregation period can be selected 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 valid aggregation results, the aggregation period must be equal to or longer than the collection interval.

For example, if you select average, choose 5 minutes for the aggregation period, and select a metric with a 1‑minute collection interval, 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 indicator 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, it may take up to 5 minutes to retrieve the downsampled data correctly. After 63 days have passed, this data will be aggregated again and provided on an hourly basis. If you select an aggregation period from 1 hour to 1 day, it may take up to one hour to retrieve the data correctly. This can cause aggregation delays because aggregating metric data requires downsampling, which takes time.

Alert

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

The alarm status is categorized as Alert(Alert), Normal(Normal), Insufficient data(No data).

• Alert(Alert): When the indicator meets the configured condition
• Normal(Normal): when the indicator does not meet the configured 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 service integrated with ServiceWatch provides basic monitoring by publishing a default set of metrics to ServiceWatch for free. By default, if you use even one of the services, basic monitoring is automatically enabled and can be viewed in ServiceWatch.

Detailed monitoring is available only for certain services and incurs a fee. 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, metrics provided by basic monitoring are collected at a 5 minute → 1 minute interval.
• Basic monitoring of Object Storage is provided for default metrics, and enabling replication metrics provides additional replication metrics.

The following includes services and guides that provide detailed monitoring.