Why is an agent update required?

The agent update is required for updating bug fixes in the previous agent version, new features or to address critical issues.

How often are agent updates released?

The agent is updated after every major release (that occurs once a quarter) or sometimes after a minor release or any hotfixes.

What is the downtime for agent updates?

Agent update downtime is very minimal and the update process takes from one minute to a maximum of two minutes.

  • The downtime also depends on the network bandwidth that is required to download the patch.
  • During this process, the agent service is stopped and restarted after the update.

How do I find devices that have agent policies?

To find devices with agent policies:

  1. Go to Setup > Accounts and click Clients.
  2. Click the client name.
  3. Select the Client Details tab to view the list of policies that are assigned to the resources.

How do I validate if the agent is successfully configured?

To validate configuration:

  1. Go to the Infrastructure tab.
  2. On the device list, search for the device on which the agent was deployed.
  3. Check for an icon that is displayed against the resource. This icon confirms that agent is successfully installed on the device.

How long are metric and alert data retained if the Agent loses network connectivity?

On loss of network connectivity, the Agent retains alert data for the last three days and retains metric data for the last four hours.

Why does OpsRamp see a Virtual Machine as a new device when it is moved between VMware Clusters or restored from backup or cloned?

Based on reconciliation logic we will create a device at the portal.
The creation of the new device could be a change in major resource attributes such as IP address, MAC address, BIOS id, MOID (VMware object id), etc.

Due to change in resource attributes of device the new resource is created on the portal.

Yes, you can link the resources by adding the old resource UUID to our agent configuration DB (Database).

You may lose the new resource metric data if you change the resource UUID from new to old.

Does OpsRamp transfer the monitoring templates assigned on the old device to the new device?

No, monitoring templates will not be transferred to the new device if they are manually assigned on the old device.

If the monitoring template is assigned with DMP (Device Management Policy) on the old device, then the templates will be transferred from the old device to the new device.

Does the new resource keep the old metric data?

No, old metric data will not be available on the new device, because the device or resource is treated as a new resource. Hence, everything gets monitored newly on the new device and successfully onboarded to OpsRamp.

Can we map the data such as Service Maps, Notes, and Knowledge Base articles to the new devices?

No, the Notes cannot be mapped to the new devices.
However, if the Service Maps and Knowledge Base articles are created with DMP, then these will be mapped to the new devices.

Where can I find the Windows Defender patches installed by the OpsRamp Agent?

Windows Defender patches will not be displayed in the Control Panel, whether it is installed by a third-party application such as OpsRamp Agent or by Windows Defender itself.

You should navigate to Event Viewer to view the information about Windows Defender patches installed by the OpsRamp Agent or any third-party applications.

Can we install the agent in a custom location?

Previously, the installation and configuration of the agent were automatically set to the default location. However, now you have the flexibility to install and configure the agent at your desired location. You can opt for a custom path, and the agent will be installed in that same location. Here is an example:

Example for Window:

  • Default Location: C:\Program Files (x86)\OpsRamp\Agent
  • Custom Path: {custom_dir}\OpsRamp\Agent

Example for Linux:

  • Default Location: /opt/opsramp/agent
  • Custom Path: {custom_dir}/opsramp/agent

Can we share any OpsRamp installer file through Microsoft Teams?

Avoid sharing any executable files or OpsRamp installer files through Microsoft Teams, as this action can internally activate processes within the Teams platform. Furthermore, sharing such files may lead to the creation of dummy resources in the OpsRamp portal.

To prevent any unexpected consequences, make sure not to share any OpsRamp sensitive documents or installer files via Microsoft Teams.

What ports are required for the Linux agent deployment tool when communicating from the jump server to the end server?

The Ansible agent script utilizes SSH for deployment, hence requiring port 22 for SSH communication from the jump server to the end server.

If we are using the agent deployment tool, do we need ICMP, Port 135, 139, and 445 from the Windows jump server to the End server?

Yes, we require either ICMP (ping) or port 135 for the device discovery. We used xCmd tool to deploy the agent deployment and this tool used the ports 135, 139 and 445.

While using the Windows deployment tool, how does communication occur between a Windows jump server and the end agent server?

The communication is facilitated through the xCmd tool. Internally, xCmd uses shared paths to push the agent installer to the remote machine.

Note: Make sure that ports 135, 139, and 445 are open for the proper functioning of the xCmd tool.

Mention the way of communication between Agent and Gateway along with port and direction?

Communication from Agent to Gateway is bi-directional and Agent communicates with Gateway using 3128 port. The 3128 port is a in-bond port in Gateway side.