This is the multi-page printable view of this section. Click here to print.
Cloud Monitoring
- 1: Overview
- 2: How-to guides
- 2.1: Using the Monitoring Dashboard
- 2.2: Analyzing Performance
- 2.3: Analyzing Logs
- 2.4: Managing Events
- 2.5: Using Custom Dashboards
- 2.6: Managing Agents
- 2.7: Appendix A. Monitoring Targets by Service
- 2.8: Appendix B. Performance Items by Service
- 2.9: Appendix C. Service-specific status check
- 3: API Reference
- 4: Release Note
1 - Overview
Service Overview
Cloud Monitoring service collects usage and change information, and logs of operating infrastructure resources, and generates events when the set threshold is exceeded, notifying users. Through this, users can quickly respond to performance degradation and failures, and can easily establish resource capacity expansion plans for a stable computing environment.
Provided Functions
Cloud Monitoring provides the following functions.
- Stable Computing Resource Management: You can easily check indicators such as CPU usage, disk usage, and memory usage. Since notifications are automatically sent to designated personnel when events occur in resources being used, you can operate computing resources stably and quickly analyze and respond to failures.
- Convenient Monitoring: Resource status information can be easily monitored by creating a dashboard. Basic dashboards and user-defined dashboards are provided, and various types of widgets can be set up to easily and quickly create dashboards.
- Event Metric Management: Event metrics can be easily set up with just a few clicks through the web-based console. Event metric settings for monitoring targets (event patterns, occurrence conditions, occurrence cycles, performance metrics, operation status, etc.) can be changed in various ways to suit the usage environment, and threshold settings and alarm settings can be easily managed.
- Resource Log Management: Log data of resources can be collected and stored, and searches can be performed on target logs as needed. Additionally, events are quantified for major keywords, and when predefined conditions are met, notifications are automatically sent to designated personnel, providing a more stable usage environment.
Components
Dashboard
The monitoring dashboard allows you to check the operation status, event status, and usage rates of monitoring targets and services.
| Item | Description |
|---|---|
| Region | Location of resources |
| Data Reference Time | Reference time of data displayed on the dashboard |
| Refresh | Refresh the dashboard based on the current time |
| Period Setting | Set the data query period and refresh cycle |
| Monitoring Status | Number and status of monitoring targets for each service in the account |
| Event History | Display recent 7-day events by risk level as a graph |
| Top 5 Performance Usage | Display the top 5 monitoring targets with the highest performance usage |
| Event Map | Display the number of events for each service by risk level |
| Event Status | Display a list of unprocessed events that have occurred |
Performance Analysis
Performance analysis allows you to check the main performance items of monitoring targets and view current data and historical data for each performance item. Users can check the performance status of monitoring targets by service or period and analyze the results by comparing specific performance.
Log Analysis
Log analysis collects and checks the logs of monitoring targets and converts them into quantifiable data for monitoring. Basic logs are provided for each monitoring target, and users can create custom logs to collect and check additional logs.
Event Management
An event is a setting that notifies users when the performance value of a monitoring target meets certain conditions. By setting events, users can grasp monitoring information that they must know without missing it. For example, if an event is set to occur when a performance value related to overload exceeds a certain value, users will be notified whenever there is a risk of overload during resource operation, allowing them to respond before problems occur. Event management allows users to create events and set them to notify designated users when specific values occur during monitoring.
Preceding Services
Cloud Monitoring has no preceding services.
2 - How-to guides
Samsung Cloud Platform Monitoring is a resource management system that allows users to monitor and analyze the operation status of resources within an account on the Samsung Cloud Platform Console. Users can efficiently manage resources using the dashboard page, widgets, and chart features.
- Users can monitor resources created in the Samsung Cloud Platform Console with authorized accounts.
- Users can log in to the Samsung Cloud Platform Console and navigate to Samsung Cloud Platform Monitoring to monitor resources.
Getting Started with Cloud Monitoring
To start using Samsung Cloud Platform Monitoring, follow these steps:
- Click on All Services > Management > Cloud Monitoring menu. This will take you to the Service Home page of Cloud Monitoring.
- Click on the Open Cloud Monitoring button on the Service Home page. This will take you to the Cloud Monitoring Console page.
Exploring the Cloud Monitoring Console
The top and left menus of the Cloud Monitoring Console are composed as follows:
| Category | Description |
|---|---|
| Custom Dashboard Management | Custom Dashboard
|
| Support | Support
|
| Region List | Region List
|
| User Information | View user information and log out of Samsung Cloud Platform Monitoring. |
| Side Menu | Displays the main features of Samsung Cloud Platform Monitoring. Each menu can be clicked to navigate to the corresponding page.
|
Ending Monitoring
To exit the Cloud Monitoring Console, click the Log Out button in the top right corner of the User Information section.
Using Common Features
This section describes frequently used features when using the Cloud Monitoring Console.
Viewing Detailed Information
To view detailed information about a monitored resource, navigate to Cloud Monitoring Console > Performance Analysis or Cloud Monitoring Console > Log Analysis > Log Status. Then, click on the monitored resource for which you want to view detailed information.
- The detailed information for a monitored resource may vary depending on the service type.
- If the operating system (OS) of the monitored resource is RHCOS (Red Hat Core OS), detailed information may not be available.
| Item | Description |
|---|---|
| Basic Information | Displays basic information about the monitored resource
|
| Performance | Displays key performance metrics as graphs |
| Logs | Displays the log collection volume as graphs |
| Events | Displays a list of events that occurred on the monitored resource |
| Agent | Provides Install, Start, Stop, Delete, and Update commands for the agent |
| Query Period Setting | Displays the query period for date/time data
|
| Monitoring Status Area | Displays the monitoring status for performance, logs, and events. |
- Agent management commands are available for Virtual Server, GPU Server, and Bare Metal Server services.
- For more information on agent installation and management, see Managing Agents.
Sorting Data
You can sort event monitoring, performance analysis, and log analysis results in descending or ascending order. To sort data, follow these steps:
- Display the information you want to sort on the page.
- Click on the Sort button next to the category name. The sort order changes between descending and ascending each time you click.
Viewing Real-Time Data
You can set the dashboard or detailed information page to automatically refresh the data at a specified interval.
- The Cloud Monitoring Console allows you to set the monitoring page to refresh periodically.
- You can refresh the data based on the current time by clicking the Refresh button.
To set the refresh interval, follow these steps:
- Click the Settings button in the top right corner of the data representation area.
- Select the refresh interval and click OK.
- You can enable or disable the automatic refresh feature.
Setting the Query Period
You can set the query period to limit the scope of performance, log, and event data, making it easier to find the information you need. To set the query period, follow these steps:
- Click the Settings button in the top right corner of the data representation area.
- Select or enter the query period.
- When entering the query period manually, it must be at least 30 minutes.
- If the data query range is fixed for each widget, the widget’s query range takes priority.
2.1 - Using the Monitoring Dashboard
The monitoring dashboard allows you to view the operational status and event history of monitored services and resources, as well as the top usage items.
Getting Started with the Monitoring Dashboard
When you navigate to the Cloud Monitoring Console page in the Samsung Cloud Platform Console, the monitoring dashboard is displayed. If you are on a different page, you can click Cloud Monitoring Console > Monitoring Dashboard to move to the monitoring dashboard page.
The monitoring dashboard is composed of the following elements.
| Item | Description |
|---|---|
| Data Reference Time | Displays the reference time for the data shown on the dashboard |
| Refresh | Refreshes the dashboard based on the current time |
| Auto Refresh | Enables or disables the auto-refresh feature for the dashboard |
| Period Setting | Sets the data retrieval period or changes the refresh cycle |
| Monitoring Status | Displays the number of monitored targets and their monitoring status for each service |
| Event History | Displays the number of events that occurred in the last 7 days as a graph by risk level |
| Top 5 Performance Usage | Displays the top 5 monitored targets with the highest performance usage as a graph |
| Event Map | Displays the number of events that occurred for each service by risk level |
| Event Status | Displays a list of unprocessed events that have occurred |
- The monitoring dashboard is automatically created when you create an account in the Samsung Cloud Platform Console and cannot be deleted.
- The widgets that make up the monitoring dashboard cannot be changed.
- To create a dashboard with a specific widget, use a custom dashboard. For more information on custom dashboards, see Using Custom Dashboards.
Understanding Common Dashboard Features
This section describes the features that can be used in the dashboard.
Downloading Widget Images
You can download a widget as an image file (*.png) by clicking the download button in the top-right corner of the widget area.
Viewing Detailed Graph Information
When you hover over a graph with your mouse cursor, detailed information appears in a popup.
Monitoring Status
Displays the number of monitored targets and their monitoring status for each service in use.
| Item | Description |
|---|---|
| Service Category | Displays the service category and the number of monitored targets for each service category
|
| Service List | Displays the list of services and the number of monitored targets included in the service category
|
| Monitoring Status | Displays the number of monitored targets and their current status
|
| Event Status | Displays the number of events that have occurred, classified by risk level (Fatal, Warning, Inform) |
- The performance collection in the monitoring status displays the combined number of performance items for both Agent and Agentless methods.
Event History
Displays the number of events that occurred in the last 7 days as a graph by risk level.
- When you hover over the graph with your mouse cursor, the event risk level and the number of occurrences for the selected date appear in a popup.
- Occurrences: The total number of events that occurred
- Active: The number of events that continue to occur because they meet the event occurrence conditions
- Inactive: The number of events that no longer occur because they do not meet the event occurrence conditions
- You can click on the risk level legend area to hide or show the corresponding graph.
Top 5 Performance Usage
Displays the top 5 monitored targets with the highest performance usage as a graph.
- When you hover over the graph with your mouse cursor, the full name of the selected target and its current performance value appear in a popup.
- Clicking on the graph opens the Monitored Target Details popup window for the corresponding target.
| Item | Description |
|---|---|
| CPU Usage/Core [Basic] | The percentage of CPU time used, excluding Idle and IOWait states |
| Memory Used [Basic] | The current amount of used memory |
| Disk Read Bytes [Basic] | The number of disk read bytes |
| Disk Write Bytes [Basic] | The number of disk write bytes |
- The monitoring dashboard only displays the performance of Virtual Servers. To display the top 5 performance of other service types, you must select and configure them in a custom dashboard.
Event Map
Displays the number of events that occurred for each service by risk level.
- When you hover over a square with your mouse cursor, the name of the monitored target appears in a popup.
- Clicking on a service item in the event map opens the Monitored Target Details popup window for the corresponding service.
Each item’s risk level is as follows.
| Item | Description |
|---|---|
| No Rule | A state where it is impossible to determine whether it is normal or abnormal. It means that there is no threshold setting value, so the state cannot be determined. |
| NORMAL | A normal state. It means that the threshold was not exceeded, so no event occurred. |
| INFORM | The lowest level of risk. It includes simple notification-level information. |
| WARNING | A medium level of risk. |
| FATAL | The highest level of risk. |
Event Status
Displays a list of events that have occurred and are still active.
- Events are displayed in the order they occurred most recently.
2.2 - Analyzing Performance
In Performance Analysis, you can check the main performance items of the monitoring target and view the current data and history of each performance item. Users can check the performance status of the monitoring target they manage by service or period and analyze the results by comparing specific performance.
Getting Started with Performance Analysis
You can start performance analysis by selecting a monitoring target directly or entering search conditions. To analyze performance by searching for a monitoring target, follow these steps:
- Click Cloud Monitoring Console > Performance Analysis. You will be moved to the Performance Analysis page.
- Enter the search conditions for the monitoring target you want to analyze in the search area, and then click Search.
| Item | Description |
|---|---|
| Search Area | Detailed search filters are displayed differently in the search area depending on the service type
|
| Number of Monitoring Targets Displayed | Displays the number of search results and the number of performance items that can be viewed at a time in the list
|
| Search Information | Displays the search result values for the search condition items
|
| Performance Indicator | Information Displays the main performance indicators for the monitoring target based on the service type
|
| Detailed View | Check the detailed information of the corresponding monitoring target |
| Performance Comparison | Select a monitoring target to compare performance |
Checking Performance Details
To check the detailed performance information of a monitoring target, follow these steps:
- Click the monitoring target you want to check in the performance analysis list. The Monitoring Details popup window will open.
- Click the Performance tab.
- When you place the mouse cursor over the graph, the values of each performance item will appear in a popup window.
- You can set the query period or change the refresh cycle by clicking the icon in the top right corner.
- You can select the graph display method by clicking the Detailed or Summary buttons in the top left corner of the performance chart.
| Item | Description |
|---|---|
| Basic Information | Displays basic information about the monitoring target |
| Detailed | Displays the performance chart of the monitoring target in detail
|
| Summary | Displays the performance chart of the monitoring target in a checkerboard format
|
| Query Period Setting |
|
| Performance Comparison | Creates a chart to compare the performance of the monitoring target and makes it possible to compare each performance |
| Performance Chart | Displays the performance chart of the monitoring target as a graph
|
- The collection cycle of performance values may vary depending on the service.
- The data in the chart is expressed in 30 points, and the data collection interval according to the data query range (time) is as follows. (The expression point may vary depending on the collection time error)
- 30 minutes: approximately 1-minute interval
- 60 minutes: approximately 2-minute interval
- 3 hours: approximately 6-minute interval
- 6 hours: approximately 12-minute interval
- 12 hours: approximately 24-minute interval
- 24 hours: approximately 48-minute interval
- 3 days: approximately 144-minute interval (2 hours 24 minutes)
- 7 days: approximately 336-minute interval (5 hours 36 minutes)
- 14 days: approximately 672-minute interval (11 hours 12 minutes)
- Custom: The user-specified range (minutes) divided by 30
- Each point’s data is expressed as the maximum value in the query range (time), and you can change the statistical type in the detailed chart.
Comparing Performance
You can check the performance items of each monitoring target and select the desired performance items to compare.
Getting Started with Performance Comparison
You can create a chart to compare the performance of the monitoring target and compare each performance.
- Only performance items of the same service type can be compared.
- Performance items may be added depending on the detailed attributes of the service type.
- Windows OS performance of VM
- Kibana-related performance of Search Engine
To start performance comparison, follow these steps:
Click Cloud Monitoring Console > Performance Analysis. You will be moved to the Performance Analysis page.
Enter the search conditions for the monitoring target you want to analyze in the search area, and then click Search.
Select all the monitoring targets you want to compare and click Performance Comparison. A popup window will open where you can compare performance.
Item Description Monitoring Target Displays the service type of the monitoring target to be compared. Click to change the service - Changing the service will delete all charts created so far.
- Click Add to search for and add the monitoring target of the currently selected service
- The selected monitoring target is displayed on the page, and you can delete the monitoring target by clicking X or Delete All
Performance Item Displays all performance items collected by the currently selected service - Check the performance items you want to compare, and they will be included in the chart.
Chart Display Method Selects the display method for the performance comparison chart - Detailed: The performance comparison chart is displayed in detail (default)
- Summary: The performance comparison chart is displayed briefly
Query Period Setting - Date/Time: Displays the query base time of the data
- Refresh: Refreshes the data directly to the current time.
- Start/Stop: Enables or disables the automatic refresh function.
- Settings: Sets the data query period or changes the automatic refresh cycle
Chart Area Displays a chart comparing the performance of the monitoring targets based on the selected performance items Click Add. A popup window will open where you can add a monitoring target.
Select the monitoring target you want to compare and click OK.
- If you select Kubernetes Engine, you must also select its subtype.
Check the performance items you want to compare. The corresponding performance items will be added to the chart.
Checking the Chart
The performance comparison result is displayed as a chart. You can change the shape of the created chart or download it as an image or Excel file.
- When you place the mouse cursor over the graph, the performance item value at the specified time appears in a popup window.
- You can hide or show the graph by clicking the target item in the legend area.
Item Description Statistical Method Sets the statistical method to be displayed as a graph - Displays statistics from 5 minutes to 6 hours.
- Basic, Maximum, Minimum, Average, Sum can be selected, and multiple methods can be selected at the same time. The selected items are displayed in the legend area
Chart Type Selects the type of graph to be displayed in the chart - Line: Line graph
- Stacked Area: Area graph
- Scatter: Scatter graph
Chart Download Checks and downloads the raw data of the chart - Chart PNG File: Downloads the chart as an image file (PNG).
- Chart Excel File: Downloads the data of the performance items displayed in the chart as an Excel file. The chart display data is a set of data automatically collected according to the query range.
- Raw Excel File: Downloads all the data of the performance items displayed in the chart for the query range period as an Excel file.
Time Series Graph Widget Addition Adds the chart to a user-defined dashboard as a time series graph widget - Clicking will open a popup window to add a time series graph widget.
Delete Deletes the performance comparison result chart Performance Comparison Status Displays the performance comparison result as a graph - When you place the mouse cursor over the graph, the performance comparison status at that time is displayed in a popup window.
2.3 - Analyzing Logs
In log analysis, the log of the monitoring target is collected and its contents are checked, and it can be monitored by converting it into an indicator, which is a structured data. Basic collection logs are provided for each monitoring target, and users can create custom logs to collect and check desired logs in addition.
Start log analysis
You can check the log status list or search for the monitoring target log to check. To check the log status list, follow the procedure below.
- Cloud Monitoring Console > Log Analysis > Log Status을 클릭하세요. Log Status 페이지로 이동합니다.
- Enter the search conditions of the service to be analyzed in the search area, and then click Log Search.
- A list of services that match the search criteria and search information will be displayed at the bottom.
- Clicking the Detail View button for each service displays detailed log information for the service.
Item Description Search Area The search filters displayed in the search area may vary depending on the service type - Advanced Search can be done by clicking the Advanced Search button.
- Each detailed search filter condition item can be selected one or more
Number of items to display for monitoring targets Displays the number of search results and the performance number that can be viewed at once in the list - The default is to view 20 at a time.
- The number of items listed can be changed to view 10, 20, 30, 40, 50, or 100 at a time
Search Information Displays the search result value for the search condition item Detailed View Check the detailed information of the corresponding monitoring target Log Search Search logs by combining keywords and queries and check detailed history
-, _, .) and can be entered up to a maximum of 100 characters.
If the monitoring target does not have permission, information about the target without permission and a permission check message will be displayed as a pop-up.Check log details
You can view the detailed log records and log graphs of the monitoring target.
Checking the log list
You can check the log details in the monitoring detail pop-up window. To check the monitoring details of the log, follow the next procedure.
Cloud Monitoring Console > Log Analysis > Log Status을 클릭하세요. Log Status 페이지로 이동합니다.
Click on the log to check the detailed information on the Log Status page. The Monitoring Details popup window will open.
Click the log tab. When you place the mouse cursor on the graph, the value of each log item appears in a popup window.
- You can set the inquiry period or change the refresh cycle by clicking the icon at the top right.
- You can select the graph display method by clicking the Detail, Summary buttons at the top left of the log chart.
Item Description Basic Information Displays basic information about the monitoring target Details The chart for each log of the monitoring target is unfolded and displayed - Check one chart in detail
Summary Performance charts of monitoring targets are displayed in a checkerboard format - Check multiple charts at a glance
Setting the inquiry period - Date/Time: Displays the standard time of the data inquiry.
- Refresh: Refreshes directly to the current time.
- Start/Stop: Turns the automatic refresh function on or off.
- Settings: Sets the data inquiry period or changes the automatic refresh cycle
Performance comparison Combine keywords and queries to search logs and check detailed history Performance-based chart The log-based chart of the monitoring target is displayed as a graph - If you place the mouse cursor over the graph, the log item value at the specified time will appear in a popup window.
Check by searching the log
You can search logs by combining keywords and queries, and check the details.
To search logs, follow the next procedure.
Cloud Monitoring Console > Log Analysis > Log Status을 클릭하세요. Log Status 페이지로 이동합니다.
Click Log Status on the Log Search page. It moves to the Log Search page.
Item Description Monitoring target Indicates the type of service for the monitoring target to be compared - Click the monitoring target list to change the service
- If the service is changed, all charts created so far will disappear.
- Click the Add button to search for and add the monitoring target of the currently selected service
- The selected monitoring target is displayed on the page, and you can delete the monitoring target by clicking X or Delete all.
Search Condition Set the condition for the log to be searched Setting the inquiry period - Date/Time: Displays the standard time of the data inquiry.
- Refresh: Refreshes directly to the current time.
- Start/Stop: Turns the auto-refresh function on or off.
- Settings: Sets the data inquiry period or changes the auto-refresh cycle
The graph of log occurrence Log occurrence graph Occurrence log message Log messages that occurred from the monitoring target are displayed by time Add button is clicked. A popup window that can add a monitoring target will open.
Click the monitoring target and select the log file you want to add.
Once the log file selection is complete, click the Confirm button.
Enter the search conditions and click the Search button. The search results will be displayed on the log volume graph and the occurred log message.
Item Description Add Metric Add a metric to the log search results - Use after searching logs
Execution History Check the list of search conditions that were recently executed for the search - Execution history displays up to 20 most recently executed search conditions
- Select the desired execution history to input as the current search condition
Search field Select search field Condition Select search condition like,!like,=,!=,<=,>=,>,<can be selected
Search value Enter the keyword to search Log Search Select an operator (AND, OR) for the newly added search condition - Only displayed when a new search condition is added
Add condition Add new search condition When searching logs, the log history corresponding to the entered condition is displayed as a chart.
- Log history is displayed in seconds.
Item Description Log occurrence graph The log occurrence during the set period is displayed as a graph - If you place the mouse cursor over the graph, the value of each log item appears in a popup window.
- Clicking on the bar graph of the graph displays the list of logs at that point in time.
Setting the inquiry period - Date/Time: Displays the reference time of the data
- Refresh: Refreshes directly to the current time.
- Start/Stop: Turns the automatic refresh function on or off.
- Settings: Sets the data inquiry period or changes the automatic refresh cycle
Monitoring target The monitoring target list is displayed - If you select a monitoring target to check the log message, the contents will be displayed in the log list
Log list Log messages that occurred in the monitoring target are displayed by time - Clicking the button in the log list displays the full message of the log
- Click download to download the currently displayed log message in Excel and TXT file formats
- Log history is displayed in seconds.
Check the status of log collection
You can check the collection information of major logs for the past 7 days in a chart.
When you place the mouse cursor on the graph, detailed information appears in a pop-up window. Only collected logs are aggregated, and uncollected logs are not displayed in the current status.
When you create an * Account, it provides 1GB of virtual capacity by default to store the collected logs.
- All logs can be stopped and restarted for collection as needed.
To check the log collection status, click Cloud Monitoring Console > Log Analysis > Log Collection Dashboard.
| Item | Description |
|---|---|
| Accumulated log occurrence amount | Amount of logs collected from the 1st of each month, displayed in GB
|
| Recent 7-day log collection amount | The amount of logs collected over the past 7 days is displayed in a graph by service type
|
| Service-specific log occurrence rate | Displays the log collected over the past 7 days, classified by service
|
| Log Collection Top 10 | Displays the top 10 monitoring targets with the most logs collected in the last 7 days within the selected service in the log occurrence rate by service as a graph
|
Check the status of the indicator settings
You can create metrics to display the occurrence of log patterns over time as a time series. To check the list of metrics, click Cloud Monitoring Console > Log Analysis > Current Metric Settings.
| Item | Description |
|---|---|
| Search area | The search filter displayed in the search area may vary depending on the service type
|
| Number of items to display for monitoring targets | Display search results
|
| Search Information | Displays the search result value for the search condition item |
| Add | Add a new indicator |
| Delete | Select and delete indicators in search information |
Check the details of the indicator
To view detailed information about the metric, follow these steps.
- Cloud Monitoring Console > Log Analysis > Metric Setting Status will be clicked. It moves to the Metric Setting Status page.
- On the Indicator Setting Status page, click the indicator name to check detailed information. The Indicator Details popup window will open.
Adding Indicators
You can add new metrics to display the desired log data as a time series.
To add a new metric, follow the procedure below.
Cloud Monitoring Console > Log Analysis > Metric Setting Status will be clicked. It moves to the Metric Setting Status page.
On the Indicator Setting Status page, click the Add button. The Add Indicator popup window opens.
Indicator Name을 입력하세요.
- Indicator names can only use English uppercase and lowercase letters, underscores (_), periods (.), and hyphens (-).
- To distinguish metrics from general performance, the prefix
metricfilter.is automatically added and cannot be deleted or changed.
Item Description Indicator Name Enter the name of the new indicator to be created Monitoring Target Indicates the type of service for the monitoring target to be compared - Click the monitoring target list to change the service
- If the service is changed, all charts created so far will disappear.
- Click the add button to search for and add the monitoring target of the currently selected service
- The selected monitoring target is displayed on the page and can be deleted by clicking X or delete all
Search Conditions Set conditions for logs to be searched Set query period - Date/Time: Displays the reference time for data query
- Refresh: Refreshes directly to the current time.
- Start/Stop: Turns automatic refresh on or off.
- Settings: Allows setting the data query period or changing the automatic refresh cycle.
Log Volume Graph When searching for logs, the log history that matches the entered conditions is displayed as a chart Occurrence Log Message Log messages that occurred from the monitoring target are displayed by time Add button is clicked. A popup window that can add monitoring targets will be opened.
Click the monitoring target and select the log file you want to add.
Once the log file selection is complete, click the Confirm button.
Enter the search conditions and click the Search button. The search results will be displayed in the log volume graph and occurrence log message.
Item Description Add Metric Add metrics to log search results - Use after searching logs
Execution History Check the list of search conditions that were recently executed for searching - Execution history displays up to 20 most recently executed search conditions
- Can input the desired search history as the current search condition
Search Field Select Search Field Condition Select search condition like,!like,=,!=,<=,>=,>,<can be selected
Search value Enter the keyword to search Operator Select an operator (AND, OR) for the newly added search condition - Only displayed when a new search condition is added
Add condition Add new search condition Click the Confirm button. A new metric will be added with a toast popup message.
Modifying Indicator Search Conditions
To modify the search criteria of the indicator, follow the next procedure.
- Cloud Monitoring Console > Log Analysis > Metric Setting Status will be clicked. It moves to the Metric Setting Status page.
- On the Indicator Setting Status page, click the Indicator Name of the indicator you want to modify. The Indicator Details popup window will open.
- Indicator Details popup window, click the Edit button. The Edit Indicator popup window opens.
- In the Modify Indicator popup window, modify the search conditions and click the Confirm button. The indicator will be modified along with a toast popup message.
Deleting Indicators
To delete an indicator, follow these steps.
- Cloud Monitoring Console > Log Analysis > Metric Setting Status을 클릭하세요. Metric Setting Status 페이지로 이동합니다.
- On the Indicator Setting Status page, select the indicator to be deleted and click the Delete button. The indicator will be deleted along with a toast popup message.
2.4 - Managing Events
An event is a setting that alerts users when the performance value of a monitored target meets certain conditions. By setting up events, users can grasp important monitoring information without missing it. For example, if an event is set to occur when a performance value related to overload exceeds a certain threshold, users will receive notifications whenever there is a risk of overload while operating the resource. Users can then take action before problems occur.
In event management, users can create events to alert designated users when specific values occur during monitoring.
Checking Event Status
The event status section displays information about all occurred events, related performance items, and event notification history. To check the event status list, follow these steps:
- Click Cloud Monitoring Console > Event Management > Event Status. The Event Status page will be displayed.
- On the Event Status page, enter the search conditions for the service you want to check in the search area, and then click the Search button.
Item Description Search Area The search filter displayed in the search area varies depending on the service type. - Click the Detailed Search button to perform a detailed search.
- Multiple conditions can be selected for each detailed search filter.
Number of Monitoring Targets Displayed Displays the number of search results and the number of performance items that can be viewed at once in the list. - The default value for the number of performance items displayed in the list is 20 per page.
- The number of performance items displayed in the list can be changed to 10, 20, 30, 40, 50, or 100 per page.
Search Information Displays the search result values for the search condition items. - Clicking on the message content for each service allows you to check the detailed information of the event.
Detailed View Displays detailed information about the corresponding monitoring target. Table. Event List
- If a Virtual Server or Node is connected to the monitoring target, the status will also be displayed in the search information area.
- The name of the monitoring target can include Korean, English ( uppercase and lowercase), numbers, and special characters (-, _, .), with a maximum of 100 characters.
Viewing Event Status List
In the monitoring detail popup window, you can check the event information, occurrence time, and duration. To check the event occurrence status, follow these steps:
- Click Cloud Monitoring Console > Event Management > Event Status. The Event Status page will be displayed.
- On the Event Status page, click the Event tab.
Item Description Event Status Displays the event message and occurrence time. Active Displays only events that are currently active. All Displays all events. Event Details Displays detailed information about the selected event message. Table. Event Tab
Checking Event Details
To check the event details, follow these steps:
- Click Cloud Monitoring Console > Event Management > Event Status. The Event Status page will be displayed.
- On the Event Status page, click the Event tab.
- On the Event Status page, select the event you want to check the details for, and then click Event Details. You can then check the event issuance conditions, performance items, and notification history.
| Item | Description |
|---|---|
| Monitoring Target | Displays the name of the monitoring target. |
| Occurrence Condition | Displays the occurrence condition of the event. |
| Performance Item | Displays a chart for the performance item.
|
| Notification History | Displays the entire notification history. |
| Event Setting Details | Displays the setting information for the corresponding event. |
Managing Event Settings
You can set up detailed event settings, such as the monitoring target, performance value that serves as the basis for event occurrence, event risk level, and event notification recipient. When the data collected from the monitoring target meets the conditions set in the event policy, notifications are sent to users via email, SMS, or messaging.
- Event policies can only be set when a monitoring target is specified, and policies for Auto-Scaling Groups can be set on a group-by-group basis.
Checking Event Settings
To check the event settings, follow these steps:
- Click Cloud Monitoring Console > Event Management > Event Settings. The Event Settings page will be displayed.
- On the Event Settings page, enter the search conditions for the service you want to check in the search area, and then click the Search button.
Item Description Search Area The search filter displayed in the search area varies depending on the service type. - Click the Detailed Search button to perform a detailed search.
- Multiple conditions can be selected for each detailed search filter.
Number of Monitoring Targets Displayed Displays the search results. - The default value is 20 per page.
- The number of performance items displayed in the list can be changed to 10, 20, 30, 40, 50, or 100 per page.
Monitoring Target Displays the name of the monitoring target. - Checking the box selects the monitoring target, and the Delete, Activate, and Notification Recipient buttons are activated.
Performance Item Displays the performance item that is the target of the event setting. Individual Item Displays the individual performance item under the performance item. - If there are no individual items, they will not be displayed.
Type/Unit Displays the value type and unit of the corresponding performance item. Event Level Displays the risk level of the corresponding event. - The risk level is set by the user when adding an event.
- Fatal: The most critical level.
- Warning: The middle level of risk.
- Information: The lowest level of risk and reference level.
Threshold Displays the reference value used to compare the performance value. Notification Recipient Displays the recipient of the event notification. - Placing the mouse cursor over the name displays the entire list.
Policy Status Displays whether the event is activated or not. Detailed View Displays detailed event information and allows modification. - Clicking Detailed View opens a popup window with detailed information about the corresponding event.
Add Adds an event. Delete Deletes an event. Activate Activates or deactivates an event. Notification Recipient Displays and manages event notification recipients. Table. Event Settings
- The name of the monitoring target can include Korean, English (uppercase and lowercase), numbers, and special characters (-, _, .), with a maximum of 100 characters.
- If you do not have permission for the monitoring target, a message will be displayed indicating that you do not have permission, along with the target information.
Checking Detailed Event Settings
You can check detailed information about the monitoring target and event conditions, and modify the event conditions and notification information.
Adding Event Settings
To add event settings, follow these steps:
- Event policies can only be set when a monitoring target is specified.
- Policies for Auto-Scaling Groups can be applied on a group-by-group basis.
Click Cloud Monitoring Console > Event Management > Event Settings. The Event Settings page will be displayed.
On the Event Settings page, click the Add button. The Add Event Settings popup window will be displayed.
Item Description Target Name Select the monitoring target to add event settings for. - Clicking the monitoring target list changes the service.
- Changing the service will delete all event conditions created so far.
- Click the Add button to search for and add the monitoring target of the currently selected service.
- The selected monitoring target is displayed on the page, and you can delete the monitoring target by clicking the X or Delete All button.
Event Settings Area Set the performance and occurrence conditions for the event. Notification Information Area Set the notification recipient and notification method for the event. Table. Add Event Settings Popup WindowIn the monitoring target area, select the service type and then click the Add button. The Add Monitoring Target popup window will be displayed.
Select the monitoring target and then click the Confirm button.
- You can select multiple monitoring targets at the same time.
- If there are multiple monitoring targets, the set event will be added to each monitoring target.
- If you select Kubernetes, you must also select the subtype.
In the performance item area, click the performance item you want to add an event for, and then enter the event occurrence condition.
- The number of times the performance item is added is displayed next to the performance item name.
- If you select multiple performance items, you must enter the event occurrence condition for each performance item.
Item Description Event Policy Template Select an existing event policy template to apply. Performance Item Click the performance item to set the event occurrence condition. Event Level Set the event level. - Fatal: The most critical level.
- Warning: The middle level of risk.
- Information: The lowest level of risk and reference level.
Performance Type Select the reference value used to determine whether the event occurs. - Collected Value: Uses the current value.
- Delta Value: Uses the difference between the previous value and the current value.
Threshold Set the reference value used to compare the performance value. - This is the criterion for determining whether the event occurs.
- Only numbers and decimal points can be entered.
Comparison Method Select the method used to compare the performance value and the threshold. - Range: Checks if the performance value is within the specified range of the threshold.
- Match: Checks if the performance value matches the threshold.
- Mismatch: Checks if the performance value does not match the threshold.
- Greater Than: Checks if the performance value is greater than the threshold.
- Greater Than or Equal To: Checks if the performance value is greater than or equal to the threshold.
- Less Than: Checks if the performance value is less than the threshold.
- Less Than or Equal To: Checks if the performance value is less than or equal to the threshold.
Individual Item Specifies the individual performance item under the performance item as the event condition. - This is only activated if the performance item can collect individual items.
Prefix Adds a prefix to the event message. - This is used as a keyword to search for the event in the Event Status page.
Statistics Sets the statistical method to apply to the collected performance values. - If a statistical method is set, the performance value to which the statistical method is applied is compared to the threshold to determine whether the event occurs. If not set, the most recent performance value is compared to the threshold.
- Statistical Method: Selects one of the maximum, minimum, average, or sum to calculate the collected performance values.
- Statistical Period: Sets the period for which the statistical method is applied. This is the period from the most recently collected performance value.
Continuous Occurrence Count Sets the number of consecutive monitoring values that meet the event occurrence condition. - This value is used as sensitivity to determine whether the event is a momentary anomaly or an actual event.
Event Occurrence Notification Time Sets the time zone for event policy settings. Table. Add Event Settings - Event Settings Area
In the Notification area, you can set up notifications.
Item Description Notification Recipient Selection Area Select the notification recipient. - Clicking the Delete button after selecting the notification recipient deletes the recipient.
Notification Recipient/Group Displays the list of recipients to whom the event notification will be sent. Event Risk Level Displays the risk level of the set event. Notification Method Displays the method used to send notifications to the recipient. Add Adds a new notification recipient from the address book. Delete Deletes the notification recipient from the list. Table. Add Event Settings - Notification Information AreaCheck the notification recipient and then click the Confirm button.
- Only the Root user or IAM user of an account can be added as a notification recipient.
- Multiple recipients can be selected at the same time.
Set the notification method for each notification recipient based on the event risk level.
- The notification method can be selected from email, SMS, or messaging, and multiple methods can be selected at the same time.
After setting the notification method, click the Confirm button.
Modifying Event Settings
To modify the event conditions and notification recipient information, follow these steps:
- Click Cloud Monitoring Console > Event Management > Event Settings. The Event Settings page will be displayed.
- On the Event Settings page, enter the search conditions for the service you want to modify in the search area, and then click the Search button.
- In the event policy list, click the Detailed View button for the event policy you want to modify. The Event Setting Details page will be displayed.
- On the Event Setting Details page, click the Modify button. The Modify Event Settings page will be displayed.
- On the Modify Event Settings page, enter the modified information and then click the Confirm button.
- You can modify the event conditions and notification information.
Deleting Event Settings
To delete event settings, follow these steps:
- Click Cloud Monitoring Console > Event Management > Event Settings. The Event Settings page will be displayed.
- On the Event Settings page, enter the search conditions for the service you want to delete in the search area, and then click the Search button.
- In the event policy list, check the event policy you want to delete and then click the Delete button.
- In the confirmation popup window, click the Confirm button.
Changing Event Setting Activation
You can easily change the activation status of event policies.
- Click Cloud Monitoring Console > Event Management > Event Settings. The Event Settings page will be displayed.
- On the Event Settings page, enter the search conditions for the service you want to delete in the search area, and then click the Search button.
- In the event policy list, check the event policy you want to change the activation status for and then click the Activate button. The Policy Activation popup window will be displayed.
- Select the activation status and then click the Confirm button.
- You can change the activation status in bulk by clicking the Activate All or Deactivate All button.
Changing Event Notification Recipients
You can check and change the notification recipients for event occurrences in bulk.
- The event notification recipient change function is intended to change the notification recipients in bulk. Therefore, existing notification recipients will be deleted and changed to the new notification recipient settings.
- To check and change the notification recipients for each policy, click the Modify button on the policy details page.
Click Cloud Monitoring Console > Event Management > Event Settings. The Event Settings page will be displayed.
On the Event Settings page, enter the search conditions for the service you want to delete in the search area, and then click the Search button.
In the event policy list, check the event policy you want to modify and then click the Notification Recipient button. The Notification Recipient page will be displayed.
On the Notification Recipient page, select the user to add as a notification recipient and then click the Confirm button.
Item Description Event Policy List Displays the list of event policies to change the notification recipients for. - Click Add to add policies to change.
- Clicking the Delete button for a policy deletes the policy.
User Search Area Enter the name, email, phone number, or company name to search for users. Notification Address Book Use the address book to check and add users. Search User List Displays the list of users included in the address book or search results. - Checking the user adds them to the notification recipient list.
Notification Recipient List Displays the list of users to be added as notification recipients for the event policies displayed in the list. - Checking the user and clicking the Delete button removes the user from the list.
Table. Changing Event Notification Recipients
Managing Event Templates
You can create event templates by setting monitoring targets, performance values that serve as the basis for event occurrence, and event risk levels. When adding or modifying events, you can use event policy templates to easily enter event conditions.
Checking the Event Policy Template List
To check the event policy template list, follow these steps:
Click Cloud Monitoring Console > Event Management > Event Settings. The Event Settings page will be displayed.
On the Event Settings page, click Event Policy Template. The Event Policy Template page will be displayed.
On the Event Policy Template page, enter the search conditions for the service you want to check in the search area, and then click Search.
Item Description Search Area Enter the conditions for the event policy template to search Add Event Policy Template Add an event policy template Template List Displays the event policy templates that match the search conditions Table. Event Policy Template List
Adding an Event Policy Template
To add an event policy template, follow these steps:
Click Cloud Monitoring Console > Event Management > Event Settings. The Event Settings page will be displayed.
On the Event Settings page, click the Event Policy Template button. The Event Policy Template page will be displayed.
On the Event Policy Template page, click the Add Event Policy Template button. The Add Event Policy Template popup window will open.
In the Add Event Policy Template popup window, set the service type and template information to add the event policy template.
*indicates required input items.Item Description Service Type Select the service type to set the event policy Template Name Enter the name of the template to create Template Description Enter a description of the template to create Table. Adding an Event Policy Template - Service Type and Template Name Settings
In the performance item section, click the performance item to add an event and enter the event occurrence conditions.
- The number of times the performance item is added is displayed next to the performance name.
- If multiple performance items are selected, event occurrence conditions must be entered for each performance item.
*indicates required input items.Item Description Load Event Policy Template Select an existing event policy template to apply Performance Item Click the performance item to set the event condition Event Level Set the event risk level Performance Type Select the performance value to use as the basis for event occurrence Threshold Set the threshold value to compare with the collected performance value Comparison Method Select the comparison method to determine event occurrence Individual Item Specify individual performance items as event conditions Prefix Add a prefix to the event message Statistics Set the statistical method to apply to the collected performance value Continuous Occurrence Count Set the number of consecutive monitoring values that meet the event occurrence conditions Event Occurrence Notification Time Set the time zone for event policy settings Table. Adding an Event Policy Template - Performance Item
Set the notification target and method when an event occurs.
Item Description Add Add a new notification target Delete Delete the selected notification target Notification Target/Group Displays the list of notification targets Event Risk Level Displays the event risk level to be notified Notification Method Displays the notification method Table. Adding an Event Policy Template - Notification Target Settings
- Only account members and address book registered in the account can be added as notification targets.
- Multiple targets can be selected at the same time.
- Click the Confirm button. The event policy template will be added, and a toast popup message will be displayed.
Modifying and Deleting an Event Policy Template
To modify or delete an event policy template, follow these steps:
- Click Cloud Monitoring Console > Event Management > Event Settings. The Event Settings page will be displayed.
- On the Event Settings page, click the Event Policy Template button. The Event Policy Template page will be displayed.
- On the Event Policy Template page, enter the search conditions for the service you want to check in the search area, and then click the Search button.
- Click the More button at the top right of the template you want to modify or delete, and then click Modify or Delete.
- Modify: The template modification popup window will open. Modify the template and click the Confirm button.
- Delete: The template will be deleted, and a toast popup message will be displayed.
- Click the Confirm button. The template will be deleted, and a toast popup message will be displayed.
Sharing an Event Policy Template
To share an event policy template, follow these steps:
- Click Cloud Monitoring Console > Event Management > Event Settings. The Event Settings page will be displayed.
- On the Event Settings page, click the Event Policy Template button. The Event Policy Template page will be displayed.
- On the Event Policy Template page, enter the search conditions for the service you want to check in the search area, and then click the Search button.
- Click the More > Share button at the top right of the template you want to share.
- Select the user to share with and click the > button. The selected user will be added to the shared target.
- Click the Confirm button. The template will be shared, and a toast popup message will be displayed.
Event Filtering
You can filter event notifications for a specific period. During the event filtering period, events will occur, but notifications will not be delivered.
To check the event filtering list, follow these steps:
- Click Cloud Monitoring Console > Event Management > Event Filtering. The Event Filtering page will be displayed.
| Item | Description |
|---|---|
| Filtering Timeline | Displays the registered filtering timeline by date |
| Filtering List | Displays the registered filtering information and action status in a list |
| Add | Adds a new event filtering |
| Delete | Deletes the selected event filtering |
| Search Area | Searches for event filtering or monitoring targets |
Adding Event Filtering
To add event filtering, follow these steps:
Click Cloud Monitoring Console > Event Management > Event Filtering. The Event Filtering page will be displayed.
On the Event Filtering page, click the Add button. The Add Event Filtering popup window will open.
In the Add Event Filtering popup window, enter the filtering information.
Item Description Event Filtering Enter the name of the event filtering Usage Set the usage of the event filtering Time Zone Set the time zone for the event filtering Repeat Type Set the repeat type of the event filtering Period Set the period for the event filtering Event Filtering Target Select the service type and monitoring target to apply the event filtering Table. Adding Event FilteringClick the Confirm button. The event filtering will be added, and a toast popup message will be displayed.
Modifying Event Filtering
To modify event filtering, follow these steps:
- Click Cloud Monitoring Console > Event Management > Event Filtering. The Event Filtering page will be displayed.
- On the Event Filtering page, click the name of the filtering you want to modify. The Event Filtering Details popup window will open.
- In the Event Filtering Details popup window, click the Modify button. The Modify Event Filtering popup window will open.
- In the Modify Event Filtering popup window, enter the modified contents and click the Confirm button. The event filtering will be modified, and a toast popup message will be displayed.
Deleting Event Filtering
To delete event filtering, follow these steps:
- Click Cloud Monitoring Console > Event Management > Event Filtering. The Event Filtering page will be displayed.
- On the Event Filtering page, select the event filtering you want to delete and click the Delete button. The event filtering will be deleted, and a toast popup message will be displayed.
- Multiple event filterings can be selected at the same time.
Managing Notification Groups
You can manage notification targets as a group when an event occurs. Notification Groups can be used to efficiently manage notification targets and easily set up notifications.
To check the Notification Groups, follow these steps:
- Click Cloud Monitoring Console > Event Management > Notification Groups. The Notification Groups page will be displayed.
- On the Notification Groups page, you can check and manage the notification groups.
Item Description Add Notification Group Adds a new notification group Notification Group Displays all notification groups created by the user Detailed Search Searches for notification groups by name Keyword Search Searches for notification groups, user names, creation dates, and last modification dates
Adding a Notification Group
To add a notification group, follow these steps:
- Click Cloud Monitoring Console > Event Management > Add Notification Group.
- On the Add Notification Group page, enter the notification group name, description, and add users.
- Click the Save button. The notification group will be added.
Modifying a Notification Group
You can add users to a notification group or delete registered users from the group.
Adding Users
To add users to a notification group, follow these steps:
- Click Cloud Monitoring Console > Event Management > Notification Groups.
- Click the notification group you want to add users to, and then click Modify.
- Select the users to add.
- Only account members can be added to the address book.
- You can use the real-time search GUI to quickly find the desired members.
- Click the Save button. The user address will be added, and a toast popup message will be displayed.
Deleting a Notification Group
To delete a notification group, follow these steps:
- Click Cloud Monitoring Console > Event Management > Notification Groups.
- Click the notification group you want to delete.
- Select the notification group to delete and click Delete.
- Multiple addresses can be selected at the same time.
- Click the Confirm button. The address will be deleted, and a toast popup message will be displayed.
2.5 - Using Custom Dashboards
A custom dashboard is a user-defined dashboard that allows users to select and arrange widgets according to their preferences. Users can customize the monitoring information and share the created custom dashboard with other users.
The following content is covered in Using Custom Dashboards.
Getting Started with Custom Dashboards
Users can create a custom dashboard and add desired widgets to view monitoring information.
Creating a Custom Dashboard
To create a custom dashboard, follow these steps:
- Click Custom Dashboard Management in the top-right menu. The Custom Dashboard Management page will be displayed.
- Click Add Dashboard. The Add Dashboard popup window will open.
- Enter the name of the dashboard to be created and click the Save button.
- The created custom dashboard will be displayed in the My Dashboards list.
Adding Widgets
Custom dashboards provide various types of widgets, such as performance statistics, comparison charts, and event lists. Users can add widgets to customize their dashboard according to their monitoring needs.
- Created widgets can be modified, copied, or deleted. For more information, see Managing Custom Widgets.
To add a widget, follow these steps:
- Click Custom Dashboard Management in the top-right menu. The Custom Dashboard Management page will be displayed.
- Select the custom dashboard to add a widget from the My Dashboards list.
- Click the + button or Add Widget button in the top-right corner of the dashboard. The Add Widget popup window will open.
- Select the widget to add to the dashboard from the Add Widget popup window.
- When a widget is selected, detailed settings and previews will be displayed.
- For each chart, see Custom Widgets for explanations and setup methods.
- Click the Confirm button.
Custom Widgets
The following types of widgets can be added to a custom dashboard:
| Widget Name | Description |
|---|---|
| Title Box | Displays a title box on the custom dashboard. |
| Event Status | Displays the status of occurred events. |
| Monitoring Status | Displays the number of monitoring targets and their status. |
| Top 5 Performance | Displays the top 5 monitoring targets with the highest performance usage rates. |
| Event Map | Displays the number of events occurred by service and risk level. |
| Event History | Displays the number of events occurred by date and risk level. |
| Time Series Graph | Displays the performance of a selected monitoring target as a time series graph. |
| Status Indicator | Displays the statistical values and risk levels of monitoring targets. |
| Instance Map | Displays the performance values of monitoring targets with different color densities. |
Title Box
Displays a title box on the custom dashboard.
- Up to 10 title boxes can be created.
- Multiple title boxes can be added at the same time.
| Item | Description |
|---|---|
| Title | Enter the text to be displayed on the title box. |
| Add | Adds a new text box. |
| Delete | Deletes the corresponding text box. |
Event Status
Displays the status of occurred events.
- All occurred events can be displayed, or only active events can be displayed.
| Item | Description |
|---|---|
| Widget Name | Enter the name of the widget. |
| Query Range | Select the range of events to be displayed on the widget. |
Monitoring Status
Displays the number of monitoring targets and their status.
| Item | Description |
|---|---|
| Widget Name | Enter the name of the widget. |
Top 5 Performance
Displays the top 5 monitoring targets with the highest performance usage rates.
| Item | Description |
|---|---|
| Widget Name | Enter the name of the widget. |
| Service | Select the service to check performance. |
| Performance Item | Select the performance item to display. |
Event Map
Displays the number of events occurred by service and risk level.
| Item | Description |
|---|---|
| Widget Name | Enter the name of the widget. |
Event History
Displays the number of events occurred by date and risk level.
| Item | Description |
|---|---|
| Widget Name | Enter the name of the widget. |
Time Series Graph
Displays the performance of a selected monitoring target as a time series graph.
- The time series graph can be changed using the dashboard’s query period setting feature.
- When the mouse cursor is placed over the graph, the time and target performance values can be checked.
| Item | Description |
|---|---|
| Widget Name | Enter the name of the widget. |
| Service | Select the service to check performance. |
| Monitoring Target | Select the monitoring target to display on the graph. |
| Performance Item | Select the performance item to display on the graph. |
| Add Option | Risk intervals can be displayed. |
The graph type can be changed by clicking the icon in the top-right corner of the preview.
- Line graph
- Area graph
- Cumulative bar graph
- Scatter graph
Status Indicator
Displays the statistical values and risk levels of monitoring targets.
When the mouse cursor is placed over the status indicator on the monitoring dashboard, detailed information about the item can be checked.
| Item | Description |
|---|---|
| Widget Name | Enter the name of the widget. |
| Service | Select the service to check performance. |
| Monitoring Target | Select the monitoring target to display on the graph. |
| Performance Item | Select the performance item to display on the graph. |
| Statistics | Select the statistical method to display the performance values of the monitoring target. |
| Add Option | Risk intervals can be displayed. |
Instance Map
Displays the performance values of monitoring targets with different color densities.
- When the mouse cursor is placed over each heatmap, detailed information about the item can be checked.
| Item | Description |
|---|---|
| Widget Name | Enter the name of the widget. |
| Service | Select the service to check performance. |
| Monitoring Target | Select the monitoring target to display on the graph. |
| Performance Item | Select the performance item to display on the graph. |
Viewing Custom Dashboards
To view a custom dashboard, follow these steps:
- Click Custom Dashboard Management in the top-right menu. The Custom Dashboard Management page will be displayed.
- Select the custom dashboard to view from the My Dashboards list.
| Item | Description |
|---|---|
| Dashboard List | Displays the list of custom dashboards. The list can be clicked to change the dashboard to be viewed. |
| Dashboard Name | Displays the name of the user-defined dashboard. |
| Dashboard Settings |
|
| Add Widget | Adds a new widget to the dashboard. |
| Edit Dashboard | Allows editing the currently set custom dashboard.
|
| Custom Widgets | Displays the widgets that make up the dashboard.
|
Downloading Widgets
Graphic widgets can be downloaded as image files (*.png).
When the mouse cursor is placed over a graph widget, a download button will be displayed in the top-right corner. Clicking the download button will download the widget as an image file.
Sharing Custom Dashboards
Custom dashboards can be shared with other users so they can view the dashboard.
To share a custom dashboard, follow these steps:
- Click Custom Dashboard Management in the top-right menu. The Custom Dashboard Management page will be displayed.
- Select the custom dashboard to share from the My Dashboards list.
- Click the Share button next to the dashboard name.
- Enter the user ID or email address of the user to share the dashboard with and click the Share button.
- Click the Confirm button.
Managing Custom Dashboards
You can modify, copy, or delete custom dashboards.
- Click Manage Custom Dashboards from the top right menu. It moves to the Manage Custom Dashboards page.
- From the My Dashboard list, select the Custom Dashboard you want to check.
- Click the More button on the top right of the dashboard, then select the desired command.
- Edit Dashboard: Modify the dashboard name.
- Copy Dashboard: Copy the dashboard to create a new dashboard.
- Share Dashboard: Share the dashboard with other users.
- Delete Dashboard: Delete the dashboard.
Managing Custom Widgets
You can change the position and size of widgets or modify and copy them.
Changing Widget Position
You can change the position of a widget by clicking on its name and dragging it.
Changing Widget Size
To change the size of a widget, follow these steps:
- Place the mouse cursor over the widget. The Resize button appears at the bottom right of the widget.
- Click the Resize button and drag it to adjust the size as needed.
Modifying, Copying, and Deleting Widgets
To modify, copy, or delete a widget, follow these steps:
- Place the mouse cursor over the widget. The More button appears at the top right of the widget.
- Click the More button, then click the desired command.
- Edit Widget: Modify the widget’s chart settings.
- Copy Widget: Copy the widget to create a new widget with the same content.
- Delete Widget: Delete the widget.
2.6 - Managing Agents
An agent is a module that collects performance values, logs, and Windows events from the monitoring target. To use the monitoring function, users must check the installation status of the agent and operate and manage it.
- If IP access control is set for the monitoring target, agent management cannot be used. If agent management is not available, check the IP access control setting status of the selected monitoring target.
- The agent management function uses the sudo command, so the sudo package must be installed in advance.
Agent Management Overview
There are performance collection agents, log collection agents, and Windows event log collection agents.
- Agents must be installed manually by the user on the monitoring target according to their needs.
Managing Agents
Managing Performance Agents
To install and manage agents, follow these steps.
- Click Cloud Monitoring Console > Performance Analysis. Move to the Performance Analysis page.
- On the Performance Analysis page, select the monitoring target and click the Details button. The Monitoring Target Details popup window opens.
- In the Monitoring Target Details popup window, click the Agent tab. Move to the Agent tab.
- Click the Performance button on the Agent tab.
- Click the Copy icon to the right of the installation command to copy the command.
- Paste the copied command into the monitoring target resource.
- Run the copied command on the monitoring target resource.
| Item | Description |
|---|---|
| Installation | Downloads and runs the script file required for agent installation. |
| Start | Runs the agent start command. |
| Stop | Runs the agent stop command. |
| Delete | Runs the agent delete command. |
| Update | Downloads and runs the script file required for agent update. |
To check the agent service status, use the following method:
- Linux: $ sudo systemctl status metricbeat
- Windows: Task Manager → service → metricbeat → Status(Running)
Managing Log Agents
To install and manage agents, follow these steps.
- Click Cloud Monitoring Console > Performance Analysis. Move to the Performance Analysis page.
- On the Performance Analysis page, select the monitoring target and click the Details button. The Monitoring Target Details popup window opens.
- In the Monitoring Target Details popup window, click the Agent tab. Move to the Agent tab.
- Click the Log button.
- Click the Copy icon to the right of the installation command to copy the command.
- Paste the copied command into the monitoring target resource.
- Run the copied command on the monitoring target resource.
| Item | Description |
|---|---|
| Installation | Downloads and runs the script file required for agent installation. |
| Start | Runs the agent start command. |
| Stop | Runs the agent stop command. |
| Delete | Runs the agent delete command. |
| Update | Downloads and runs the script file required for agent update. |
To check the agent service status, use the following method:
- Linux: $ sudo systemctl status filebeat
- Windows: Task Manager → service → filebeat → Status(Running)
To add logs to be monitored, select the log addition action, enter the log name and log path correctly, and click the Generate Command button. Paste the generated command into the monitoring target resource and run it.
Managing Event Agents
To install and manage agents, follow these steps.
- Click Cloud Monitoring Console > Performance Analysis. Move to the Performance Analysis page.
- On the Performance Analysis page, select the monitoring target and click the Details button. The Monitoring Target Details popup window opens.
- In the Monitoring Target Details popup window, click the Agent tab. Move to the Agent tab.
- Click the Event button.
- Click the Copy icon to the right of the installation command to copy the command.
- Paste the copied command into the monitoring target resource.
- Run the copied command on the monitoring target resource.
| Item | Description |
|---|---|
| Installation | Downloads and runs the script file required for agent installation. |
| Start | Runs the agent start command. |
| Stop | Runs the agent stop command. |
| Delete | Runs the agent delete command. |
| Update | Downloads and runs the script file required for agent update. |
To check the agent service status, use the following method:
- Windows: Task Manager → service → winlogbeat → Status(Running)
2.7 - Appendix A. Monitoring Targets by Service
Compute type
Virtual Server
| Division | Monitoring Target | Collection Method | Collection Cycle |
|---|---|---|---|
| Performance | OS | Agent Agentless | 1m |
| Log | OS | Agent | Log Occurrence Time |
| Status | OS | Agentless | 1m |
GPU Server
| Division | Monitoring Target | Collection Method | Collection Cycle |
|---|---|---|---|
| Performance | OS | Agent Agentless | 1m |
| Log | OS | Agent | Log Occurrence Time |
| Status | OS | Agentless | 1m |
Bare Metal Server
| Division | Monitoring Target | Collection Method | Collection Cycle |
|---|---|---|---|
| Performance | OS | Agent | 1m |
| Log | OS | Agent | Log Occurrence Time |
| Status | OS | N/A | - |
Multi-node GPU Cluster [Cluster Fabric]
| Division | Monitoring Target | Collection Method | Collection Cycle |
|---|---|---|---|
| Performance | OS | Agent | 1m |
| Log | OS | Agent | Log Occurrence Time |
| Status | OS | N/A | - |
Multi-node GPU Cluster [Node]
| Division | Monitoring Target | Collection Method | Collection Cycle |
|---|---|---|---|
| Performance | OS | Agent | 1m |
| Log | OS | Agent | Log Occurrence Time |
| Status | OS | N/A | - |
Storage type
All Storage type services have the same monitoring target, collection method, and collection cycle.
- File Storage
- Object Storage
- Block Storage(BM)
- Block Storage(VM)
| Division | Monitoring Target | Collection Method | Collection Cycle |
|---|---|---|---|
| Performance | Storage | Agentless | 1m |
| Log | Storage | N/A | - |
| Status | Storage | Agentless | 1m |
Database type
The monitoring target and collection method, and collection cycle are the same for all types of Database services.
- PostgreSQL(DBaaS)
- MariaDB(DBaaS)
- MySQL(DBaaS)
- Microsoft SQL Server
- EPAS
- CacheStore(DBaaS)
- Redis
- Valkey
| Category | Monitoring Target | Collection Method | Collection Cycle |
|---|---|---|---|
| Performance | Database Process, OS | Agent | 1m |
| Log | Database Process, OS | Agent | Log Occurrence Time |
| Status | Database Process | Agent | 1m |
| OS | Agentless | 1m |
Data Analytics type
| Category | Monitoring Target | Collection Method | Collection Cycle |
|---|---|---|---|
| Performance | Data Analytics Process, OS | Agent | 1m |
| Log | Data Analytics Process, OS | Agent | When a log occurs |
| Status | Data Analytics Process | Agent | 1m |
| OS | Agentless | 1m |
Container type
Kubernetes Engine
| Division | Monitoring Target | Collection Method | Collection Cycle |
|---|---|---|---|
| Performance | Cluster, Namespace, Node, ReplicaSet, Deployment, StatefulSet, DaemonSet, Job, CronJob, Pod | Agentless | 5m |
| Log | Cluster, Namespace, Node, ReplicaSet, Deployment, StatefulSet, DaemonSet, Job, CronJob, Pod | Agentless | When a log occurs |
| Status | Cluster, Namespace, Node, ReplicaSet, Deployment, StatefulSet, DaemonSet, Job, CronJob, Pod | Agentless | 5m |
Container Registry
| Category | Monitoring Target | Collection Method | Collection Cycle |
|---|---|---|---|
| Performance | Container Registry | Agentless | 5m |
| Log | Container Registry | Agentless | When a log occurs |
| Status | Container Registry | Agentless | 5m |
Networking type
VPC
| Category | Monitoring Target | Collection Method | Collection Cycle |
|---|---|---|---|
| Performance | Internet Gateway | Agentless | 5m |
| Log | Internet Gateway | N/A | - |
| Status | Internet Gateway | N/A | - |
Load Balancer(OLD)
Load Balancer(OLD)
| Category | Monitoring Target | Collection Method | Collection Cycle |
|---|---|---|---|
| Performance | Load Balancer | Agentless | 5m |
| Log | Load Balancer | N/A | - |
| Status | Load Balancer | Agentless | 5m |
Load Balancer Listener(OLD)
| Category | Monitoring Target | Collection Method | Collection Cycle |
|---|---|---|---|
| Performance | Load Balancer Listener | Agentless | 5m |
| Log | Load Balancer Listener | N/A | - |
| Status | Load Balancer Listener | Agentless | 5m |
Load Balancer
Load Balancer
| Division | Monitoring Target | Collection Method | Collection Cycle |
|---|---|---|---|
| Performance | Load Balancer | Agentless | 5m |
| Log | Load Balancer | N/A | - |
| Status | Load Balancer | Agentless | 5m |
Load Balancer Listener
| Category | Monitoring Target | Collection Method | Collection Cycle |
|---|---|---|---|
| Performance | Load Balancer Listener | Agentless | 5m |
| Log | Load Balancer Listener | N/A | - |
| Status | Load Balancer Listener | Agentless | 5m |
Load Balancer Server Group
| Category | Monitoring Target | Collection Method | Collection Cycle |
|---|---|---|---|
| Performance | Load Balancer Server Group | Agentless | 5m |
| Log | Load Balancer Server Group | N/A | - |
| Status | Load Balancer Server Group | Agentless | 5m |
Direct Connect
| Division | Monitoring Target | Collection Method | Collection Cycle |
|---|---|---|---|
| Performance | Direct Connect | Agentless | 5m |
| Log | Direct Connect | N/A | - |
| Status | Direct Connect | N/A | - |
Cloud WAN
| Division | Monitoring Target | Collection Method | Collection Cycle |
|---|---|---|---|
| Performance | Cloud WAN | Agentless | 10m |
| Log | Cloud WAN | N/A | - |
| Status | Cloud WAN | Agentless | 10m |
Global CDN
| Category | Monitoring Target | Collection Method | Collection Cycle |
|---|---|---|---|
| Performance | Global CDN | Agentless | 5m |
| Log | Global CDN | N/A | - |
| Status | Global CDN | Agentless | 5m |
2.8 - Appendix B. Performance Items by Service
Compute Type
Virtual Server
Agentless (Basic Metrics)
| Performance Item Group Name | Performance Item Name | Collection Unit | Collection Cycle | Description |
|---|---|---|---|---|
| Memory | Memory Total [Basic] | bytes | 1m | Available memory in bytes |
| Memory | Memory Used [Basic] | bytes | 1m | Currently used memory in bytes |
| Memory | Memory Swap In [Basic] | bytes | 1m | Swapped memory in bytes |
| Memory | Memory Swap Out [Basic] | bytes | 1m | Swapped memory in bytes |
| Memory | Memory Free [Basic] | bytes | 1m | Unused memory in bytes |
| Disk | Disk Read Bytes [Basic] | bytes | 1m | Read bytes |
| Disk | Disk Read Requests [Basic] | cnt | 1m | Number of read requests |
| Disk | Disk Write Bytes [Basic] | bytes | 1m | Write bytes |
| Disk | Disk Write Requests [Basic] | cnt | 1m | Number of write requests |
| CPU | CPU Usage [Basic] | % | 1m | Average system CPU usage over 1 minute |
| State | Instance State [Basic] | state | 1m | Instance state |
| Network | Network In Bytes [Basic] | bytes | 1m | Received bytes |
| Network | Network In Dropped [Basic] | cnt | 1m | Dropped received packets |
| Network | Network In Packets [Basic] | cnt | 1m | Number of received packets |
| Network | Network Out Bytes [Basic] | bytes | 1m | Sent bytes |
| Network | Network Out Dropped [Basic] | cnt | 1m | Dropped sent packets |
| Network | Network Out Packets [Basic] | cnt | 1m | Number of sent packets |
- For Windows OS, you need to install the Balloon Driver or the monitoring performance agent to provide memory performance indicators.
Agent (Detailed Metrics)
| Performance Item Group Name | Performance Item Name | Collection Unit | Collection Cycle | Description |
|---|---|---|---|---|
| CPU | Core Usage [IO Wait] | % | 1m | CPU time spent in wait state (disk wait) |
| CPU | Core Usage [System] | % | 1m | CPU time spent in kernel space |
| CPU | Core Usage [User] | % | 1m | CPU time spent in user space |
| CPU | CPU Cores | cnt | 1m | Number of CPU cores on the host. The maximum value of the unnormalized ratio is 100%* of the number of cores. The unnormalized ratio already reflects this value, and the maximum value is 100%* of the number of cores. |
| CPU | CPU Usage [Active] | % | 1m | CPU time used, excluding idle and IOWait states (using all 4 cores at 100%: 400%) |
| CPU | CPU Usage [Idle] | % | 1m | CPU time spent in idle state |
| CPU | CPU Usage [IO Wait] | % | 1m | CPU time spent in wait state (disk wait) |
| CPU | CPU Usage [System] | % | 1m | CPU time used by the kernel (using all 4 cores at 100%: 400%) |
| CPU | CPU Usage [User] | % | 1m | CPU time used by the user (using all 4 cores at 100%: 400%) |
| CPU | CPU Usage/Core [Active] | % | 1m | CPU time used, excluding idle and IOWait states (normalized by the number of cores, using all 4 cores at 100%: 100%) |
| CPU | CPU Usage/Core [Idle] | % | 1m | CPU time spent in idle state |
| CPU | CPU Usage/Core [IO Wait] | % | 1m | CPU time spent in wait state (disk wait) |
| CPU | CPU Usage/Core [System] | % | 1m | CPU time used by the kernel (normalized by the number of cores, using all 4 cores at 100%: 100%) |
| CPU | CPU Usage/Core [User] | % | 1m | CPU time used by the user (normalized by the number of cores, using all 4 cores at 100%: 100%) |
| Disk | Disk CPU Usage [IO Request] | % | 1m | CPU time spent executing I/O requests to the device (device bandwidth utilization). If this value is close to 100%, the device is saturated. |
| Disk | Disk Queue Size [Avg] | num | 1m | Average queue length of requests executed on the device |
| Disk | Disk Read Bytes | bytes | 1m | Bytes read from the device per second |
| Disk | Disk Read Bytes [Delta Avg] | bytes | 1m | Average of system.diskio.read.bytes_delta for individual disks |
| Disk | Disk Read Bytes [Delta Max] | bytes | 1m | Maximum of system.diskio.read.bytes_delta for individual disks |
| Disk | Disk Read Bytes [Delta Min] | bytes | 1m | Minimum of system.diskio.read.bytes_delta for individual disks |
| Disk | Disk Read Bytes [Delta Sum] | bytes | 1m | Sum of system.diskio.read.bytes_delta for individual disks |
| Disk | Disk Read Bytes [Delta] | bytes | 1m | Delta of system.diskio.read.bytes for individual disks |
| Disk | Disk Read Bytes [Success] | bytes | 1m | Total bytes read successfully. For Linux, it is assumed that the sector size is 512 and the value is the number of sectors read multiplied by 512 |
| Disk | Disk Read Requests | cnt | 1m | Number of read requests to the disk device per second |
| Disk | Disk Read Requests [Delta Avg] | cnt | 1m | Average of system.diskio.read.count_delta for individual disks |
| Disk | Disk Read Requests [Delta Max] | cnt | 1m | Maximum of system.diskio.read.count_delta for individual disks |
| Disk | Disk Read Requests [Delta Min] | cnt | 1m | Minimum of system.diskio.read.count_delta for individual disks |
| Disk | Disk Read Requests [Delta Sum] | cnt | 1m | Sum of system.diskio.read.count_delta for individual disks |
| Disk | Disk Read Requests [Success Delta] | cnt | 1m | Delta of system.diskio.read.count for individual disks |
| Disk | Disk Read Requests [Success] | cnt | 1m | Total number of successful read completions |
| Disk | Disk Request Size [Avg] | num | 1m | Average size of requests executed on the device (in sectors) |
| Disk | Disk Service Time [Avg] | ms | 1m | Average service time of I/O requests executed on the device (in milliseconds) |
| Disk | Disk Wait Time [Avg] | ms | 1m | Average time spent waiting for I/O requests to be executed on the device |
| Disk | Disk Wait Time [Read] | ms | 1m | Average disk read wait time |
| Disk | Disk Wait Time [Write] | ms | 1m | Average disk write wait time |
| Disk | Disk Write Bytes [Delta Avg] | bytes | 1m | Average of system.diskio.write.bytes_delta for individual disks |
| Disk | Disk Write Bytes [Delta Max] | bytes | 1m | Maximum of system.diskio.write.bytes_delta for individual disks |
| Disk | Disk Write Bytes [Delta Min] | bytes | 1m | Minimum of system.diskio.write.bytes_delta for individual disks |
| Disk | Disk Write Bytes [Delta Sum] | bytes | 1m | Sum of system.diskio.write.bytes_delta for individual disks |
| Disk | Disk Write Bytes [Delta] | bytes | 1m | Delta of system.diskio.write.bytes for individual disks |
| Disk | Disk Write Bytes [Success] | bytes | 1m | Total bytes written successfully. For Linux, it is assumed that the sector size is 512 and the value is the number of sectors written multiplied by 512 |
| Disk | Disk Write Requests | cnt | 1m | Number of write requests to the disk device per second |
| Disk | Disk Write Requests [Delta Avg] | cnt | 1m | Average of system.diskio.write.count_delta for individual disks |
| Disk | Disk Write Requests [Delta Max] | cnt | 1m | Maximum of system.diskio.write.count_delta for individual disks |
| Disk | Disk Write Requests [Delta Min] | cnt | 1m | Minimum of system.diskio.write.count_delta for individual disks |
| Disk | Disk Write Requests [Delta Sum] | cnt | 1m | Sum of system.diskio.write.count_delta for individual disks |
| Disk | Disk Write Requests [Success Delta] | cnt | 1m | Delta of system.diskio.write.count for individual disks |
| Disk | Disk Write Requests [Success] | cnt | 1m | Total number of successful writes |
| Disk | Disk Writes Bytes | bytes | 1m | Bytes written to the device per second |
| FileSystem | Filesystem Hang Check | state | 1m | Filesystem (local/NFS) hang check (normal: 1, abnormal: 0) |
| FileSystem | Filesystem Nodes | cnt | 1m | Total number of file nodes in the filesystem |
| FileSystem | Filesystem Nodes [Free] | cnt | 1m | Total number of available file nodes in the filesystem |
| FileSystem | Filesystem Size [Available] | bytes | 1m | Disk space available for non-privileged users (in bytes) |
| FileSystem | Filesystem Size [Free] | bytes | 1m | Available disk space (in bytes) |
| FileSystem | Filesystem Size [Total] | bytes | 1m | Total disk space (in bytes) |
| FileSystem | Filesystem Usage | % | 1m | Percentage of used disk space |
| FileSystem | Filesystem Usage [Avg] | % | 1m | Average of filesystem.used.pct for individual filesystems |
| FileSystem | Filesystem Usage [Inode] | % | 1m | Inode usage rate |
| FileSystem | Filesystem Usage [Max] | % | 1m | Maximum of filesystem.used.pct for individual filesystems |
| FileSystem | Filesystem Usage [Min] | % | 1m | Minimum of filesystem.used.pct for individual filesystems |
| FileSystem | Filesystem Usage [Total] | % | 1m | - |
| FileSystem | Filesystem Used | bytes | 1m | Used disk space (in bytes) |
| FileSystem | Filesystem Used [Inode] | bytes | 1m | Inode usage |
| Memory | Memory Free | bytes | 1m | Total available memory (in bytes), excluding system cache and buffer memory (see system.memory.actual.free). |
| Memory | Memory Free [Actual] | bytes | 1m | Actual available memory (in bytes). The calculation method varies depending on the OS. For Linux, it is the value of MemAvailable in /proc/meminfo, or the calculated value using available memory and cache/buffer memory if /proc/meminfo is not available. For OSX, it is the sum of available memory and inactive memory. For Windows, it is the same value as system.memory.free. |
| Memory | Memory Free [Swap] | bytes | 1m | Available swap memory |
| Memory | Memory Total | bytes | 1m | Total memory |
| Memory | Memory Total [Swap] | bytes | 1m | Total swap memory |
| Memory | Memory Usage | % | 1m | Percentage of used memory |
| Memory | Memory Usage [Actual] | % | 1m | Percentage of actually used memory |
| Memory | Memory Usage [Cache Swap] | % | 1m | Cache swap usage rate |
| Memory | Memory Usage [Swap] | % | 1m | Percentage of used swap memory |
| Memory | Memory Used | bytes | 1m | Used memory |
| Memory | Memory Used [Actual] | bytes | 1m | Actually used memory (in bytes). The value of total memory minus used memory. The available memory is calculated differently depending on the OS (see system.actual.free). |
| Memory | Memory Used [Swap] | bytes | 1m | Used swap memory |
| Network | Collisions | cnt | 1m | Network collisions |
| Network | Network In Bytes | bytes | 1m | Received bytes |
| Network | Network In Bytes [Delta Avg] | bytes | 1m | Average of system.network.in.bytes_delta for individual networks |
| Network | Network In Bytes [Delta Max] | bytes | 1m | Maximum of system.network.in.bytes_delta for individual networks |
| Network | Network In Bytes [Delta Min] | bytes | 1m | Minimum of system.network.in.bytes_delta for individual networks |
| Network | Network In Bytes [Delta Sum] | bytes | 1m | Sum of system.network.in.bytes_delta for individual networks |
| Network | Network In Bytes [Delta] | bytes | 1m | Delta of received bytes |
| Network | Network In Dropped | cnt | 1m | Dropped received packets |
| Network | Network In Errors | cnt | 1m | Number of receive errors |
| Network | Network In Packets | cnt | 1m | Number of received packets |
| Network | Network In Packets [Delta Avg] | cnt | 1m | Average of system.network.in.packets_delta for individual networks |
| Network | Network In Packets [Delta Max] | cnt | 1m | Maximum of system.network.in.packets_delta for individual networks |
| Network | Network In Packets [Delta Min] | cnt | 1m | Minimum of system.network.in.packets_delta for individual networks |
| Network | Network In Packets [Delta Sum] | cnt | 1m | Sum of system.network.in.packets_delta for individual networks |
| Network | Network In Packets [Delta] | cnt | 1m | Delta of received packets |
| Network | Network Out Bytes | bytes | 1m | Sent bytes |
| Network | Network Out Bytes [Delta Avg] | bytes | 1m | Average of system.network.out.bytes_delta for individual networks |
| Network | Network Out Bytes [Delta Max] | bytes | 1m | Maximum of system.network.out.bytes_delta for individual networks |
| Network | Network Out Bytes [Delta Min] | bytes | 1m | Minimum of system.network.out.bytes_delta for individual networks |
| Network | Network Out Bytes [Delta Sum] | bytes | 1m | Sum of system.network.out.bytes_delta for individual networks |
| Network | Network Out Bytes [Delta] | bytes | 1m | Delta of sent bytes |
| Network | Network Out Dropped | cnt | 1m | Dropped sent packets. This value is not reported by the OS, so it is always 0 on Darwin and BSD. |
| Network | Network Out Errors | cnt | 1m | Number of transmit errors |
| Network | Network Out Packets | cnt | 1m | Number of sent packets |
| Network | Network Out Packets [Delta Avg] | cnt | 1m | Average of system.network.out.packets_delta for individual networks |
| Network | Network Out Packets [Delta Max] | cnt | 1m | Maximum of system.network.out.packets_delta for individual networks |
| Network | Network Out Packets [Delta Min] | cnt | 1m | Minimum of system.network.out.packets_delta for individual networks |
| Network | Network Out Packets [Delta Sum] | cnt | 1m | Sum of system.network.out.packets_delta for individual networks |
| Network | Network Out Packets [Delta] | cnt | 1m | Delta of sent packets |
| Network | Open Connections [TCP] | cnt | 1m | Number of open TCP connections |
| Network | Open Connections [UDP] | cnt | 1m | Number of open UDP connections |
| Network | Port Usage | % | 1m | Port usage rate |
| Network | SYN Sent Sockets | cnt | 1m | Number of sockets in the SYN_SENT state (when connecting to a remote host) |
| Process | Kernel PID Max | cnt | 1m | Value of kernel.pid_max |
| Process | Kernel Thread Max | cnt | 1m | Value of kernel.threads-max |
| Process | Process CPU Usage | % | 1m | Percentage of CPU time consumed by the process since the last update. This value is similar to the %CPU value displayed by the top command on Unix systems. |
| Process | Process CPU Usage/Core | % | 1m | Percentage of CPU time used by the process since the last event. This value is normalized by the number of cores and ranges from 0 to 100%. |
| Process | Process Memory Usage | % | 1m | Percentage of main memory (RAM) used by the process |
| Process | Process Memory Used | bytes | 1m | Resident Set size. The amount of memory used by the process in RAM. On Windows, this is the current working set size. |
| Process | Process PID | PID | 1m | Process PID |
| Process | Process PPID | PID | 1m | Parent process PID |
| Process | Processes [Dead] | cnt | 1m | Number of dead processes |
| Process | Processes [Idle] | cnt | 1m | Number of idle processes |
| Process | Processes [Running] | cnt | 1m | Number of running processes |
| Process | Processes [Sleeping] | cnt | 1m | Number of sleeping processes |
| Process | Processes [Stopped] | cnt | 1m | Number of stopped processes |
| Process | Processes [Total] | cnt | 1m | Total number of processes |
| Process | Processes [Unknown] | cnt | 1m | Number of processes with unknown or unsearchable status |
| Process | Processes [Zombie] | cnt | 1m | Number of zombie processes |
| Process | Running Process Usage | % | 1m | Process usage rate |
| Process | Running Processes | cnt | 1m | Number of running processes |
| Process | Running Thread Usage | % | 1m | Thread usage rate |
| Process | Running Threads | cnt | 1m | Total number of threads running in running processes |
| System | Context Switches | cnt | 1m | Number of context switches (per second) |
| System | Load/Core [1 min] | cnt | 1m | Load over the last 1 minute, normalized by the number of cores |
| System | Load/Core [15 min] | cnt | 1m | Load over the last 15 minutes, normalized by the number of cores |
| System | Load/Core [5 min] | cnt | 1m | Load over the last 5 minutes, normalized by the number of cores |
| System | Multipaths [Active] | cnt | 1m | Number of active paths for external storage connections |
| System | Multipaths [Failed] | cnt | 1m | Number of failed paths for external storage connections |
| System | Multipaths [Faulty] | cnt | 1m | Number of faulty paths for external storage connections |
| System | NTP Offset | num | 1m | Measured offset (time difference between the NTP server and the local environment) of the last sample |
| System | Run Queue Length | num | 1m | Length of the run queue |
| System | Uptime | ms | 1m | System uptime (in milliseconds) |
| Windows | Context Switchies | cnt | 1m | Number of CPU context switches (per second) |
| Windows | Disk Read Bytes [Sec] | cnt | 1m | Number of bytes read from the Windows logical disk per second |
| Windows | Disk Read Time [Avg] | sec | 1m | Average time spent reading data (in seconds) |
| Windows | Disk Transfer Time [Avg] | sec | 1m | Average disk wait time |
| Windows | Disk Usage | % | 1m | Disk usage rate |
| Windows | Disk Write Bytes [Sec] | cnt | 1m | Number of bytes written to the Windows logical disk per second |
| Windows | Disk Write Time [Avg] | sec | 1m | Average time spent writing data (in seconds) |
| Windows | Pagingfile Usage | % | 1m | Paging file usage rate |
| Windows | Pool Used [Non Paged] | bytes | 1m | Non-paged pool usage of kernel memory |
| Windows | Pool Used [Paged] | bytes | 1m | Paged pool usage of kernel memory |
| Windows | Process [Running] | cnt | 1m | Number of currently running processes |
| Windows | Threads [Running] | cnt | 1m | Number of currently running threads |
| Windows | Threads [Waiting] | cnt | 1m | Number of threads waiting for processor time |
GPU Server
Agentless (Basic Metrics)
| Performance Item Group Name | Performance Item Name | Collection Unit | Collection Cycle | Description |
|---|---|---|---|---|
| Memory | Memory Total [Basic] | bytes | 1m | Available memory in bytes |
| Memory | Memory Used [Basic] | bytes | 1m | Currently used memory in bytes |
| Memory | Memory Swap In [Basic] | bytes | 1m | Swapped memory in bytes |
| Memory | Memory Swap Out [Basic] | bytes | 1m | Swapped memory in bytes |
| Memory | Memory Free [Basic] | bytes | 1m | Unused memory in bytes |
| Disk | Disk Read Bytes [Basic] | bytes | 1m | Read bytes |
| Disk | Disk Read Requests [Basic] | cnt | 1m | Number of read requests |
| Disk | Disk Write Bytes [Basic] | bytes | 1m | Write bytes |
| Disk | Disk Write Requests [Basic] | cnt | 1m | Number of write requests |
| CPU | CPU Usage [Basic] | % | 1m | Average system CPU usage over 1 minute |
| State | Instance State [Basic] | state | 1m | Instance state |
| Network | Network In Bytes [Basic] | bytes | 1m | Received bytes |
| Network | Network In Dropped [Basic] | cnt | 1m | Dropped received packets |
| Network | Network In Packets [Basic] | cnt | 1m | Number of received packets |
| Network | Network Out Bytes [Basic] | bytes | 1m | Sent bytes |
| Network | Network Out Dropped [Basic] | cnt | 1m | Dropped sent packets |
| Network | Network Out Packets [Basic] | cnt | 1m | Number of sent packets |
Agent (Detailed Metrics)
| Performance Item Group Name | Performance Item Name | Collection Unit | Collection Cycle | Description |
|---|---|---|---|---|
| GPU | GPU Count | cnt | 1m | Number of GPUs |
| GPU | GPU Memory Usage | % | 1m | GPU memory usage rate |
| GPU | GPU Memory Used | bytes | 1m | GPU memory usage |
| GPU | GPU Temperature | ℃ | 1m | GPU temperature |
| GPU | GPU Usage | % | 1m | Total GPU usage rate (using all 8 GPUs at 100%: 800%) |
| GPU | GPU Usage [Avg] | % | 1m | Average GPU usage rate (%) |
| GPU | GPU Power Cap | W | 1m | Maximum power capacity of the GPU |
| GPU | GPU Power Usage | W | 1m | Current power usage of the GPU |
| GPU | GPU Memory Usage [Avg] | % | 1m | Average GPU memory usage rate |
| GPU | GPU Count in use | cnt | 1m | Number of GPUs in use by jobs running on the node |
| GPU | Execution State for nvidia-smi | state | 1m | Execution result of the nvidia-smi command |
| CPU | Core Usage [IO Wait] | % | 1m | CPU time spent in wait state (disk wait) |
| CPU | Core Usage [System] | % | 1m | CPU time spent in kernel space |
| CPU | Core Usage [User] | % | 1m | CPU time spent in user space |
| CPU | CPU Cores | cnt | 1m | Number of CPU cores on the host. The maximum value of the unnormalized ratio is 100%* of the number of cores. The unnormalized ratio already reflects this value, and the maximum value is 100%* of the number of cores. |
| CPU | CPU Usage [Active] | % | 1m | CPU time used, excluding idle and IOWait states (using all 4 cores at 100%: 400%) |
| CPU | CPU Usage [Idle] | % | 1m | CPU time spent in idle state |
| CPU | CPU Usage [IO Wait] | % | 1m | CPU time spent in wait state (disk wait) |
| CPU | CPU Usage [System] | % | 1m | CPU time used by the kernel (using all 4 cores at 100%: 400%) |
| CPU | CPU Usage [User] | % | 1m | CPU time used by the user (using all 4 cores at 100%: 400%) |
| CPU | CPU Usage/Core [Active] | % | 1m | CPU time used, excluding idle and IOWait states (normalized by the number of cores, using all 4 cores at 100%: 100%) |
| CPU | CPU Usage/Core [Idle] | % | 1m | CPU time spent in idle state |
| CPU | CPU Usage/Core [IO Wait] | % | 1m | CPU time spent in wait state (disk wait) |
| CPU | CPU Usage/Core [System] | % | 1m | CPU time used by the kernel (normalized by the number of cores, using all 4 cores at 100%: 100%) |
| CPU | CPU Usage/Core [User] | % | 1m | CPU time used by the user (normalized by the number of cores, using all 4 cores at 100%: 100%) |
| Disk | Disk CPU Usage [IO Request] | % | 1m | The ratio of CPU time spent executing I/O requests for the device (device bandwidth utilization). If this value is close to 100%, the device is in a saturated state. |
| Disk | Disk Queue Size [Avg] | num | 1m | The average queue length of requests executed for the device. |
| Disk | Disk Read Bytes | bytes | 1m | The number of bytes read from the device per second. |
| Disk | Disk Read Bytes [Delta Avg] | bytes | 1m | The average of system.diskio.read.bytes_delta for individual disks. |
| Disk | Disk Read Bytes [Delta Max] | bytes | 1m | The maximum of system.diskio.read.bytes_delta for individual disks. |
| Disk | Disk Read Bytes [Delta Min] | bytes | 1m | The minimum of system.diskio.read.bytes_delta for individual disks. |
| Disk | Disk Read Bytes [Delta Sum] | bytes | 1m | The sum of system.diskio.read.bytes_delta for individual disks. |
| Disk | Disk Read Bytes [Delta] | bytes | 1m | The delta value of system.diskio.read.bytes for individual disks. |
| Disk | Disk Read Bytes [Success] | bytes | 1m | The total number of bytes read successfully. On Linux, it is assumed that the sector size is 512 and the value is calculated by multiplying the number of sectors read by 512. |
| Disk | Disk Read Requests | cnt | 1m | The number of read requests for the disk device per second. |
| Disk | Disk Read Requests [Delta Avg] | cnt | 1m | The average of system.diskio.read.count_delta for individual disks. |
| Disk | Disk Read Requests [Delta Max] | cnt | 1m | The maximum of system.diskio.read.count_delta for individual disks. |
| Disk | Disk Read Requests [Delta Min] | cnt | 1m | The minimum of system.diskio.read.count_delta for individual disks. |
| Disk | Disk Read Requests [Delta Sum] | cnt | 1m | The sum of system.diskio.read.count_delta for individual disks. |
| Disk | Disk Read Requests [Success Delta] | cnt | 1m | The delta value of system.diskio.read.count for individual disks. |
| Disk | Disk Read Requests [Success] | cnt | 1m | The total number of successful read requests. |
| Disk | Disk Request Size [Avg] | num | 1m | The average size of requests executed for the device (in sectors). |
| Disk | Disk Service Time [Avg] | ms | 1m | The average service time for input requests executed for the device (in milliseconds). |
| Disk | Disk Wait Time [Avg] | ms | 1m | The average time spent executing requests for the device. |
| Disk | Disk Wait Time [Read] | ms | 1m | The average disk wait time for read operations. |
| Disk | Disk Wait Time [Write] | ms | 1m | The average disk wait time for write operations. |
| Disk | Disk Write Bytes [Delta Avg] | bytes | 1m | The average of system.diskio.write.bytes_delta for individual disks. |
| Disk | Disk Write Bytes [Delta Max] | bytes | 1m | The maximum of system.diskio.write.bytes_delta for individual disks. |
| Disk | Disk Write Bytes [Delta Min] | bytes | 1m | The minimum of system.diskio.write.bytes_delta for individual disks. |
| Disk | Disk Write Bytes [Delta Sum] | bytes | 1m | The sum of system.diskio.write.bytes_delta for individual disks. |
| Disk | Disk Write Bytes [Delta] | bytes | 1m | The delta value of system.diskio.write.bytes for individual disks. |
| Disk | Disk Write Bytes [Success] | bytes | 1m | The total number of bytes written successfully. On Linux, it is assumed that the sector size is 512 and the value is calculated by multiplying the number of sectors written by 512. |
| Disk | Disk Write Requests | cnt | 1m | The number of write requests for the disk device per second. |
| Disk | Disk Write Requests [Delta Avg] | cnt | 1m | The average of system.diskio.write.count_delta for individual disks. |
| Disk | Disk Write Requests [Delta Max] | cnt | 1m | The maximum of system.diskio.write.count_delta for individual disks. |
| Disk | Disk Write Requests [Delta Min] | cnt | 1m | The minimum of system.diskio.write.count_delta for individual disks. |
| Disk | Disk Write Requests [Delta Sum] | cnt | 1m | The sum of system.diskio.write.count_delta for individual disks. |
| Disk | Disk Write Requests [Success Delta] | cnt | 1m | The delta value of system.diskio.write.count for individual disks. |
| Disk | Disk Write Requests [Success] | cnt | 1m | The total number of successful write requests. |
| Disk | Disk Writes Bytes | bytes | 1m | The number of bytes written to the device per second. |
| FileSystem | Filesystem Hang Check | state | 1m | Filesystem (local/NFS) hang check (normal: 1, abnormal: 0). |
| FileSystem | Filesystem Nodes | cnt | 1m | The total number of file nodes in the file system. |
| FileSystem | Filesystem Nodes [Free] | cnt | 1m | The total number of available file nodes in the file system. |
| FileSystem | Filesystem Size [Available] | bytes | 1m | The available disk space (in bytes) that can be used by non-privileged users. |
| FileSystem | Filesystem Size [Free] | bytes | 1m | The available disk space (in bytes). |
| FileSystem | Filesystem Size [Total] | bytes | 1m | The total disk space (in bytes). |
| FileSystem | Filesystem Usage | % | 1m | The percentage of used disk space. |
| FileSystem | Filesystem Usage [Avg] | % | 1m | The average of filesystem.used.pct for individual file systems. |
| FileSystem | Filesystem Usage [Inode] | % | 1m | The inode usage rate. |
| FileSystem | Filesystem Usage [Max] | % | 1m | The maximum of filesystem.used.pct for individual file systems. |
| FileSystem | Filesystem Usage [Min] | % | 1m | The minimum of filesystem.used.pct for individual file systems. |
| FileSystem | Filesystem Usage [Total] | % | 1m | - |
| FileSystem | Filesystem Used | bytes | 1m | The used disk space (in bytes). |
| FileSystem | Filesystem Used [Inode] | bytes | 1m | The inode usage. |
| Memory | Memory Free | bytes | 1m | The total available memory (in bytes), excluding memory used by system cache and buffers (see system.memory.actual.free). |
| Memory | Memory Free [Actual] | bytes | 1m | The actual available memory (in bytes), which varies depending on the OS. On Linux, it is calculated using /proc/meminfo, and on OSX, it is the sum of available and inactive memory. On Windows, it is the same as system.memory.free. |
| Memory | Memory Free [Swap] | bytes | 1m | The available swap memory. |
| Memory | Memory Total | bytes | 1m | The total memory. |
| Memory | Memory Total [Swap] | bytes | 1m | The total swap memory. |
| Memory | Memory Usage | % | 1m | The percentage of used memory. |
| Memory | Memory Usage [Actual] | % | 1m | The percentage of actual used memory. |
| Memory | Memory Usage [Cache Swap] | % | 1m | The cache swap usage rate. |
| Memory | Memory Usage [Swap] | % | 1m | The percentage of used swap memory. |
| Memory | Memory Used | bytes | 1m | The used memory. |
| Memory | Memory Used [Actual] | bytes | 1m | The actual used memory (in bytes), which is the total memory minus the used memory. The available memory varies depending on the OS (see system.actual.free). |
| Memory | Memory Used [Swap] | bytes | 1m | The used swap memory. |
| Network | Collisions | cnt | 1m | Network collisions. |
| Network | Network In Bytes | bytes | 1m | The number of bytes received. |
| Network | Network In Bytes [Delta Avg] | bytes | 1m | The average of system.network.in.bytes_delta for individual networks. |
| Network | Network In Bytes [Delta Max] | bytes | 1m | The maximum of system.network.in.bytes_delta for individual networks. |
| Network | Network In Bytes [Delta Min] | bytes | 1m | The minimum of system.network.in.bytes_delta for individual networks. |
| Network | Network In Bytes [Delta Sum] | bytes | 1m | The sum of system.network.in.bytes_delta for individual networks. |
| Network | Network In Bytes [Delta] | bytes | 1m | The delta value of the number of bytes received. |
| Network | Network In Dropped | cnt | 1m | The number of packets dropped during reception. |
| Network | Network In Errors | cnt | 1m | The number of errors during reception. |
| Network | Network In Packets | cnt | 1m | The number of packets received. |
| Network | Network In Packets [Delta Avg] | cnt | 1m | The average of system.network.in.packets_delta for individual networks. |
| Network | Network In Packets [Delta Max] | cnt | 1m | The maximum of system.network.in.packets_delta for individual networks. |
| Network | Network In Packets [Delta Min] | cnt | 1m | The minimum of system.network.in.packets_delta for individual networks. |
| Network | Network In Packets [Delta Sum] | cnt | 1m | The sum of system.network.in.packets_delta for individual networks. |
| Network | Network In Packets [Delta] | cnt | 1m | The delta value of the number of packets received. |
| Network | Network Out Bytes | bytes | 1m | The number of bytes sent. |
| Network | Network Out Bytes [Delta Avg] | bytes | 1m | The average of system.network.out.bytes_delta for individual networks. |
| Network | Network Out Bytes [Delta Max] | bytes | 1m | The maximum of system.network.out.bytes_delta for individual networks. |
| Network | Network Out Bytes [Delta Min] | bytes | 1m | The minimum of system.network.out.bytes_delta for individual networks. |
| Network | Network Out Bytes [Delta Sum] | bytes | 1m | The sum of system.network.out.bytes_delta for individual networks. |
| Network | Network Out Bytes [Delta] | bytes | 1m | The delta value of the number of bytes sent. |
| Network | Network Out Dropped | cnt | 1m | The number of packets dropped during transmission. This value is not reported by the OS and is always 0 on Darwin and BSD. |
| Network | Network Out Errors | cnt | 1m | The number of errors during transmission. |
| Network | Network Out Packets | cnt | 1m | The number of packets sent. |
| Network | Network Out Packets [Delta Avg] | cnt | 1m | The average of system.network.out.packets_delta for individual networks. |
| Network | Network Out Packets [Delta Max] | cnt | 1m | The maximum of system.network.out.packets_delta for individual networks. |
| Network | Network Out Packets [Delta Min] | cnt | 1m | The minimum of system.network.out.packets_delta for individual networks. |
| Network | Network Out Packets [Delta Sum] | cnt | 1m | The sum of system.network.out.packets_delta for individual networks. |
| Network | Network Out Packets [Delta] | cnt | 1m | The delta value of the number of packets sent. |
| Network | Open Connections [TCP] | cnt | 1m | The number of open TCP connections. |
| Network | Open Connections [UDP] | cnt | 1m | The number of open UDP connections. |
| Network | Port Usage | % | 1m | The port usage rate. |
| Network | SYN Sent Sockets | cnt | 1m | The number of sockets in the SYN_SENT state (when connecting to a remote host). |
| Process | Kernel PID Max | cnt | 1m | The kernel.pid_max value. |
| Process | Kernel Thread Max | cnt | 1m | The kernel.threads-max value. |
| Process | Process CPU Usage | % | 1m | The percentage of CPU time consumed by the process since the last update. This value is similar to the %CPU value displayed by the top command on Unix systems. |
| Process | Process CPU Usage/Core | % | 1m | The percentage of CPU time used by the process since the last event, normalized by the number of cores (0-100%). |
| Process | Process Memory Usage | % | 1m | The percentage of main memory (RAM) used by the process. |
| Process | Process Memory Used | bytes | 1m | The resident set size, which is the amount of memory used by the process in RAM. On Windows, it is the current working set size. |
| Process | Process PID | PID | 1m | The process ID. |
| Process | Process PPID | PID | 1m | The parent process ID. |
| Process | Processes [Dead] | cnt | 1m | The number of dead processes. |
| Process | Processes [Idle] | cnt | 1m | The number of idle processes. |
| Process | Processes [Running] | cnt | 1m | The number of running processes. |
| Process | Processes [Sleeping] | cnt | 1m | The number of sleeping processes. |
| Process | Processes [Stopped] | cnt | 1m | The number of stopped processes. |
| Process | Processes [Total] | cnt | 1m | The total number of processes. |
| Process | Processes [Unknown] | cnt | 1m | The number of processes with unknown or unsearchable states. |
| Process | Processes [Zombie] | cnt | 1m | The number of zombie processes. |
| Process | Running Process Usage | % | 1m | The process usage rate. |
| Process | Running Processes | cnt | 1m | The number of running processes. |
| Process | Running Thread Usage | % | 1m | The thread usage rate. |
| Process | Running Threads | cnt | 1m | The total number of threads running in running processes. |
| System | Context Switches | cnt | 1m | The number of context switches per second. |
| System | Load/Core [1 min] | cnt | 1m | The load average over the last 1 minute, normalized by the number of cores. |
| System | Load/Core [15 min] | cnt | 1m | The load average over the last 15 minutes, normalized by the number of cores. |
| System | Load/Core [5 min] | cnt | 1m | The load average over the last 5 minutes, normalized by the number of cores. |
| System | Multipaths [Active] | cnt | 1m | The number of active paths for external storage connections. |
| System | Multipaths [Failed] | cnt | 1m | The number of failed paths for external storage connections. |
| System | Multipaths [Faulty] | cnt | 1m | The number of faulty paths for external storage connections. |
| System | NTP Offset | num | 1m | The measured offset (time difference between the NTP server and the local environment) of the last sample. |
| System | Run Queue Length | num | 1m | The length of the run queue. |
| System | Uptime | ms | 1m | The OS uptime (in milliseconds). |
| Windows | Context Switchies | cnt | 1m | The number of CPU context switches per second. |
| Windows | Disk Read Bytes [Sec] | cnt | 1m | The number of bytes read from the Windows logical disk per second. |
| Windows | Disk Read Time [Avg] | sec | 1m | The average time spent reading data (in seconds). |
| Windows | Disk Transfer Time [Avg] | sec | 1m | The average disk wait time. |
| Windows | Disk Usage | % | 1m | The disk usage rate. |
| Windows | Disk Write Bytes [Sec] | cnt | 1m | The number of bytes written to the Windows logical disk per second. |
| Windows | Disk Write Time [Avg] | sec | 1m | The average time spent writing data (in seconds). |
| Windows | Pagingfile Usage | % | 1m | The paging file usage rate. |
| Windows | Pool Used [Non Paged] | bytes | 1m | The Nonpaged Pool usage of kernel memory. |
| Windows | Pool Used [Paged] | bytes | 1m | The Paged Pool usage of kernel memory. |
| Windows | Process [Running] | cnt | 1m | The number of currently running processes. |
| Windows | Threads [Running] | cnt | 1m | The number of currently running threads. |
| Windows | Threads [Waiting] | cnt | 1m | The number of threads waiting for processor time. |
Bare Metal Server
Agent (Detailed Metrics)
| Performance Item Group Name | Performance Item Name | Collection Unit | Collection Cycle | Description |
|---|---|---|---|---|
| CPU | Core Usage [IO Wait] | % | 1m | The ratio of CPU time spent in a waiting state (disk wait). |
| CPU | Core Usage [System] | % | 1m | The percentage of CPU time used by the kernel. |
| CPU | Core Usage [User] | % | 1m | The percentage of CPU time used in the user space. |
| CPU | CPU Cores | cnt | 1m | The number of CPU cores on the host. The maximum value for unnormalized rates is 100% * the number of cores. The maximum value for normalized rates is 100%. |
| CPU | CPU Usage [Active] | % | 1m | The percentage of CPU time used, excluding idle and IOWait states (all 4 cores using 100%: 400%). |
| CPU | CPU Usage [Idle] | % | 1m | The ratio of CPU time spent in an idle state. |
| CPU | CPU Usage [IO Wait] | % | 1m | The ratio of CPU time spent in a waiting state (disk wait). |
| CPU | CPU Usage [System] | % | 1m | The percentage of CPU time used by the kernel (all 4 cores using 100%: 400%). |
| CPU | CPU Usage [User] | % | 1m | The percentage of CPU time used in the user area (all 4 cores using 100%: 400%). |
| CPU | CPU Usage/Core [Active] | % | 1m | The percentage of CPU time used, excluding idle and IOWait states (normalized by the number of cores, all 4 cores using 100%: 100%). |
| CPU | CPU Usage/Core [Idle] | % | 1m | The ratio of CPU time spent in an idle state. |
| CPU | CPU Usage/Core [IO Wait] | % | 1m | The ratio of CPU time spent in a waiting state (disk wait). |
| CPU | CPU Usage/Core [System] | % | 1m | The percentage of CPU time used by the kernel (normalized by the number of cores, all 4 cores using 100%: 100%). |
| CPU | CPU Usage/Core [User] | % | 1m | The percentage of CPU time used in the user area (normalized by the number of cores, all 4 cores using 100%: 100%). |
| Disk | Disk CPU Usage [IO Request] | % | 1m | The ratio of CPU time spent executing I/O requests for the device (device bandwidth utilization). If this value is close to 100%, the device is in a saturated state. |
| Disk | Disk Queue Size [Avg] | num | 1m | The average queue length of requests executed for the device. |
| Disk | Disk Read Bytes | bytes | 1m | The number of bytes read from the device per second. |
| Disk | Disk Read Bytes [Delta Avg] | bytes | 1m | The average of system.diskio.read.bytes_delta for individual disks. |
| Disk | Disk Read Bytes [Delta Max] | bytes | 1m | The maximum of system.diskio.read.bytes_delta for individual disks. |
| Disk | Disk Read Bytes [Delta Min] | bytes | 1m | The minimum of system.diskio.read.bytes_delta for individual disks. |
| Disk | Disk Read Bytes [Delta Sum] | bytes | 1m | The sum of system.diskio.read.bytes_delta for individual disks. |
| Disk | Disk Read Bytes [Delta] | bytes | 1m | The delta value of system.diskio.read.bytes for individual disks. |
| Disk | Disk Read Bytes [Success] | bytes | 1m | The total number of bytes read successfully. On Linux, it is assumed that the sector size is 512 and the value is calculated by multiplying the number of sectors read by 512. |
| Disk | Disk Read Requests | cnt | 1m | The number of read requests for the disk device per second. |
| Disk | Disk Read Requests [Delta Avg] | cnt | 1m | The average of system.diskio.read.count_delta for individual disks. |
| Disk | Disk Read Requests [Delta Max] | cnt | 1m | The maximum of system.diskio.read.count_delta for individual disks. |
| Disk | Disk Read Requests [Delta Min] | cnt | 1m | The minimum of system.diskio.read.count_delta for individual disks. |
| Disk | Disk Read Requests [Delta Sum] | cnt | 1m | The sum of system.diskio.read.count_delta for individual disks. |
| Disk | Disk Read Requests [Success Delta] | cnt | 1m | The delta value of system.diskio.read.count for individual disks. |
| Disk | Disk Read Requests [Success] | cnt | 1m | The total number of successful read requests. |
| Disk | Disk Request Size [Avg] | num | 1m | The average size of requests executed for the device (in sectors). |
| Disk | Disk Service Time [Avg] | ms | 1m | The average service time for input requests executed for the device (in milliseconds). |
| Disk | Disk Wait Time [Avg] | ms | 1m | The average time spent executing requests for the device. |
| Disk | Disk Wait Time [Read] | ms | 1m | The average disk wait time for read operations. |
| Disk | Disk Wait Time [Write] | ms | 1m | The average disk wait time for write operations. |
| Disk | Disk Write Bytes [Delta Avg] | bytes | 1m | The average of system.diskio.write.bytes_delta for individual disks. |
| Disk | Disk Write Bytes [Delta Max] | bytes | 1m | The maximum of system.diskio.write.bytes_delta for individual disks. |
| Disk | Disk Write Bytes [Delta Min] | bytes | 1m | The minimum of system.diskio.write.bytes_delta for individual disks. |
| Disk | Disk Write Bytes [Delta Sum] | bytes | 1m | The sum of system.diskio.write.bytes_delta for individual disks. |
| Disk | Disk Write Bytes [Delta] | bytes | 1m | The delta value of system.diskio.write.bytes for individual disks. |
| Disk | Disk Write Bytes [Success] | bytes | 1m | The total number of bytes written successfully. On Linux, it is assumed that the sector size is 512 and the value is calculated by multiplying the number of sectors written by 512. |
| Disk | Disk Write Requests | cnt | 1m | The number of write requests for the disk device per second. |
| Disk | Disk Write Requests [Delta Avg] | cnt | 1m | The average of system.diskio.write.count_delta for individual disks. |
| Disk | Disk Write Requests [Delta Max] | cnt | 1m | The maximum of system.diskio.write.count_delta for individual disks. |
| Disk | Disk Write Requests [Delta Min] | cnt | 1m | The minimum of system.diskio.write.count_delta for individual disks. |
| Disk | Disk Write Requests [Delta Sum] | cnt | 1m | The sum of system.diskio.write.count_delta for individual disks. |
| Disk | Disk Write Requests [Success Delta] | cnt | 1m | The delta value of system.diskio.write.count for individual disks. |
| Disk | Disk Write Requests [Success] | cnt | 1m | The total number of successful write requests. |
| Disk | Disk Writes Bytes | bytes | 1m | The number of bytes written to the device per second. |
| FileSystem | Filesystem Hang Check | state | 1m | Filesystem (local/NFS) hang check (normal: 1, abnormal: 0). |
| FileSystem | Filesystem Nodes | cnt | 1m | The total number of file nodes in the file system. |
| FileSystem | Filesystem Nodes [Free] | cnt | 1m | The total number of available file nodes in the file system. |
| FileSystem | Filesystem Size [Available] | bytes | 1m | The available disk space (in bytes) that can be used by non-privileged users. |
| FileSystem | Filesystem Size [Free] | bytes | 1m | The available disk space (in bytes). |
| FileSystem | Filesystem Size [Total] | bytes | 1m | The total disk space (in bytes). |
| FileSystem | Filesystem Usage | % | 1m | The percentage of used disk space. |
| FileSystem | Filesystem Usage [Avg] | % | 1m | The average of filesystem.used.pct for individual file systems. |
| FileSystem | Filesystem Usage [Inode] | % | 1m | The inode usage rate. |
| FileSystem | Filesystem Usage [Max] | % | 1m | The maximum of filesystem.used.pct for individual file systems. |
| FileSystem | Filesystem Usage [Min] | % | 1m | The minimum of filesystem.used.pct for individual file systems. |
| FileSystem | Filesystem Usage [Total] | % | 1m | - |
| FileSystem | Filesystem Used | bytes | 1m | The used disk space (in bytes). |
| FileSystem | Filesystem Used [Inode] | bytes | 1m | The inode usage. |
| Memory | Memory Free | bytes | 1m | The total available memory (in bytes), excluding memory used by system cache and buffers (see system.memory.actual.free). |
| Memory | Memory Free [Actual] | bytes | 1m | The actual available memory (in bytes), which varies depending on the OS. On Linux, it is calculated using /proc/meminfo, and on OSX, it is the sum of available and inactive memory. On Windows, it is the same as system.memory.free. |
| Memory | Memory Free [Swap] | bytes | 1m | The available swap memory. |
| Memory | Memory Total | bytes | 1m | The total memory. |
| Memory | Memory Total [Swap] | bytes | 1m | The total swap memory. |
| Memory | Memory Usage | % | 1m | The percentage of used memory. |
| Memory | Memory Usage [Actual] | % | 1m | The percentage of actual used memory. |
| Memory | Memory Usage [Cache Swap] | % | 1m | The cache swap usage rate. |
| Memory | Memory Usage [Swap] | % | 1m | The percentage of used swap memory. |
| Memory | Memory Used | bytes | 1m | The used memory. |
| Memory | Memory Used [Actual] | bytes | 1m | The actual used memory (in bytes), which is the total memory minus the used memory. The available memory varies depending on the OS (see system.actual.free). |
| Memory | Memory Used [Swap] | bytes | 1m | The used swap memory. |
| Network | Collisions | cnt | 1m | Network collisions. |
| Network | Network In Bytes | bytes | 1m | The number of bytes received. |
| Network | Network In Bytes [Delta Avg] | bytes | 1m | The average of system.network.in.bytes_delta for individual networks. |
| Network | Network In Bytes [Delta Max] | bytes | 1m | The maximum of system.network.in.bytes_delta for individual networks. |
| Network | Network In Bytes [Delta Min] | bytes | 1m | The minimum of system.network.in.bytes_delta for individual networks. |
| Network | Network In Bytes [Delta Sum] | bytes | 1m | The sum of system.network.in.bytes_delta for individual networks. |
| Network | Network In Bytes [Delta] | bytes | 1m | The delta value of the number of bytes received. |
| Network | Network In Dropped | cnt | 1m | The number of packets dropped during reception. |
| Network | Network In Errors | cnt | 1m | The number of errors during reception. |
| Network | Network In Packets | cnt | 1m | The number of packets received. |
| Network | Network In Packets [Delta Avg] | cnt | 1m | The average of system.network.in.packets_delta for individual networks. |
| Network | Network In Packets [Delta Max] | cnt | 1m | The maximum of system.network.in.packets_delta for individual networks. |
| Network | Network In Packets [Delta Min] | cnt | 1m | The minimum of system.network.in.packets_delta for individual networks. |
| Network | Network In Packets [Delta Sum] | cnt | 1m | The sum of system.network.in.packets_delta for individual networks. |
| Network | Network In Packets [Delta] | cnt | 1m | The delta value of the number of packets received. |
| Network | Network Out Bytes | bytes | 1m | The number of bytes sent. |
| Network | Network Out Bytes [Delta Avg] | bytes | 1m | The average of system.network.out.bytes_delta for individual networks. |
| Network | Network Out Bytes [Delta Max] | bytes | 1m | The maximum of system.network.out.bytes_delta for individual networks. |
| Network | Network Out Bytes [Delta Min] | bytes | 1m | The minimum of system.network.out.bytes_delta for individual networks. |
| Network | Network Out Bytes [Delta Sum] | bytes | 1m | The sum of system.network.out.bytes_delta for individual networks. |
| Network | Network Out Bytes [Delta] | bytes | 1m | The delta value of the number of bytes sent. |
| Network | Network Out Dropped | cnt | 1m | The number of packets dropped during transmission. This value is not reported by the OS and is always 0 on Darwin and BSD. |
| Network | Network Out Errors | cnt | 1m | The number of errors during transmission. |
| Network | Network Out Packets | cnt | 1m | The number of packets sent. |
| Network | Network Out Packets [Delta Avg] | cnt | 1m | The average of system.network.out.packets_delta for individual networks. |
| Network | Network Out Packets [Delta Max] | cnt | 1m | The maximum of system.network.out.packets_delta for individual networks. |
| Network | Network Out Packets [Delta Min] | cnt | 1m | The minimum of system.network.out.packets_delta for individual networks. |
| Network | Network Out Packets [Delta Sum] | cnt | 1m | The sum of system.network.out.packets_delta for individual networks. |
| Network | Network Out Packets [Delta] | cnt | 1m | The delta value of the number of packets sent. |
| Network | Open Connections [TCP] | cnt | 1m | The number of open TCP connections. |
| Network | Open Connections [UDP] | cnt | 1m | The number of open UDP connections. |
| Network | Port Usage | % | 1m | The port usage rate. |
| Network | SYN Sent Sockets | cnt | 1m | The number of sockets in the SYN_SENT state (when connecting to a remote host). |
| Process | Kernel PID Max | cnt | 1m | The kernel.pid_max value. |
| Process | Kernel Thread Max | cnt | 1m | The kernel.threads-max value. |
| Process | Process CPU Usage | % | 1m | The percentage of CPU time consumed by the process since the last update. This value is similar to the %CPU value displayed by the top command on Unix systems. |
| Process | Process CPU Usage/Core | % | 1m | The percentage of CPU time used by the process since the last event, normalized by the number of cores (0-100%). |
| Process | Process Memory Usage | % | 1m | The percentage of main memory (RAM) used by the process. |
| Process | Process Memory Used | bytes | 1m | The resident set size, which is the amount of memory used by the process in RAM. On Windows, it is the current working set size. |
| Process | Process PID | PID | 1m | The process ID. |
| Process | Process PPID | PID | 1m | The parent process ID. |
| Process | Processes [Dead] | cnt | 1m | The number of dead processes. |
| Process | Processes [Idle] | cnt | 1m | The number of idle processes. |
| Process | Processes [Running] | cnt | 1m | The number of running processes. |
| Process | Processes [Sleeping] | cnt | 1m | The number of sleeping processes. |
| Process | Processes [Stopped] | cnt | 1m | The number of stopped processes. |
| Process | Processes [Total] | cnt | 1m | The total number of processes. |
| Process | Processes [Unknown] | cnt | 1m | The number of processes with unknown or unsearchable states. |
| Process | Processes [Zombie] | cnt | 1m | The number of zombie processes. |
| Process | Running Process Usage | % | 1m | The process usage rate. |
| Process | Running Processes | cnt | 1m | The number of running processes. |
| Process | Running Thread Usage | % | 1m | The thread usage rate. |
| Process | Running Threads | cnt | 1m | The total number of threads running in running processes. |
| System | Context Switches | cnt | 1m | The number of context switches per second. |
| System | Load/Core [1 min] | cnt | 1m | The load average over the last 1 minute, normalized by the number of cores. |
| System | Load/Core [15 min] | cnt | 1m | The load average over the last 15 minutes, normalized by the number of cores. |
| System | Load/Core [5 min] | cnt | 1m | The load average over the last 5 minutes, normalized by the number of cores. |
| System | Multipaths [Active] | cnt | 1m | The number of active paths for external storage connections. |
| System | Multipaths [Failed] | cnt | 1m | The number of failed paths for external storage connections. |
| System | Multipaths [Faulty] | cnt | 1m | The number of faulty paths for external storage connections. |
| System | NTP Offset | num | 1m | The measured offset (time difference between the NTP server and the local environment) of the last sample. |
| System | Run Queue Length | num | 1m | The length of the run queue. |
| System | Uptime | ms | 1m | The OS uptime (in milliseconds). |
| Windows | Context Switchies | cnt | 1m | The number of CPU context switches per second. |
| Windows | Disk Read Bytes [Sec] | cnt | 1m | The number of bytes read from the Windows logical disk per second. |
| Windows | Disk Read Time [Avg] | sec | 1m | The average time spent reading data (in seconds). |
| Windows | Disk Transfer Time [Avg] | sec | 1m | The average disk wait time. |
| Windows | Disk Usage | % | 1m | The disk usage rate. |
| Windows | Disk Write Bytes [Sec] | cnt | 1m | The number of bytes written to the Windows logical disk per second. |
| Windows | Disk Write Time [Avg] | sec | 1m | The average time spent writing data (in seconds). |
| Windows | Pagingfile Usage | % | 1m | The paging file usage rate. |
| Windows | Pool Used [Non Paged] | bytes | 1m | The Nonpaged Pool usage of kernel memory. |
| Windows | Pool Used [Paged] | bytes | 1m | The Paged Pool usage of kernel memory. |
| Windows | Process [Running] | cnt | 1m | The number of currently running processes. |
| Windows | Threads [Running] | cnt | 1m | The number of currently running threads. |
| Windows | Threads [Waiting] | cnt | 1m | The number of threads waiting for processor time. |
Storage type
File Storage
| Performance item group name | Performance item name | Collection unit | Collection cycle | Description |
|---|---|---|---|---|
| Volume | Instance State | state | 1m | File storage volume status |
| Volume | IOPS [Other] | iops | 1m | IOPS (other) |
| Volume | IOPS [Read] | iops | 1m | IOPS (read) |
| Volume | IOPS [Total] | iops | 1m | IOPS (total) |
| Volume | IOPS [Write] | iops | 1m | IOPS (write) |
| Volume | Latency Time [Other] | usec | 1m | Latency time (other) |
| Volume | Latency Time [Read] | usec | 1m | Latency time (read) |
| Volume | Latency Time [Total] | usec | 1m | Latency time (total) |
| Volume | Latency Time [write] | usec | 1m | Latency time (write) |
| Volume | Throughput [Other] | MB/s | 1m | Throughput (other) |
| Volume | Throughput [Read] | MB/s | 1m | Throughput (read) |
| Volume | Throughput [Total] | MB/s | 1m | Throughput (total) |
| Volume | Throughput [Write] | MB/s | 1m | Throughput (write) |
| Volume | Volume Total | bytes | 1m | Total bytes |
| Volume | Volume Usage | % | 1m | Usage rate |
| Volume | Volume Used | bytes | 1m | Used amount |
Object Storage
| Performance item group name | Performance item name | Collection unit | Collection cycle | Description |
|---|---|---|---|---|
| Request | Requests [Delete] | cnt | 1m | Number of HTTP DELETE requests executed on objects in the bucket |
| Request | Requests [Download Avg] | bytes | 1m | Average download usage per bucket |
| Request | Requests [Get] | cnt | 1m | Number of HTTP GET requests executed on objects in the bucket |
| Request | Requests [Head] | cnt | 1m | Number of HTTP HEAD requests executed on objects in the bucket |
| Request | Requests [List] | cnt | 1m | Number of LIST requests executed on objects in the bucket |
| Request | Requests [Post] | cnt | 1m | Number of HTTP POST requests executed on objects in the bucket |
| Request | Requests [Put] | cnt | 1m | Number of HTTP PUT requests executed on objects in the bucket |
| Request | Requests [Total] | cnt | 1m | Total number of HTTP requests executed on the bucket |
| Request | Requests [Upload Avg] | bytes | 1m | Average upload usage per bucket |
| Usage | Bucket Used | bytes | 1m | Amount of data stored in the bucket (in bytes) |
| Usage | Objects | cnt | 1m | Number of objects stored in the bucket |
Database type
PostgreSQL(DBaaS)
| Performance item group name | Performance item name | Collection unit | Collection cycle | Description |
|---|---|---|---|---|
| Activelock | Active Locks | cnt | 1m | Number of active locks |
| Activelock | Active Locks [Access Exclusive] | cnt | 1m | Number of access exclusive locks |
| Activelock | Active Locks [Access Share] | cnt | 1m | Number of access share locks |
| Activelock | Active Locks [Total] | cnt | 1m | Total number of active locks |
| Activelock | Exclusive Locks | cnt | 1m | Number of exclusive locks |
| Activelock | Row Exclusive Locks | cnt | 1m | Number of row exclusive locks |
| Activelock | Row Share Locks | cnt | 1m | Number of row share locks |
| Activelock | Share Locks | cnt | 1m | Number of share locks |
| Activelock | Share Row Exclusive Locks | cnt | 1m | Number of share row exclusive locks |
| Activelock | Share Update Exclusive Locks | cnt | 1m | Number of share update exclusive locks |
| ActiveSession | Active Sessions | cnt | 1m | Number of active sessions |
| ActiveSession | Active Sessions [Total] | cnt | 1m | Total number of active sessions |
| ActiveSession | Idle In Transaction Sessions | cnt | 1m | Number of idle in transaction sessions |
| ActiveSession | Idle In Transaction Sessions [Total] | cnt | 1m | Total number of idle in transaction sessions |
| ActiveSession | Idle Sessions | cnt | 1m | Number of idle sessions |
| ActiveSession | Idle Sessions [Total] | cnt | 1m | Total number of idle sessions |
| ActiveSession | Waiting Sessions | cnt | 1m | Number of waiting sessions |
| ActiveSession | Waiting Sessions [Total] | cnt | 1m | Total number of waiting sessions |
| Connection | Connection Usage | % | 1m | DB connection usage rate |
| Connection | Connection Usage [Total] | % | 1m | Total DB connection usage rate |
| DB Age | DB Age Max | age | 1m | Database age (frozen XID) value |
| Lock | Wait Locks | cnt | 1m | Number of sessions waiting for locks (per DB) |
| Lock | Wait Locks [Long Total] | cnt | 1m | Number of sessions waiting for locks for more than 300 seconds |
| Lock | Wait Locks [Long] | cnt | 1m | Number of sessions waiting for locks for more than 300 seconds |
| Lock | Wait Locks [Total] | cnt | 1m | Total number of sessions waiting for locks |
| Long Transaction | Transaction Time Max [Long] | sec | 1m | Longest transaction time (in seconds) |
| Long Transaction | Transaction Time Max Total [Long] | sec | 1m | Longest transaction time (in seconds) |
| Replica | Apply Lag Time | sec | 1m | Apply lag time |
| Replica | Check No Replication | cnt | 1m | Check no replication value |
| Replica | Check Replication | state | 1m | Check replication state value |
| Slowquery | Slowqueries | cnt | 1m | Number of slow queries (more than 5 minutes) |
| State | Instance State [PID] | PID | 1m | Postgres process PID |
| Tablespace | Tablespace Used | bytes | 1m | Tablespace usage |
| Tablespace | Tablespace Used [Total] | bytes | 1m | Total tablespace usage |
| Tablespace | Tablespace Used Bytes [MB] | bytes | 1m | Filesystem directory usage (in MB) |
| Tablespace | Tablespaces [Total] | cnt | 1m | Total number of tablespaces |
MariaDB(DBaaS)
| Performance item group name | Performance item name | Collection unit | Collection cycle | Description |
|---|---|---|---|---|
| Activelock | Active Locks | cnt | 1m | Number of active locks |
| Activesssion | Active Sessions | cnt | 1m | Number of connected threads |
| Activesssion | Connection Usage [Total] | % | 1m | DB connection usage rate |
| Activesssion | Connections | cnt | 1m | Number of connections |
| Activesssion | Connections [MAX] | cnt | 1m | Maximum number of connected threads |
| Datafile | Binary Log Used [MB] | bytes | 1m | Binary log usage (in MB) |
| Datafile | Data Directory Used [MB] | bytes | 1m | Datadir usage (in MB) |
| Datafile | Open Files | cnt | 1m | Number of open files |
| Datafile | Open Files [MAX] | cnt | 1m | Maximum number of open files |
| Datafile | Open Files Usage | % | 1m | Open file usage rate |
| Datafile | Relay Log Used [MB] | bytes | 1m | Relay log usage (in MB) |
| State | Instance State [PID] | PID | 1m | Mariadbd process PID (or mysqld process PID for versions prior to 10.5.2) |
| State | Safe PID | PID | 1m | Mariadbd_safe process PID (or mysqld_safe process PID for versions prior to 10.5.2) |
| State | Slave Behind Master seconds | sec | 1m | Time difference between master and slave (in seconds) |
| Tablespace | Tablespace Used | bytes | 1m | Tablespace usage |
| Tablespace | Tablespace Used [Total] | bytes | 1m | Total tablespace usage |
| Transaction | Running Threads | cnt | 1m | Number of running threads |
| Transaction | Slowqueries | cnt | 1m | Number of slow queries (more than 10 seconds) |
| Transaction | Slowqueries [Total] | cnt | 1m | Total number of slow queries |
| Transaction | Transaction Time [Long] | sec | 1m | Longest transaction time (in seconds) |
| Transaction | Wait Locks | cnt | 1m | Number of sessions waiting for locks for more than 60 seconds |
MySQL(DBaaS)
| Performance item group name | Performance item name | Collection unit | Collection cycle | Description |
|---|---|---|---|---|
| Activelock | Active Locks | cnt | 1m | Number of active locks |
| Activesssion | Active Sessions | cnt | 1m | Number of connected threads |
| Activesssion | Connection Usage [Total] | % | 1m | DB connection usage rate |
| Activesssion | Connections | cnt | 1m | Number of connections |
| Activesssion | Connections [MAX] | cnt | 1m | Maximum number of connected threads |
| Datafile | Binary Log Used [MB] | bytes | 1m | Binary log usage (in MB) |
| Datafile | Data Directory Used [MB] | bytes | 1m | Datadir usage (in MB) |
| Datafile | Open Files | cnt | 1m | Number of open files |
| Datafile | Open Files [MAX] | cnt | 1m | Maximum number of open files |
| Datafile | Open Files Usage | % | 1m | Open file usage rate |
| Datafile | Relay Log Used [MB] | bytes | 1m | Relay log usage (in MB) |
| State | Instance State [PID] | PID | 1m | Mysqld process PID |
| State | Safe PID | PID | 1m | Safe program PID |
| State | Slave Behind Master seconds | sec | 1m | Time difference between master and slave (in seconds) |
| Tablespace | Tablespace Used | bytes | 1m | Tablespace usage |
| Tablespace | Tablespace Used [Total] | bytes | 1m | Total tablespace usage |
| Transaction | Running Threads | cnt | 1m | Number of running threads |
| Transaction | Slowqueries | cnt | 1m | Number of slow queries (more than 10 seconds) |
| Transaction | Slowqueries [Total] | cnt | 1m | Total number of slow queries |
| Transaction | Transaction Time [Long] | sec | 1m | Longest transaction time (in seconds) |
| Transaction | Wait Locks | cnt | 1m | Number of sessions waiting for locks for more than 60 seconds |
CacheStore(DBaaS)
| Performance item group name | Performance item name | Collection unit | Collection cycle | Description |
|---|---|---|---|---|
| CacheStore | Active Defragmentation Keys [Hits] | cnt | 1m | Number of keys defragmented |
| CacheStore | Active Defragmentation Keys [Miss] | cnt | 1m | Number of keys skipped during defragmentation |
| CacheStore | Active Defragmentationd [Hits] | cnt | 1m | Number of values reassigned during defragmentation |
| CacheStore | Active Defragmentations [Miss] | cnt | 1m | Number of defragmentation processes started and stopped |
| CacheStore | Allocated Bytes [OS] | bytes | 1m | Bytes allocated by CacheStore and recognized by the operating system (resident set size) |
| CacheStore | Allocated Bytes [Redis] | bytes | 1m | Total bytes allocated by CacheStore |
| CacheStore | AOF Buffer Size | bytes | 1m | AOF buffer size |
| CacheStore | AOF File Size [Current] | bytes | 1m | Current AOF file size |
| CacheStore | AOF File Size [Lastest Startup] | bytes | 1m | AOF file size at the last startup or rewrite |
| CacheStore | AOF Rewrite Buffer Size | bytes | 1m | AOF rewrite buffer size |
| CacheStore | AOF Rewrite Current Time | sec | 1m | Time spent on the current AOF rewrite process |
| CacheStore | AOF Rewrite Last Time | sec | 1m | Time spent on the last AOF rewrite process |
| CacheStore | Calls | cnt | 1m | Number of commands executed (not rejected) |
| CacheStore | Calls [Failed] | cnt | 1m | Number of failed commands (CacheStore 6.2-rc2) |
| CacheStore | Calls [Rejected] | cnt | 1m | Number of rejected commands (CacheStore 6.2-rc2) |
| CacheStore | Changes [Last Saved] | cnt | 1m | Number of changes since the last dump |
| CacheStore | Client Output Buffer [MAX] | cnt | 1m | Longest output list among current client connections |
| CacheStore | Client Input Buffer [MAX] | cnt | 1m | Largest input buffer among current client connections (CacheStore 5.0) |
| CacheStore | Clients [Sentinel] | cnt | 1m | Number of client connections (sentinel) |
| CacheStore | Connected Slaves | cnt | 1m | Number of connected slaves |
| CacheStore | Connections [Blocked] | cnt | 1m | Number of clients waiting for blocking calls (BLPOP, BRPOP, BRPOPLPUSH) |
| CacheStore | Connections [Current] | cnt | 1m | Number of client connections (excluding slave connections) |
| CacheStore | Copy On Write Allocated Size [AOF] | bytes | 1m | COW allocation size (in bytes) during the last RDB save operation |
| CacheStore | Copy On Write Allocated Size [RDB] | bytes | 1m | COW allocation size (in bytes) during the last RDB save operation |
| CacheStore | CPU Time [Average] | cnt | 1m | Average CPU usage per command execution |
| CacheStore | CPU Time [Total] | usec | 1m | Total CPU time used by these commands |
| CacheStore | CPU Usage [System Process] | % | 1m | System CPU usage by background processes |
| CacheStore | CPU Usage [System] | % | 1m | System CPU usage by the CacheStore server |
| CacheStore | CPU Usage [User Process] | % | 1m | User CPU usage by background processes |
| CacheStore | CPU Usage [User] | % | 1m | User CPU usage by the CacheStore server |
| CacheStore | Dataset Used | bytes | 1m | Dataset size (in bytes) |
| CacheStore | Disk Used | bytes | 1m | Datadir usage |
| CacheStore | Evicted Keys | cnt | 1m | Number of evicted keys due to maxmemory limit |
| CacheStore | Fsyncs [Delayed] | cnt | 1m | Delayed fsync counter |
| CacheStore | Fsyncs [Pending] | cnt | 1m | Number of fsync operations pending in the background I/O queue (in bytes) |
| CacheStore | Full Resyncs | cnt | 1m | Number of full resynchronizations with slaves |
| CacheStore | Keys [Expired] | cnt | 1m | Total number of key expiration events |
| CacheStore | Keys [Keyspace] | cnt | 1m | Number of keys in the keyspace |
| CacheStore | Lastest Fork Duration Time | usec | 1m | Time taken by the last fork operation (in microseconds) |
| CacheStore | Lookup Keys [Hit] | cnt | 1m | Number of successful key lookups in the main dictionary |
| CacheStore | Lookup Keys [Miss] | cnt | 1m | Number of failed key lookups in the main dictionary |
| CacheStore | Lua Engine Memory Used | bytes | 1m | Memory used by the Lua engine |
| CacheStore | Master Last Interaction Time Ago | sec | 1m | Time elapsed since the last interaction with the master (in seconds) |
| CacheStore | Master Last Interaction Time Ago [Sync] | sec | 1m | Time elapsed since the last interaction with the master (in seconds) |
| CacheStore | Master Offset | pid | 1m | Current replication offset of the server |
| CacheStore | Master Second Offset | pid | 1m | Offset of the replication ID that will be accepted |
| CacheStore | Master Sync Left Bytes | bytes | 1m | Number of bytes remaining to be synchronized |
| CacheStore | Memory Fragmentation Rate | % | 1m | Ratio of used_memory_rss to used_memory |
| CacheStore | Memory Fragmentation Rate [Allocator] | % | 1m | Fragmentation ratio |
| CacheStore | Memory Fragmentation Used | bytes | 1m | Difference between used_memory_rss and used_memory (in bytes) |
| CacheStore | Memory Fragmentation Used [Allocator] | bytes | 1m | Resident bytes |
| CacheStore | Memory Max Value | bytes | 1m | Memory limit |
| CacheStore | Memory Resident [Allocator] | bytes | 1m | Resident memory |
| CacheStore | Memory RSS Rate [Allocator] | % | 1m | Resident ratio |
| CacheStore | Memory Used [Active] | bytes | 1m | Active memory |
| CacheStore | Memory Used [Allocated] | bytes | 1m | Allocated memory |
| CacheStore | Memory Used [Resident] | bytes | 1m | Resident bytes |
| CacheStore | Network In Bytes [Total] | bytes | 1m | Total network input (in bytes) |
| CacheStore | Network Out Bytes [Total] | bytes | 1m | Total network output (in bytes) |
| CacheStore | Network Read Rate | cnt | 1m | Network read rate (in KB/sec) |
| CacheStore | Network Write Rate | cnt | 1m | Network write rate (in KB/sec) |
| CacheStore | Partial Resync Requests [Accepted] | cnt | 1m | Number of accepted partial resynchronization requests |
| CacheStore | Partial Resync Requests [Denied] | cnt | 1m | Number of denied partial resynchronization requests |
| CacheStore | Peak Memory Consumed | bytes | 1m | Maximum memory consumed by CacheStore |
| CacheStore | Processed Commands | cnt | 1m | Number of commands processed per second |
| CacheStore | Processed Commands [Total] | cnt | 1m | Total number of commands processed |
| CacheStore | Pub/Sub Channels | cnt | 1m | Global number of pub/sub channels with client subscriptions |
| CacheStore | Pub/Sub Patterns | cnt | 1m | Global number of pub/sub patterns with client subscriptions |
| CacheStore | RDB Saved Duration Time [Current] | sec | 1m | Time taken by the current RDB save operation (in seconds) |
| CacheStore | RDB Saved Duration Time [Last] | sec | 1m | Time taken by the last RDB save operation (in seconds) |
| CacheStore | Received Connections [Total] | cnt | 1m | Total number of connections received |
| CacheStore | Rejected Connections [Total] | cnt | 1m | Total number of connections rejected |
| CacheStore | Replication Backlog Actove Count | cnt | 1m | Replication backlog active flag |
| CacheStore | Replication Backlog Master Offset | cnt | 1m | Master offset of the replication backlog buffer |
| CacheStore | Replication Backlog Size | bytes | 1m | Size of the replication backlog buffer (in bytes) |
| CacheStore | Replication Backlog Size [Total] | bytes | 1m | Total size of the replication backlog buffer (in bytes) |
| CacheStore | Slave Priority | cnt | 1m | Priority of the instance as a failover target |
| CacheStore | Slave Replication Offset | pid | 1m | Replication offset of the slave instance |
| CacheStore | Slow Operations | cnt | 1m | Number of slow operations |
| CacheStore | Sockets [MIGRATE] | cnt | 1m | Number of sockets opened for migration |
| CacheStore | Tracked Keys [Expiry] | cnt | 1m | Number of keys being tracked for expiry (only for writable slaves) |
| State | Instance State [PID] | PID | 1m | PID of the redis-server process |
| State | Sentinel State [PID] | PID | 1m | PID of the sentinel process |
EPAS
| Performance Item Group Name | Performance Item Name | Collection Unit | Collection Cycle | Description |
|---|---|---|---|---|
| Activelock | Access Exclusive Locks | cnt | 1m | Number of access exclusive locks |
| Activelock | Access Share Locks | cnt | 1m | Number of access share locks |
| Activelock | Active Locks | cnt | 1m | Number of active locks |
| Activelock | Active Locks [Total] | cnt | 1m | Total number of active locks |
| Activelock | Exclusive Locks | cnt | 1m | Number of exclusive locks |
| Activelock | Row Exclusive Locks | cnt | 1m | Number of row exclusive locks |
| Activelock | Row Share Locks | cnt | 1m | Number of row share locks |
| Activelock | Share Locks | cnt | 1m | Number of share locks |
| Activelock | Share Row Exclusive Locks | cnt | 1m | Number of share row exclusive locks |
| Activelock | Share Update Exclusive Locks | cnt | 1m | Number of share update exclusive locks |
| Activesession | Active Sessions | cnt | 1m | Number of active sessions |
| Activesession | Active Sessions [Total] | cnt | 1m | Total number of active sessions |
| Activesession | Idel In Transaction Sessions | cnt | 1m | Number of idle in transaction sessions |
| Activesession | Idle In Transaction Sessions [Total] | cnt | 1m | Total number of idle in transaction sessions |
| Activesession | Idle Sessions | cnt | 1m | Number of idle sessions |
| Activesession | Idle Sessions [Total] | cnt | 1m | Total number of idle sessions |
| Activesession | Waiting Sessions | cnt | 1m | Number of waiting sessions |
| Activesession | Waiting Sessions [Total] | cnt | 1m | Total number of waiting sessions |
| Connection | Connection Usage | % | 1m | DB connection usage rate (%) |
| Connection | Connection Usage [Total] | % | 1m | Total DB connection usage rate (%) |
| Connection | Connection Usage Per DB | % | 1m | DB connection usage rate per DB (%) |
| DB Age | DB Age Max | age | 1m | Database age (frozen XID) value |
| Lock | Wait Locks | cnt | 1m | Number of sessions waiting for locks |
| Lock | Wait Locks [Long Total] | cnt | 1m | Total number of sessions waiting for locks for a long time |
| Lock | Wait Locks [Long] | cnt | 1m | Number of sessions waiting for locks for a long time |
| Lock | Wait Locks [Total] | cnt | 1m | Total number of sessions waiting for locks |
| Lock | Wait Locks Per DB [Total] | cnt | 1m | Total number of sessions waiting for locks per DB |
| Long Transaction | Transaction Time Max [Long] | sec | 1m | Maximum transaction time (in minutes) |
| Long Transaction | Transaction Time Max Total [Long] | sec | 1m | Maximum transaction time (in minutes) |
| Replica | Apply Lag Time | sec | 1m | Apply lag time |
| Replica | Check No Replication | cnt | 1m | Check no replication value |
| Replica | Check Replication | state | 1m | Check replication state value |
| Slowquery | Slowqueries | cnt | 1m | Number of slow queries |
| State | Instance state [PID] | PID | 1m | PID of the edb-postgres process |
| Tablespace | Tablespace Used Bytes [MB] | bytes | 1m | Filesystem directory usage (in MB) |
| Tablespace | Tablespace [Total] | cnt | 1m | Total number of tablespaces |
| Tablespace | Tablespace Used | bytes | 1m | Used tablespace size |
| Tablespace | Tablespace Used [Total] | bytes | 1m | Total used tablespace size |
Microsoft SQL Server
| Performance Item Group Name | Performance Item Name | Collection Unit | Collection Cycle | Description |
|---|---|---|---|---|
| Activelock | Active Locks | cnt | 1m | Number of active locks |
| Activesssion | Active Sessions | cnt | 1m | Number of active sessions |
| Activetransaction | Active Transactions [Total] | cnt | 1m | Total number of active transactions |
| Connection | Connected Users | cnt | 1m | Number of users connected to the system |
| Datafile | Datavolume Size [Free] | bytes | 1m | Available space |
| Datafile | DBFiles [Not Online] | cnt | 1m | Number of data files that are not online |
| Datafile | Tablespace Used | bytes | 1m | Used data volume size |
| Lock | Lock Processes [Blocked] | cnt | 1m | Number of SQL processes blocked by other processes |
| Lock | Lock Waits [Per Second] | cnt | 1m | Number of lock waits per second |
| Slowquery | Blocking Session ID | ID | 1m | ID of the session blocking the query |
| Slowquery | Slowqueries | cnt | 1m | Number of slow queries |
| Slowquery | Slowquery CPU Time | ms | 1m | CPU time taken by slow queries |
| Slowquery | Slowquery Execute Context ID | ID | 1m | ID of the execution context of slow queries |
| Slowquery | Slowquery Memory Usage | bytes | 1m | Memory usage of slow queries |
| Slowquery | Slowquery Session ID | ID | 1m | ID of the session executing slow queries |
| Slowquery | Slowquery Wait Duration Time | ms | 1m | Wait duration time of slow queries |
| State | Instance State [Cluster] | state | 1m | State of the MSSQL cluster |
| State | Instance State [PID] | PID | 1m | PID of the sqlservr.exe process |
| State | Page IO Latch Wait Time | ms | 1m | Average wait time for page IO latches |
| Transaction | Transaction Time [MAX] | cnt | 1m | Maximum transaction time |
Data Analytics 유형
Event Streams
| Performance Item Group Name | Performance Item Name | Collection Unit | Collection Cycle | Description |
|---|---|---|---|---|
| Broker | Connections [Zookeeper Client] | cnt | 1m | Number of ZooKeeper connections |
| Broker | Failed [Client Fetch Request] | cnt | 1m | Number of failed client fetch requests |
| Broker | Failed [Produce Request] | cnt | 1m | Number of failed produce requests |
| Broker | Incomming Messages | cnt | 1m | Number of incoming messages |
| Broker | Leader Elections | cnt | 1m | Number of leader elections |
| Broker | Leader Elections [Unclean] | cnt | 1m | Number of unclean leader elections |
| Broker | Log Flushes | cnt | 1m | Number of log flushes |
| Broker | Network In Bytes | bytes | 1m | Total network input (in bytes) |
| Broker | Network Out Bytes | bytes | 1m | Total network output (in bytes) |
| Broker | Rejected Bytes | bytes | 1m | Total rejected bytes |
| Broker | Request Queue Length | cnt | 1m | Request queue length |
| Broker | Zookeeper Sessions [Closed] | cnt | 1m | Number of closed ZooKeeper sessions |
| Broker | Zookeeper Sessions [Expired] | cnt | 1m | Number of expired ZooKeeper sessions |
| Broker | Zookeeper Sessions [Readonly] | cnt | 1m | Number of read-only ZooKeeper sessions |
| Broker | Incomming Messages Rate [Topic] | cnt | 1m | Incoming message rate per topic |
| Broker | Incomming Byte Rate [Second] | bytes | 1m | Incoming byte rate per second |
| Broker | Outgoing Byte Rate [Second] | bytes | 1m | Outgoing byte rate per second |
| Broker | Rejected Byte Rate [Second] | bytes | 1m | Rejected byte rate per second |
| Disk | Disk Used | bytes | 1m | Datadir usage |
| State | AKHQ State [PID] | PID | 1m | PID of the akhq process |
| State | Instance State [PID] | PID | 1m | PID of the kafka process |
| State | Zookeeper State [PID] | PID | 1m | PID of the zookeeper process |
Search Engine
| Performance Item Group Name | Performance Item Name | Collection Unit | Collection Cycle | Description |
|---|---|---|---|---|
| Cluster | Shards | cnt | 1m | Number of shards in the cluster |
| Cluster | Shards [Primary] | cnt | 1m | Number of primary shards in the cluster |
| Cluster | Index [Total] | cnt | 1m | Total number of indices in the cluster |
| Cluster | License Expiry Date [ms] | ms | 1m | License expiry date (in milliseconds) |
| Cluster | License Status | state | 1m | License status |
| Cluster | License Type | type | 1m | License type |
| FileSystem | Disk Usage | bytes | 1m | Datadir usage |
| Node | Documents [Deleted] | cnt | 1m | Total number of deleted documents |
| Node | Documents [Existing] | cnt | 1m | Total number of existing documents |
| Node | Filesystem Bytes [Available] | bytes | 1m | Available filesystem bytes |
| Node | Filesystem Bytes [Free] | bytes | 1m | Free filesystem bytes |
| Node | Filesystem Bytes [Total] | bytes | 1m | Total filesystem bytes |
| Node | JVM Heap Used [Init] | bytes | 1m | Initial JVM heap usage (in bytes) |
| Node | JVM Heap Used [MAX] | bytes | 1m | Maximum JVM heap usage (in bytes) |
| Node | JVM Non Heap Used [Init] | bytes | 1m | Initial JVM non-heap usage (in bytes) |
| Node | JVM Non Heap Used [MAX] | bytes | 1m | Maximum JVM non-heap usage (in bytes) |
| Node | Segments | cnt | 1m | Total number of segments |
| Node | Segments Bytes | bytes | 1m | Total size of segments (in bytes) |
| Node | Store Bytes | bytes | 1m | Total size of the store (in bytes) |
| State | Instance state [PID] | PID | 1m | PID of the Elasticsearch process |
| Task | Queue Time | ms | 1m | Queue time |
| Kibana | Kibana state [PID] | PID | 1m | PID of the Kibana process |
| Kibana | Kibana Connections | cnt | 1m | Number of connections |
| Kibana | Kibana Memory Heap Allocated [Limit] | bytes | 1m | Maximum allocated heap size (in bytes) |
| Kibana | Kibana Memory Heap Allocated [Total] | bytes | 1m | Total allocated heap size (in bytes) |
| Kibana | Kibana Memory Heap Used | bytes | 1m | Used heap size (in bytes) |
| Kibana | Kibana Process Uptime | ms | 1m | Process uptime |
| Kibana | Kibana Requests [Disconnected] | cnt | 1m | Number of disconnected requests |
| Kibana | Kibana Requests [Total] | cnt | 1m | Total number of requests |
| Kibana | Kibana Response Time [Avg] | ms | 1m | Average response time |
| Kibana | Kibana Response Time [MAX] | ms | 1m | Maximum response time |
Container 유형
Kubernetes Engine
| Performance Item Group Name | Performance Item Name | Collection Unit | Collection Cycle | Description |
|---|---|---|---|---|
| Cluster | Cluster Namespaces [Active] | cnt | 5m | Number of active namespaces |
| Cluster | Cluster Namespaces [Total] | cnt | 5m | Total number of namespaces |
| Cluster | Cluster Nodes [Ready] | cnt | 5m | Number of ready nodes |
| Cluster | Cluster Nodes [Total] | cnt | 5m | Total number of nodes |
| Cluster | Cluster Pods [Failed] | cnt | 5m | Number of failed pods |
| Cluster | Cluster Pods [Pending] | cnt | 5m | Number of pending pods |
| Cluster | Cluster Pods [Running] | cnt | 5m | Number of running pods |
| Cluster | Cluster Pods [Succeeded] | cnt | 5m | Number of succeeded pods |
| Cluster | Cluster Pods [Unknown] | cnt | 5m | Number of unknown pods |
| Cluster | Instance State | state | 5m | Cluster state |
| Namespace | Namespace Pods [Failed] | cnt | 5m | Number of failed pods in the namespace |
| Namespace | Namespace Pods [Pending] | cnt | 5m | Number of pending pods in the namespace |
| Namespace | Namespace Pods [Running] | cnt | 5m | Number of running pods in the namespace |
| Namespace | Namespace Pods [Succeeded] | cnt | 5m | Number of succeeded pods in the namespace |
| Namespace | Namespace Pods [Unknown] | cnt | 5m | Number of unknown pods in the namespace |
| Namespace | Namespace GPU Clock Frequency | MHz | 5m | GPU clock frequency |
| Namespace | Namespace GPU Memory Usage | % | 5m | GPU memory usage |
| Node | Node CPU Size [Allocatable] | cnt | 5m | Allocatable CPU size |
| Node | Node CPU Size [Capacity] | cnt | 5m | CPU capacity |
| Node | Node CPU Usage | % | 5m | CPU usage |
| Node | Node CPU Usage [Request] | % | 5m | CPU request ratio |
| Node | Node CPU Used | state | 5m | CPU utilization |
| Node | Node Filesystem Usage | % | 5m | Filesystem usage |
| Node | Node Memory Size [Allocatable] | bytes | 5m | Allocatable memory size |
| Node | Node Memory Size [Capacity] | bytes | 5m | Memory capacity |
| Node | Node Memory Usage | % | 5m | Memory usage |
| Node | Node Memory Usage [Request] | % | 5m | Memory request ratio |
| Node | Node Memory Workingset | bytes | 5m | Node memory working set |
| Node | Node Network In Bytes | bytes | 5m | Node network RX bytes |
| Node | Node Network Out Bytes | bytes | 5m | Node network TX bytes |
| Node | Node Network Total Bytes | bytes | 5m | Node network total bytes |
| Node | Node Pods [Failed] | cnt | 5m | Number of failed pods in the node |
| Node | Node Pods [Pending] | cnt | 5m | Number of pending pods in the node |
| Node | Node Pods [Running] | cnt | 5m | Number of running pods in the node |
| Node | Node Pods [Succeeded] | cnt | 5m | Number of succeeded pods in the node |
| Node | Node Pods [Unknown] | cnt | 5m | Number of unknown pods in the node |
| Pod | Pod CPU Usage [Limit] | % | 5m | Pod CPU usage limit ratio |
| Pod | Pod CPU Usage [Request] | % | 5m | Pod CPU request ratio |
| Pod | Pod CPU Usage | mc | 5m | Pod CPU usage |
| Pod | Pod Memory Usage [Limit] | % | 5m | Pod memory usage limit ratio |
| Pod | Pod Memory Usage [Request] | % | 5m | Pod memory request ratio |
| Pod | Pod Memory Usage | bytes | 5m | Pod memory usage |
| Pod | Pod Network In Bytes | bytes | 5m | Pod network RX bytes |
| Pod | Pod Network Out Bytes | bytes | 5m | Pod network TX bytes |
| Pod | Pod Network Total Bytes | bytes | 5m | Pod network total bytes |
| Pod | Pod Restart Containers | cnt | 5m | Number of container restarts in the pod |
| Workload | Workload Pods [Running] | cnt | 5m | - |
Container Registry
| Performance Item Group Name | Performance Item Name | Collection Unit | Collection Cycle | Description |
|---|---|---|---|---|
| Container Registry | Image Pulls [Denied] | cnt | 1m | Number of denied image tag (digest) pulls |
| Container Registry | Image Pushs [Allowed] | cnt | 1m | Number of allowed image tag (digest) pushes |
| Container Registry | Image Pushs [Denied] | cnt | 1m | Number of denied image tag (digest) pushes |
| Container Registry | Image Scans [Allowed] | cnt | 1m | Number of allowed image tag (digest) scans |
| Container Registry | Image Scans [Denied] | cnt | 1m | Number of denied image tag (digest) scans |
| Container Registry | Image Tags [Deleted] | cnt | 1m | Number of deleted image tags (digests) |
| Container Registry | Images [Created] | cnt | 1m | Number of created images |
| Container Registry | Images [Deleted] | cnt | 1m | Number of deleted images |
| Container Registry | Logins [Allowed] | cnt | 1m | Number of allowed registry logins |
| Container Registry | Logins [Denied] | cnt | 1m | Number of denied registry logins |
| Container Registry | Repositories [Created] | cnt | 1m | Number of created repositories |
| Container Registry | Repositories [Deleted] | cnt | 1m | Number of deleted repositories |
| State | Instance State | state | 1m | Status check |
Networking Type
Internet Gateway
| Performance Item Group Name | Performance Item Name | Collection Unit | Collection Cycle | Description |
|---|---|---|---|---|
| Internet Gateway | Network In Total Bytes [Internet Delta] | bytes | 5m | Cumulative traffic from Internet Gateway to VPC over 5 minutes (Internet) ※ Average traffic bps conversion formula: cumulative traffic (bytes) / 300 (seconds) * 8 (bits) |
| Internet Gateway | Network In Total Bytes [Internet] | bytes | 5m | RX bytes total |
| Internet Gateway | Network Out Total Bytes [Internet Delta] | bytes | 5m | Cumulative traffic from VPC to Internet Gateway over 5 minutes (Internet) ※ Average traffic bps conversion formula: cumulative traffic (bytes) / 300 (seconds) * 8 (bits) |
| Internet Gateway | Network Out Total Bytes [Internet] | bytes | 5m | TX bytes total |
Load Balancer (OLD)
| Performance Item Group Name | Performance Item Name | Collection Unit | Collection Cycle | Description |
|---|---|---|---|---|
| Load Balancer | Current Connection | cnt | 5m | Current number of connections |
| Load Balancer | Total Connection | cnt | 5m | Total number of connections |
| Load Balancer | Total Connection [Delta] | cnt | 5m | Total number of connections (delta value) |
| Load Balancer | Network In Bytes | bytes | 5m | In bytes |
| Load Balancer | Network In Bytes [Delta] | bytes | 5m | Cumulative traffic from client to Load Balancer over 5 minutes ※ Average traffic bps conversion formula: cumulative traffic (bytes) / 300 (seconds) * 8 (bits) |
| Load Balancer | Network Out Bytes | bytes | 5m | Out bytes |
| Load Balancer | Network Out Bytes [Delta] | bytes | 5m | Cumulative traffic from Load Balancer to client over 5 minutes ※ Average traffic bps conversion formula: cumulative traffic (bytes) / 300 (seconds) * 8 (bits) |
| Load Balancer | Instance State | state | 5m | Load Balancer status |
Load Balancer Listener (OLD)
| Performance Item Group Name | Performance Item Name | Collection Unit | Collection Cycle | Description |
|---|---|---|---|---|
| Listener | Connections [Current] | cnt | 5m | Current number of connections |
| Listener | Connections [Total Delta] | cnt | 5m | Total number of connections (delta value) |
| Listener | Connections [Total] | cnt | 5m | Total number of connections |
| Listener | Instance State | state | 5m | LB Listener status |
| Listener | Network In Bytes | bytes | 5m | In bytes |
| Listener | Network In Bytes [Delta] | bytes | 5m | Cumulative traffic from client to Load Balancer over 5 minutes ※ Average traffic bps conversion formula: cumulative traffic (bytes) / 300 (seconds) * 8 (bits) |
| Listener | Network Out Bytes | bytes | 5m | Out bytes |
| Listener | Network Out Bytes [Delta] | bytes | 5m | Cumulative traffic from Load Balancer to client over 5 minutes ※ Average traffic bps conversion formula: cumulative traffic (bytes) / 300 (seconds) * 8 (bits) |
Direct Connect
| Performance Item Group Name | Performance Item Name | Collection Unit | Collection Cycle | Description |
|---|---|---|---|---|
| Direct Connect | Network In Bytes | bytes | 5m | Cumulative traffic from Direct Connect to VPC |
| Direct Connect | Network In Bytes [Delta] | bytes | 5m | Cumulative traffic from Direct Connect to VPC over 5 minutes ※ Average traffic bps conversion formula: cumulative traffic (bytes) / 300 (seconds) * 8 (bits) |
| Direct Connect | Network Out Bytes | bytes | 5m | Cumulative traffic from VPC to Direct Connect |
| Direct Connect | Network Out Bytes [Delta] | bytes | 5m | Cumulative traffic from VPC to Direct Connect over 5 minutes ※ Average traffic bps conversion formula: cumulative traffic (bytes) / 300 (seconds) * 8 (bits) |
Load Balancer
| Performance Item Group Name | Performance Item Name | Collection Unit | Collection Cycle | Description |
|---|---|---|---|---|
| State | Instance State | state | 5m | LB status |
| Load Balancer | Current Connection | cnt | 5m | Current number of connections |
| Load Balancer | Total L4 Connection | cnt | 5m | Total number of L4 connections |
| Load Balancer | Total L7 Connection | cnt | 5m | Total number of L7 connections |
| Load Balancer | Total TCP Connection | cnt | 5m | Total number of TCP connections |
| Load Balancer | Total Connection | cnt | 5m | Total number of connections |
| Load Balancer | Bytes processed in forward direction | bytes | 5m | Forward network bytes |
| Load Balancer | Packets processed in forward direction | cnt | 5m | Forward network packets |
| Load Balancer | Bytes processed in reverse direction | bytes | 5m | Reverse network bytes |
| Load Balancer | Packets processed in reverse direction | cnt | 5m | Reverse network packets |
| Load Balancer | Total failure actions | cnt | 5m | Total number of failure actions |
| Load Balancer | Current Request | cnt | 5m | Current number of requests |
| Load Balancer | Current response | cnt | 5m | Current number of responses |
| Load Balancer | Total Request | cnt | 5m | Total number of requests |
| Load Balancer | Total Request Success | cnt | 5m | Total number of successful requests |
| Load Balancer | Peak Connection | cnt | 5m | Peak number of connections |
| Load Balancer | Current Connection Rate | % | 5m | Current SSL connection rate |
| Load Balancer | Last response time | ms | 5m | Last response time |
| Load Balancer | Fastest response time | ms | 5m | Fastest response time |
| Load Balancer | Slowest response time | ms | 5m | Slowest response time |
| Load Balancer | Current SSL Connection | cnt | 5m | Current number of SSL connections |
| Load Balancer | Total SSL Connection | cnt | 5m | Total number of SSL connections |
Load Balancer Listener
| Performance Item Group Name | Performance Item Name | Collection Unit | Collection Cycle | Description |
|---|---|---|---|---|
| State | Instance State | state | 5m | LB status |
| Load Balancer | Current Connection | cnt | 5m | Current number of connections |
| Load Balancer | Total L4 Connection | cnt | 5m | Total number of L4 connections |
| Load Balancer | Total L7 Connection | cnt | 5m | Total number of L7 connections |
| Load Balancer | Total TCP Connection | cnt | 5m | Total number of TCP connections |
| Load Balancer | Total Connection | cnt | 5m | Total number of connections |
| Load Balancer | Bytes processed in forward direction | bytes | 5m | Forward network bytes |
| Load Balancer | Packets processed in forward direction | cnt | 5m | Forward network packets |
| Load Balancer | Bytes processed in reverse direction | bytes | 5m | Reverse network bytes |
| Load Balancer | Packets processed in reverse direction | cnt | 5m | Reverse network packets |
| Load Balancer | Total failure actions | cnt | 5m | Total number of failure actions |
| Load Balancer | Current Request | cnt | 5m | Current number of requests |
| Load Balancer | Current response | cnt | 5m | Current number of responses |
| Load Balancer | Total Request | cnt | 5m | Total number of requests |
| Load Balancer | Total Request Success | cnt | 5m | Total number of successful requests |
| Load Balancer | Peak Connection | cnt | 5m | Peak number of connections |
| Load Balancer | Current Connection Rate | % | 5m | Current SSL connection rate |
| Load Balancer | Last response time | ms | 5m | Last response time |
| Load Balancer | Fastest response time | ms | 5m | Fastest response time |
| Load Balancer | Slowest response time | ms | 5m | Slowest response time |
| Load Balancer | Current SSL Connection | cnt | 5m | Current number of SSL connections |
| Load Balancer | Total SSL Connection | cnt | 5m | Total number of SSL connections |
Load Balancer Server Group
| Performance Item Group Name | Performance Item Name | Collection Unit | Collection Cycle | Description |
|---|---|---|---|---|
| Server Group | Instance State | state | 5m | LB Server Group status |
| Server Group | Peak Connection | cnt | 5m | Server group peak number of connections |
| Server Group | Healthy host | cnt | 5m | Server group number of healthy hosts |
| Server Group | Unhealthy host | cnt | 5m | Server group number of unhealthy hosts |
| Server Group | Request Count | cnt | 5m | Number of requests |
| Server Group | Response Count | cnt | 5m | Number of responses |
| Server Group | 2xx Response Count | cnt | 5m | Number of 2xx responses |
| Server Group | 3xx Response Count | cnt | 5m | Number of 3xx responses |
| Server Group | 4xx Response Count | cnt | 5m | Number of 4xx responses |
| Server Group | 5xx Response Count | cnt | 5m | Number of 5xx responses |
2.9 - Appendix C. Service-specific status check
Compute type
Virtual Server
| Performance Item Name | Description | Value |
|---|---|---|
| Instance State [Basic] | Instance Status | NOSTATE, RUNNING, BLOCKED, PAUSED, SHUTDOWN, SHUTOFF, CRASHED, PMSUSPENDED, LAST |
GPU Server
| Performance Item Name | Description | Value |
|---|---|---|
| Instance State [Basic] | Instance Status | NOSTATE RUNNING, BLOCKED, PAUSED, SHUTDOWN, SHUTOFF, CRASHED, PMSUSPENDED, LAST |
Bare Metal Server
| Performance Item Name | Description | Value |
|---|---|---|
| N/A | N/A | N/A |
Multi-node GPU Cluster [Cluster Fabric]
| Performance Item Name | Description | Value |
|---|---|---|
| N/A | N/A | N/A |
Multi-node GPU Cluster [Node]
| Performance Item Name | Description | Value |
|---|---|---|
| N/A | N/A | N/A |
Storage type
File Storage
| Performance Item Name | Description | Value |
|---|---|---|
| Instance State | File Storage volume status | * 1: Online in case * 0: other status values (Offline) |
Object Storage
| Performance Item Name | Description | Value |
|---|---|---|
| N/A | N/A | N/A |
Block Storage(BM)
| Performance Item Name | Description | Value |
|---|---|---|
| Instance State | Blockstorage Volume Status | * 1: running (normal) * 0: down (abnormal) |
Block Storage(VM)
| Performance Item Name | Description | Value |
|---|---|---|
| Instance State | Blockstorage volume status | * 1: running (normal) * 0: down (abnormal) |
Database type
PostgreSQL(DBaaS)
| Performance Item Name | Description | Value |
|---|---|---|
| Instance State [PID] | postgres process PID | * PID: when the postgres process exists * -1: when the process does not exist |
MariaDB(DBaaS)
| Performance Item Name | Description | Value |
|---|---|---|
| Safe PID | mariadb_safe process PID | * PID: when the mariadb_safe process exists * -1: when the process does not exist |
| Instance State [PID] | mariadb process PID | * PID: when the mariadb process exists * -1: when the process does not exist |
MySQL(DBaaS)
| Performance Item Name | Description | Value |
|---|---|---|
| Instance State [PID] | mysqld process PID | * PID: when the mysqld process exists * -1: when the process does not exist |
Microsoft SQL Server(DBaaS)
| Performance Item Name | Description | Value |
|---|---|---|
| Instance State [Cluster] | MSSQL cluster configuration status | * PID: when the mssql process exists * -1: when the process does not exist |
| Instance State [PID] | sqlservr.exe process pid | * For Microsoft SQL Server, the secondary server is also running with PID, so it’s impossible to check the status with only PID |
EPAS(DBaaS)
| Performance Item Name | Description | Value |
|---|---|---|
| Instance State [PID] | Postgres process PID | * PID: When the postgres process exists * -1: When the process does not exist |
CacheStore(DBaaS)
Redis
| Performance Item Name | Description | Value |
|---|---|---|
| Instance State [PID] | Redis-server process PID | * -1: in case the process does not exist |
| Sentinel State [PID] | Sentinel process PID | * -1: in case the process does not exist |
Valkey
| Performance Item Name | Description | Value |
|---|---|---|
| Instance State [PID] | Valkey-server process PID | * -1: in case the process does not exist |
| Sentinel State [PID] | Sentinel process PID | * -1: in case the process does not exist |
Data Analytics type
Event Streams
| Performance Item Name | Description | Value |
|---|---|---|
| AKHQ State [PID] | akhq process PID | * PID: akhq process exists * -1: process does not exist |
| Instance State [PID] | kafka process PID | * PID: when the kafka process exists * -1: when the process does not exist |
| Zookeeper State [Pid] | zookeeper process PID | * PID: when the zookeeper process exists * -1: when the process does not exist |
Search Engine
| Performance Item Name | Description | Value |
|---|---|---|
| Instance State [PID] | Elasticsearch process PID | * PID: When the Elasticsearch process exists * -1: When the process does not exist |
| Kibana State [PID] | Kibana process PID | * PID: When the Kibana process exists * -1: When the process does not exist |
Elasticsearch
| Performance Item Name | Description | Value |
|---|---|---|
| Instance State [PID] | Elasticsearch process PID | * -1: in case the process does not exist |
| Kibana State [PID] | Dashboard process PID | * -1: in case the process does not exist |
Opensearch
| Performance Item Name | Description | Value |
|---|---|---|
| Instance State [PID] | Opensearch process PID | * -1: in case the process does not exist |
| Dashboard State [PID] | Dashboard process PID | * -1: in case the process does not exist |
Vertica(DBaaS)
| Performance Item Name | Description | Value |
|---|---|---|
| Instance State [PID] | Vertica Process PID | * -1: when the process does not exist |
Container type
Kubernetes Engine
| Performance Item Name | Description | Value |
|---|---|---|
| Instance State | Cluster Status | * 1: Status check query sum(up{job=“kubernetes-apiservers”}) returns a value greater than 0 * 0: Status check query sum(up{job=“kubernetes-apiservers”}) returns a value less than or equal to 0 |
Container Registry
| Performance Item Name | Description | Value |
|---|---|---|
| Instance State | Container Registry Status | * 1: running (normal) * 0: down (abnormal) |
Networking type
Internet Gateway
| Performance Item Name | Description | Value |
|---|---|---|
| N/A | N/A | N/A |
Load Balancer(OLD)
| Performance Item Name | Description | Value |
|---|---|---|
| Instance State | Load Balancer status | Determined by provisioning_status in API call result |
- 1: ACTIVE
- 0: ETC|
Load Balancer Listener(OLD)
| Performance Item Name | Description | Value |
|---|---|---|
| Instance State | Load Balancer Listener status | Determined by provisioning_status in API call results * 1: ACTIVE * 0: ETC |
Load Balancer
| Performance Item Name | Description | Value |
|---|---|---|
| Instance State | Load Balancer status | Determined by provisioning_status in API call result |
- 1: ACTIVE
- 0: ETC|
Load Balancer Listener
| Performance Item Name | Description | Value |
|---|---|---|
| Instance State | Load Balancer Listener status, determined by provisioning_status in API call results * 1: ACTIVE * 0: ETC |
Load Balancer Server Group
| Performance Item Name | Description | Value |
|---|---|---|
| Instance State | Status of Load Balancer Server Group, determined by provisioning_status in API call results * 1: ACTIVE * 0: ETC |
Direct Connect
| Performance Item Name | Description | Value |
|---|---|---|
| N/A | N/A | N/A |
Cloud WAN
| Performance Item Name | Description | Value |
|---|---|---|
| Instance State | Attachment connection status | * 0: down * 1: up * 2: testing * 3: unknown |
Global CDN
| Performance Item Name | Description | Value |
|---|---|---|
| Instance State | Global CDN Status | * 1: running (normal) * 0: down (abnormal) |
3 - API Reference
4 - Release Note
Cloud Monitoring
- In July 2025, a linked service with Cloud Monitoring was added.
- Additional linked services: Compute(Multi-node GPU Cluster [Cluster Fabric], Multi-node GPU Cluster [Node]), Storage(Block Storage(BM), Block Storage(VM)), Networking(Cloud WAN, Global CDN), Database(Valkey), Data Analytics(Opensearch, Vertica(DBaaS))
- In February 2025, a linked service with Cloud Monitoring was added.
- Additional linked services: Container(Container Registry), Database(EPAS, Microsoft SQL Server), Data Analytics(Event Streams, Search Engine), Networking(Load Balancer, Load Balancer Listener, Load Balancer Server Group, VPN)
- Cloud Monitoring service has been released. It collects usage and change information of operating infrastructure resources, and supports a stable cloud operating environment through event occurrence/notification when exceeding the set threshold.