| Term | Definition |
|---|---|
| Discovery | It means the process of adding a device/interface in OpManager for monitoring. |
| Re-discovery | The process of discovering an existing device or a set of devices or interfaces to update newly added details such as device name, device type and hard disk space. |
| Rule Engine | An option used to automate post-discovery actions. For example, you can create a rule to associate Notification Profile to all server devices. Likewise, you can create rules to add monitors, add a business view, add an event log monitor and more. |
| Inventory | After the discovery process, all the devices and interfaces discovered can be viewed under the Inventory tab. Further, VLANs, subnets, VMs, IP SLA monitors, storage devices can be viewed under dedicated tabs such as Network, Server, Virtualization and Storage. |
| Device snapshot /summary page | Snapshot page refers to the page that opens when you click on a particular device from the list given under the Inventory tab. The snapshot page provides availability, health and in depth performance stats of a device. |
| Monitor | A monitor refers to the metric used to measure the performance of a device or interface. For example, CPU Utilization is a monitor that measures the level of CPU utilization for a device. |
| Device template | It is a default set of monitors that will be associated to a device once it is discovered in OpManager. Each device model will have a unique template and it differs based on the vendor and model. |
| Alarm | An alarm is an alert notification that is used to notify the user when a threshold violation occurs. |
| Threshold value | There are multiple threshold levels that are associated to monitors in OpManager: Attention, Trouble and Critical. For each monitor, a user can assign the threshold values and if a device crosses the specified threshold values for a monitor then an alarm is raised. |
| Severity | Refers to how serious the issue is. Attention, Trouble and Critical are the three types of severity. |
| Notification Profile | This feature allows you to configure the criteria and the notification channel to send alarm details from OpManager. |
| Business Views | A visual representation of the arrangement of devices in your network. |
| Dashboard | It gives a complete overview of your entire network. |
| Widgets | A widget is a window inside the dashboard. There are multiple widgets on the dashboard and each contains specific information. (Example: Recent Alarms, Devices by Utilization) |
| CCTV view | You can create a CCTV view (aka NOC view) by selecting multiple custom dashboards. This NOC view/CCTV will present selected dashboards alternatingly at regular intervals. This will be useful for your NOC team to centrally monitor the entire network. |
| Groups | Groups help you to organize multiple devices or interfaces to push bulk configurations. |
| Reports | A database of the monitoring statistics of your network devices and interfaces, primarily useful for future analysis. |
| Report builder | A feature that allows you to create a report with selected monitors from the Inventory page in the UI. (The report can be accessed under Reports--> Integrated Reports) |
| SNMP Trap | A traps is a cryptic message that is sent from the agent on the monitored device to the OpManager when a fault/network issue occurs in the device. |
| Workflow | An automation mechanism that can be created and executed by the user to accomplish routine tasks. |
| Polling interval | The time period between any two consecutive polls. |
| APM Plugin | This refers to the application manager plugin. By downloading and installing this plugin in OpManager, you will be able to monitor applications, servers, databases., etc. in your network. |
| Rebranding | This option helps you to change the default OpManager's logo into your organization's logo. |
| Custom fields | A user-defined specific detail that you want to add about a device or interface apart from the existing fields. (For example: Adding Service Tag to a device) This field will be displayed on the snapshot page of a device or interface. |
| Probe | It is the monitoring agent installed in a remote network site to monitor the network and send monitoring data to the Central. |
| Central | It gives a centralized view of the monitoring data collected from Probes installed in various network sites. |
| Agent | Agent is the small executable file installed in a remote windows device to monitor the device. With agent based monitoring, OpManager need not use its server resources to poll the remote device every time. The agent monitors the device and sends data to OpManager. |
Thank you for your feedback!
