(Optional) Manually Configuring the Agent on a Windows Server

Scenarios

After you install the Agent, configure it by clicking Restore Agent Configurations on the Cloud Eye console. If the Agent fails to be configured by clicking Restore Agent Configurations or due to other reasons, manually configure it by following the instructions provided in this topic.

Constraints

The Agent cannot be installed on Windows BMSs.

Windows and Linux OSs are supported. For details, see What OSs Does the Agent Support?

Prerequisites

The Agent has been installed.

Checking the Version of the Agent In Use

1. Log in to an ECS as an administrator.
2. Check the installation path and the Agent version.
   • The installation path of the early version of the Agent is C:\Program Files\telescope. For details about how to manually configure the Agent, see Procedure (for the Early Version of the Agent).
   • The installation path of the new version of the Agent is C:\Program Files\uniagent\extension\install\telescope. For details about how to manually configure the Agent, see Procedure (for the New Version of the Agent).

Procedure (for the New Version of the Agent)

1. Log in to the ECS.
2. Open the conf.json file in the C:\Program Files\uniagent\extension\install\telescope\bin folder.
3. Configure the following parameters. For details, see Table 1.

   {
       "InstanceId":"XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
       "ProjectId": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
       "AccessKey": "XXXXXXXXXXXXXXXXXXXX",
       "SecretKey": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
       "RegionId": "ap-southeast-1",
       "ClientPort": 0,
       "PortNum": 200
   }

   Table 1 Public parameters

   Parameter	Description
   InstanceId	(Optional) Specifies the ECS ID. You can log in to the management console and view the ECS ID in the ECS list. NOTE: If you do not configure InstanceId, retain "InstanceId":"". If you configure it, ensure that the following two requirements are met: The ECS ID must be unique at all sites, that is, in the same region, InstanceId used by the Agent cannot be the same. Otherwise, errors may occur. The InstanceId value must be consistent with the actual ECS or BMS ID. Otherwise, you cannot see the OS monitoring data on Cloud Eye.
   ProjectId	Specifies the project ID. You do not need to configure ProjectId. Retain "ProjectId": "". If you wish to configure it, perform the following operations: Log in to the Cloud Eye console, click the username in the upper right corner, and choose My Credentials. Under Projects, obtain the project ID for the region where the ECS or BMS is located.
   AccessKey/SecretKey	To obtain the AK and SK, perform the following operations: Log in to the Cloud Eye console, click the username in the upper right corner, and choose My Credentials, and choose Access Keys. If you have obtained the access key, obtain the AccessKey value and the SecretKey value in the credentials.csv file saved when you create Access Keys. If no access keys are available, click Create Access Key to create one. Save the credentials.csv file and obtain the AccessKey value and the SecretKey value in it. NOTICE: For the security purpose, use an IAM username with the CES Administrator and LTS Administrator permissions. The configured access key must be within the Access Keys list on the My Credentials page. Otherwise its authentication will fail and you cannot view OS monitoring data on Cloud Eye.
   RegionId	Specifies the region ID.
   ClientPort	Specifies the start port number used by the Agent. NOTE: The default value is 0, indicating that the Agent will randomly use any port. Ports 1 to 1023 are reserved. You are advised not to specify a port in this range for the Agent.
   PortNum	Specifies the number of ports configured for the Agent. NOTE: The default value is 200. If ClientPort is 5000, the port range will be 5000 to 5199.

   

   • After you configure the Agent, its status is still displayed as Uninstalled because no monitoring data is reported yet. Wait 3 to 5 minutes and refresh the page.
   • If the Agent is in the Running state, the Agent has been installed and has started to collect fine-grained metric data.

Procedure (for the Early Version of the Agent)

1. Log in to the ECS.
2. Open the conf.json file in the telescope_windows_amd64\bin directory.
3. Configure the following parameters. For details, see Table 2.

   Table 2 Public parameters

   Parameter	Description
   InstanceId	(Optional) Specifies the ECS ID. You can log in to the management console and view the ECS ID in the ECS list. NOTE: If you do not configure InstanceId, retain "InstanceId":"". If you configure it, ensure that the following two requirements are met: The ECS ID must be unique at all sites, that is, in the same region, InstanceId used by the Agent cannot be the same. Otherwise, errors may occur. The InstanceId value must be consistent with the actual ECS or BMS ID. Otherwise, you cannot see the OS monitoring data on Cloud Eye.
   ProjectId	Specifies the project ID. You do not need to configure ProjectId. Retain "ProjectId": "". If you wish to configure it, perform the following operations: Log in to the Cloud Eye console, click the username in the upper right corner, and choose My Credentials. Under Projects, obtain the project ID for the region where the ECS or BMS is located.
   AccessKey/SecretKey	To obtain the AK and SK, perform the following operations: Log in to the Cloud Eye console, click the username in the upper right corner, and choose My Credentials, and choose Access Keys. If you have obtained the access key, obtain the AccessKey value and the SecretKey value in the credentials.csv file saved when you create Access Keys. If no access keys are available, click Create Access Key to create one. Save the credentials.csv file and obtain the AccessKey value and the SecretKey value in it. NOTICE: For security purposes, it is recommended that the user be an IAM user with the CES Administrator and LTS Administrator permissions only.. The configured access key must be within the Access Keys list on the My Credentials page. Otherwise its authentication will fail and you cannot view OS monitoring data on Cloud Eye.
   RegionId	Specifies the region ID.
   ClientPort	Specifies the start port number used by the Agent. NOTE: The default value is 0, indicating that the Agent will randomly use any port. Ports 1 to 1023 are reserved. You are advised not to specify a port in this range for the Agent.
   PortNum	Specifies the number of ports configured for the Agent. NOTE: The default value is 200. If ClientPort is 5000, the port range will be 5000 to 5199.

4. Wait for a few minutes.

   If Agent Status is Running, the Agent has been installed and starts to collect fine-grained metric data.