--- title: "Configuring servers for monitoring" canonical: "https://thoughtdata.refined.site/space/TUD/57672498/Configuring%20servers%20for%20monitoring" format: markdown --- ## Configuring servers for monitoring This section describes manual configuration of individual servers for Infrastructure monitoring. Related Topic [Discovery](https://thoughtdata.atlassian.net/wiki/spaces/e360/pages/57770502) Optionally you may choose to "auto discover" servers for monitoring using the Discovery processor more details. Servers pre-configured using manual approach are skipped during the discovery process. Launch Configuration workflow in Enterprise360 on left pane and select **"Entity Configuration"**. Perform the following steps for configuring each server manually. Click the "Entity Configuration" tab. **Adding Servers for monitoring using SSH/WMI method** If you are adding the server using SSH or WMI method. In the Entity Type drop-down menu click "Host". ![image](media://70f0f7a7-bfe0-46e2-9dac-b8560a650a37) Discovery  Click "Add New Host". ![image](media://15e6021f-0f0a-4c23-b547-e53e5e5ce1ea) Add new server/device Click "ssh" from the protocol drop-down list. The supported sensors which are provisioned and up and running are listed in the "Sensor Name" drop-down list. Choose the right InfraSense sensor depending on whether you need to add Linux/Windows based servers. Select the right InfraSense sensor name which you would like to associate the server for monitoring as illustrated below. ![image](media://30d60c26-1143-4acb-b18f-5f4102112e79)  Enter specific details in the fields as described in the table below. | | | | --- | --- | | Option/Field... | Click/Enter... | | IP Address | The IP address of the host (server) being configured.
**Note**: If the server has multiple IP addresses, provide the primary IP address of the server which is used to control the routing/firewall rules on the server.  If Server is expected to change the IP address frequently(E.g. : Microservices environment in public cloud), Remote monitoring using SSH/SNMP/WMI is not recommended and you will have to choose InfraSense Active agent for monitoring such servers. InfraSense active agent is a software agent which resides on the server and monitors the server continuously irrespective of its IP address getting changed quite often. InfraSense active agent has pre-configured IP of InfraSense sensor to which it communicates. Refer to InfraSense active agent section for more details | | Access port | The port associated with the protocol selected. The port number is auto configured depending on the method selected. Change this setting only if you are running SSH/WMI on non standard ports(Uncommon in most environments) | | Username | The username associated with the server (machine/server). | | Password | The password pertaining to the username. | | Domain | The Domain name of the server being configured.(Optional) If the server allows domain authentication (primarily for windows based systems) the domain name will be used as configured. | | Polling interval (minutes) | The frequency of polling for infrastructure metrics for this server. Default 5 minutes **Note**: Changing this value to lower than 5 minutes can increase the load on your InfraSense sensor. This configuration impacts your InfraSense performance and scalability. | | Save | Save the configuration to add the server for monitoring. | Post configuration, to verify if Enterprise360 is successfully monitoring your added server launch "Discovered devices" dashboard and check if the server is discovered and added successfully for continuous monitoring. **Adding Servers for monitoring using SNMP method** If you are adding the server using SNMP method. In the Entity Type drop-down menu click "SNMP". ![image](media://70f0f7a7-bfe0-46e2-9dac-b8560a650a37) SNMP Configure the below settings ![image](media://acc43752-a45c-4dbf-a4ec-f55c03f2981f) Add new SNMP based server/device  Enter specific details in the fields as described in the table below. | | | | --- | --- | | Option/Field... | Click/Enter... | | SNMP Version | The SNMP Version used to communicate to the server/device. Currently supported options are V1 and V2c. SNMPv3 is currently in beta phase | | Sensor Name | Choose the right InfraSense Sensor name which you would like associate with the server/device for SNMP monitoring. Only those InfraSense sensor which has SNMP collector enabled will be provided in the drop down list | | Device IP | IP address of the server/device on which SNMP is enabled | | Access Port | Defaults to 161, Change to the correct UDP port number if SNMP is configured on a non standard port other than 161(Uncommon in most IT environments) | | Polling interval (minutes) | The frequency of polling for infrastructure metrics for this server. Default 5 minutes **Note**: Changing this value to lower than 5 minutes can increase the load on your InfraSense sensor. This configuration impacts your InfraSense performance and scalability. | | Read Community | The SNMP Read Community string configured on the server(Default: public). | | Trap Port | Defaults to 162, Change to the correct UDP port number if SNMP Traps are configured to listen on non standard port other than 162 (Uncommon in most IT environments) | | Save | Save the configuration to add the server/device for monitoring. | After completing the configuration steps, perform the following steps to verify that Enterprise360 is monitoring your server/device: - launch the "Discovered devices" dashboard. - see that the server/device is listed in the table of discovered and added devices. See [Discovery](https://thoughtdata.atlassian.net/wiki/spaces/e360/pages/57672498). Once verified Enterprise360 successfully performs continuous monitoring  of the devices.