Troubleshoot common issues

Available in Classic and VPC

You might run into the following problems when using Cloud Insight. Find out causes and possible solutions.

No server response

Server does not respond at all (server hangs), metric is not collected, and alarm does not pulse.

Cause

When there's a server hang, the agent doesn't work because it can't get the CPU assigned. The problem may continue until the process causing the hang releases the hanged status on its own, or until you forcibly end the process.

Solution

If you cannot input anything to the server, you may have to force to restart it.
If a server is not working normally due to hangs or issues in the agent or network, use agent_status metric from Server (Classic) or Server (VPC) to perform a check.

Dataset is not collected

The agent is properly running, but no data is collected in Cloud Insight.

Cause

The outbound communication from agent to Cloud Insight may be blocked due to reasons such as intra-server firewall settings, security solutions installations, etc., even if the agent is properly running.

Solution

See the following port list and check if the firewall is down.

Classic environment

VPC environment

Service data is not viewed

NAVER Cloud Platform's service data is not available on the dashboard.

Cause

You can view the basic metrics provided by default from each NAVER Cloud Platform service without any additional settings in Cloud Insight. For Extended Metrics that are additionally provided, you need to first set them up from the console of each service.

Solution

• Check the service list in the API guides for the basic/extended metric provided by each service.
• For Server (VPC), you can set it up through detailed monitoring settings. For more information, see detailed monitoring setting.
• Extended metric is collected from the setting time. Check whether the inquiry period in the Cloud Insight has been correctly set.

Server is created/deleted continuously whenever ASG policy is registered

When ASG policy is registered as an action, servers are continuously created/deleted.

Cause

If you've set up an ASG policy as an action when creating an event rule, the event's occurrence will execute the ASG policy. Then the policy will run with the cooldown time specified in the ASG policy. When the Event ends, the policy also ends.

Solution

So, servers can be continuously created or deleted until event ends.

The created custom schema is not displayed

Custom schema was created but is not found on the console.

Cause

You can check for it in the console, but only after data is collected with the custom schema created.

Solution

See SendData API for data transfer. Data can be viewed after data collection has begun and a specific time has passed according to the aggregation interval set when the custom schema was created.

The data sent to API is not displayed

I sent data through the API, but I can't find it in the console.

Cause

It is likely that the default period for the data inquiry was misconfigured.

Solution

The default period for searching data on Cloud Insight is set to 1 hour before the search time. Search after setting the search period so that it includes the point in time where you sent them through the API.

The data sent to API differs from the results displayed on the dashboard

The data sent to API differs from the results displayed on the dashboard.

Cause

Cloud Insight calculates collected data using various aggregation functions for each specific cycle. The result you see on the dashboard is the calculated result, so it may differ from the data you sent to API.

Solution

You can set the aggregation interval and aggregation functions when creating custom schema.

Agent was not installed

Agent was not normally installed.

Solution

If agent was not normally installed, you can reinstall it in the following ways.

Linux

1. To abort agent, run /home1/nbpmon/agent_controller_linux/stop_agent.sh

2. To delete agent, run /home1/nbpmon/agent_controller_linux/uninstall_agent.sh

3. To delete agent installation path, delete /home1/nbpmon/agent_controller_linux Back up necessary files in advance.

4. Run agent installation.

   • For agent's installation, see agent installation.

Window

1. Run the following command to stop agent.

   C:\Program Files(x86)\NBP\agent_controller_windows\agent.bat stop
   

2. Run the following command to delete agent.

   C:\Program Files (x86)\NBP\agent_controller_windows\agent.bat uninstall
   

3. To delete agent installation path, delete C:\Program Files (x86)\NBP\agent_controller_windows Back up necessary files in advance.

4. Run agent installation.

   • For agent's installation, see agent installation.