Rapidly Responds to Equipment Failure and Improves Resource Management
Use this service to continuously monitor all resources involved with your system’s operation and warn you of possible overloads, according to preset values. By preventing or quickly counteracting equipment failures and providing strategies for efficient resource performance, our management technology ensures continuous service to your users.
- Ensures Stable Operation of Computing Resources
- Through basic monitoring functions, you can receive system-related indicators, such as CPU usage rate, disk usage rate, and memory usage rate. Detailed monitoring functions, such as event settings, and comparison function per computing resource, enable effective failure analysis and quick response.
- Various information collection and detailed item settings
- 8개 분류 내 36개의 세부 항목에 대한 모니터링 성능 정보를 수집하고, 12개 분류 내 57개의 세부 항목과 관련된 이벤트 경보를 설정할 수 있습니다. 이를 통해 보다 세밀한 모니터링이 가능합니다.
- Graphs and Statistics
- You can check your monitoring data in various forms through the HTTP GET/POST method of the RESTful API. Users can directly collect and analyze real-time data as well as daily statistics through the API to be used appropriately for their businesses.
- Monitoring of various services
- You can check the state of computing resources of various services, such as Server and Auto Scaling provided by NAVER CLOUD PLATFORM. Additional features are planned to be added later on for quick response on mobile applications, such as logs and linking designated metrics.
- Customized monitoring
- You can create and operate the charts and dashboards in the desired format. Also, by dividing and monitoring servers by group, you can quickly check the status of the interested resource and quickly respond to failures.
- Simple Event Settings
- A simple template allows you to change various event-related settings with a click of a button. Designed with an intuitive UI, the Event Configuration Templates help you to manage thresholds and notifications quickly and easily.
Detailed Features
Provides various functions for effective monitoring.
Setting Monitoring Items and Interval
Can collect monitoring information and set notification settings for events that occur for various items such as CPU, memory, disk, load average, network, disk I / O, file monitoring, file system, log monitoring, process, and Ping Fail, etc. Among these items, some items such as Ping Fail and log monitoring are provided only with event notification setting, and up to 20 items can be set for event setting. The monitoring results are provided in 1 minute, 5 minutes, 2 hours and 1 day intervals according to the selected period. In particular, for the last 8 days, monitoring results are stored every minute for efficient response. Current monitoring information cycle is minimum one-day up to one year.
Collected monitoring information and event notification setting items
| Monitoring information collected | Event notification setting items | ||
|---|---|---|---|
| Category | Details | Category | Details |
| CPU | Used(%), System(%), User(%), iowait(%) | CPU | Used(%), System(%), User(%), Idle(%), iowait(%), nice(%), irq(%), softirq(%), privileged time(%), dpc time(%), interrupt time(%), processor time(%) |
| Memory | Used(%), Total/Used/Free/Buffer/Cached(Bytes) | Memory | Used(%), Total/Used/Free/Buffer/Cached/Shared(Bytes), pgin/sec(MB), pgout/sec(MB) |
| File System | FimeSystem Name, Size(MB), Used(MB/%), Avail(MB), Mount | File System | Used/iuse(%), availability/used capacity (MB), mount status |
| NIC | Output(bps/pps/error), Input(bps/pps) | NIC | Output(bps/pps/error), Input(bps/pps/error), collision |
| Disk I/O | Read Bytes, Write Bytes | Disk I/O | Read Bytes/Count, Write Bytes/Count |
| Swap | Used(%), Total/Used/Free(Bytes) | Swap | Used(%), Total/Used(Bytes) |
| Load Average | 1min, 5mins, 15mins | Load Average | 1min, 5mins, 15mins |
| File Watch | Changes, Size, Existence, No change | ||
| No. of Users | No. of Users | ||
| Log Watch | File Log | ||
| Ping Fail | Ping Fail | ||
| Process | Process name, PID, CPU (%), Memory (%/KB), Prior, Thread, CPU Time for TOP 10 | Process | Process down, CPU (%), Memory(%/KB), Number of Thread, Total number of processes, Process restart |
Monitoring Dashboard
The monitoring dashboard compiles essential information about your network on a single screen for maximum efficiency. The dashboard displays the status of events occurred and terminated during a day, the status of events occurred over the past week, and the status of the top 5 servers by item for those with monitoring configured. With the dashboard, you can continuously monitor the status of the server in operation and conveniently check a specific server of your choice. To further increase the efficiency of system operation, you can easily use the dashboard data to track displayed issues in greater detail and track occurring issues.
Set Monitoring Parameters
Up to 8 categories and 36 items are available for monitoring (for some items, only event notification settings are available). By default, status information for 10 of the 36 items is provided, enabling detailed analysis. You can change the 10 items to suit the needs of your business. A chart comparison function is provided to allow you to select specific servers you want to compare and compare them by item. This is useful for checking differences between servers to identify problems or issues. It is also convenient when identifying servers that have a large difference in monitoring indicators in particular items compared to other servers.
Customizable dashboard
The 'My Chart' feature allows you to create your own customized charts and dashboards so you can see the performance information of the instances in real-time. The 'My Group' feature allows you to group your instances to efficiently monitor your primary and interest servers and react quickly in the event of a failure. In addition, the user-customized charts and dashboards are provided in the form of widgets to allow users to check desired information easily.
Event Setting Log
The event setting log shows you the history of your event settings for the last month. To prevent the improper use of the service, you can check the monitoring usage of the user of their event setting details, set date, responsible personnel, and access IP.
Event Setting Template
You can easily manage frequently-used information, such as events and receivers, in a template form. Save a template in advance so you can quickly apply it to a newly-added instance for a fast event setting.
Auto Scaling Group Monitoring
Auto Scaling group monitoring averages the set parameters of servers within a group to provide a monitoring service.
Events can be set for 6 categories (CPU, memory, load average, network, disk I/O, and the file system) and 15 items.
Using the API
You need to get an OAuth authentication key to use the API. An API authorization key can be issued and managed from My Page in the portal. The API is executed with the RESTful API type HTTP GET/POST method call. The API enables you to create various monitoring management features.
Monitoring Settings
| Monitoring Item | Item | Event Triggering Condition | Settings | Example | Remark |
|---|---|---|---|---|---|
| CPU | Used(%) | The CPU usage (%) value (1 min average) remains equal to or higher than the threshold for the specified duration. | 1. Usage ▲▲ % 2. or higher 3. Duration OO mins | When the CPU usage remains ▲▲% or higher for OO mins or longer, an event is generated. | - Monitoring is not performed per individual CPU core, but for all CPU cores |
| iowait(%) | CPU iowait(%) value (1-min average) remains equal to or higher than the threshold for the specified duration. | 1. Usage ▲▲% 2. or higher 3. Duration OO mins | When the CPU iowait remains ▲▲% or higher for OO mins or longer, an event is generated. | ||
| Memory | Used(%) | The memory usage (%) value (1 min average) remains equal to or higher than the threshold for the specified duration. | 1. Usage ▲▲% 2. or higher 3. Duration OO mins | When the memory usage remains ▲▲% or higher for OO mins or longer, an event is generated. | |
| Swap | Used(%) | The swap usage (%) value (1-min average) remains equal to or higher than the threshold for the specified duration. | 1. Usage ▲▲% 2. or higher 3. Duration OO mins | When the swap usage remains ▲▲% or higher for OO mins or longer, an event is generated. | |
| Disk I/O | read bytes | The read byte value (per second) of the disk remains equal to or higher than the threshold for the specified duration. | 1. ▲▲▲bytes/sec 2. or higher 3. Duration OO mins | When the read byte value (per second) of the disk remains **% or higher for OO mins or longer, an event is generated. | |
| write bytes | The write byte value (per second) of the disk remains equal to or higher than the threshold for the specified duration. | 1. ▲▲▲bytes/sec 2. or higher 3. Duration OO mins | When the write byte value (per second) of the disk remains **% or higher for OO mins or longer, an event is generated. | ||
| Network | bps in | The inbound byte value (per second) of the NIC remains equal to or higher than the threshold for the specified duration. | 1. Baud rate ▲▲▲bytes/sec 2. or higher 3. Duration OO mins | When the inbound byte value (per second) of the NIC remains **% or higher for OO mins or longer, an event is generated. | - The interface name of the network to be monitored must be defined (e.g., eth0, bond0) |
| bps out | The outbound byte value (per second) of the NIC remains equal to or higher than the threshold for the specified duration. | 1. Baud rate ▲▲▲bytes/sec 2. or higher 3. Duration OO mins | When the outbound byte value (per second) of the NIC remains▲▲% or higher for OO mins or longer, an event is generated. | ||
| pps in | The inbound packet value (per second) of the NIC remains equal to or higher than the threshold for the specified duration. | 1. Baud rate ▲▲▲packets/sec 2. or higher 3. Duration OO mins | When the inbound packet value (per second) of the NIC remains ▲▲% or higher for OO mins or longer, an event is generated. | ||
| pps out | The outbound packet value (per second) of the NIC remains equal to or higher than the threshold for the specified duration. | 1. Baud rate ▲▲▲packets/sec 2. or higher 3. Duration OO mins | When the outbound packet value (per second) of the NIC remains **% or higher for OO mins or longer, an event is generated. | ||
| File Watch | Size | The file size exceeds the threshold for the specified duration, starting from the set time. | 1. File Size ▲▲▲KB 2. or higher 3. Duration OO mins 4. Full path of the file (e.g., /tmp/abc.ext) | If the file size of /tmp/acb.ext is ▲▲▲KB or larger for OO mins or longer, an event is generated. | The remote user must have permission to access the appropriate file. |
| Changes | The file is modified every minute for the specified duration, starting from the set time. | 1. Duration OO mins 2. Full path of the file (e.g., /tmp/abc.ext) | If the file (/tmp/acb.ext) is consecutively modified every minute for OO mins, an event is generated. E.g. When the time is set to 0 mins, an event is generated as soon as the file is modified. When set to 2mins, an event is generated if the file is modified within 1min from the set time and again within the following minute. | ||
| No change | The file is not modified for the specified duration, starting from the set time. | 1. Duration OO mins 2. Full path of the file (e.g.) /tmp/abc.ext) | If the file (/tmp/acb.ext) is not modified for OO mins, an event is generated. | ||
| File existence | If the file does not exist, an event is generated. | 1. Full path of the file (e.g., /tmp/abc.ext) | If the file /tmp/acb.ext does not exist, an event is generated. | ||
| File System | Used(%) | The usage (%) of the file system exceeds the threshold for the specified duration. | 1. Usage ▲▲% 2. or higher 3. Duration OO mins 4. Mounted directory (e.g.) /home | If the usage (%) of the /home directory mounted remains ▲▲% or higher for OO mins or longer, an event is generated. | - A file system mounted on the network cannot be monitored. (e.g., NFS or fuse) |
| Load Average | Load average (1 min) | The value (1 min average) of the load average is remains higher than the threshold for the specified duration. | 1. 1 min average of Load Average ▲▲ 2. or higher 3. Duration OO mins | If the value (1min average) of the load average remains for more than OO mins at higher than ▲▲, an event is generated. | You can set the watch feature for only the Linux server. |
| Load average (5 mins) | The value (5 mins average) of the load average is remains higher than the threshold for the specified duration. | 1. 5 mins average of Load Average ▲▲ 2. or higher 3. Duration OO mins | If the value (5mins average) of the load average remains for more than OO mins at higher than ▲▲, an event is generated. | ||
| Load average (15mins) | The value (15mins average) of the load average is remains higher than the threshold for the specified duration. | 1. 15mins average of Load Average ▲▲ 2. or higher 3. Duration OO mins | If the value (15mins average) of the load average remains for more than OO mins higher than ▲▲, an event is generated. | ||
| Log Watch | File Log | In the file being watched, the string is included (or not included) every minute for the specified duration, starting from the set time. | 1. Log matching string (e.g.) Exception 2. Included/Not included 3. Duration OO mins 4. Full path of the file (e.g.) /tmp/abc.ext) | If the string ‘Exception’ is included (or not included) in the file (/tmp/abc.log) every minute for the specified time, starting from the set time, an event is generated. E.g. If the duration is set to 0 min, an event is immediately generated as soon as the matching string is included (or not included). If set to 2mins, an event is generated if the matching string has been included (or not included) within 1 minute from the set time and is included again (or not included) within the following 1 minute. | - The nbpmon user must have permission to access the watched over file. - Encoding uses UTF-8. - Case-sensitive. - Regular expressions can be used. |
| Process | Process down | The process is down. | 1. Process matching string (e.g.) snmp | If the number of processes that include the string ‘snmp’ is 0, an event is generated. E.g. When the process /home1/nbpmon/noms/nsight/bin/noms_nsight-start and the process /usr/sbin/snmp-start and the matching string are set to ‘start’, the number of processes is recognized as 2. When both processes are down, the number is recognized as 0 and an event is generated. | - To monitor a single process, enter the entire name of the process as the setting. E.g. Match the string to the process name extracted by ps –ef. |
| CPU(%) | The CPU usage (%) of the process remains ** or higher than the threshold for the specified time. | 1. Usage ▲▲% 2. or higher 3. Duration OO mins 4. Process matching string (e.g.) snmp | If the usage (%) of the CPU occupied by the process that includes the string ‘snmp’ remains ▲▲ or higher for OO mins or longer, an event is generated. E.g. When the process /home1/nbpmon/noms/nsight/bin/noms_nsight-start and the process /usr/sbin/snmp-start and the matching string are set to ‘start’, the number of processes is recognized as 2. When the sum of CPU usage (%) occupied by the two processes remains ▲▲ or higher for OO mins or longer, an event is generated. | ||
| mem(%) | The memory usage (%) of the process remains ** or higher than the threshold for the specified time. | 1. Usage ▲▲% 2. or higher 3. Duration OO mins 4. Process matching string (e.g.) snmp | If the usage (%) of the memory occupied by the process that includes the string ‘snmp’ remains ▲▲ or higher for OO mins or longer, an event is generated. E.g. When the process /home1/nbpmon/noms/nsight/bin/noms_nsight-start and the process /usr/sbin/snmp-start and the matching string are set to ‘start’, the number of processes is recognized as 2. When the sum of memory usage (%) occupied by the two processes remains ▲▲ or higher for OO mins or longer, an event is generated. | ||
| Ping Fail | Ping Fail | Monitoring does not work for 3 consecutive mins or longer, and the collector server has sent 10 or more consecutive ping packets (at an interval of 3 seconds) that have failed to reach the server. | - | If monitoring does not work for 3 consecutive mins or longer, and the collector server has sent 10 or more consecutive ping packets (at an interval of 3 seconds) that have failed to reach the server, an event is generated. | - The collector server must be able to send and receive ping packets to and from the server. |
Related Services
Pricing Information
To help you operate your business flexibly in different situations, we offer a practical service and the corresponding pricing model.
| Classification | Usage Fee |
|---|---|
| Basic Monitoring | Free |
| Detailed Monitoring (including event and notification services) | Free |
Was this page helpful?