Monitoring provides 360-degree visibility for applications, servers, virtualization, containers, synthetics, storage, and network devices.
A monitor is a mechanism to check a device periodically for its behavior and performance. Using monitoring, you can gather information and keep track of the performance of your target resources.
As part of the onboarding process:
- All resources in your network are discovered and managed.
- Monitoring templates are assigned to monitor resources according to the configured metrics.
- Timely alerts are raised for quick action.
The dashboard acts as a window to monitor the health, performance, and availability of resources.
The OpsRamp platform includes hundreds of built-in monitors that capture availability and performance metrics and optimal thresholds for supported resources.
View service impact
Your organization may be responsible for managing different types of IT services, for example:
- Applications (for example, an order management application) or
- Infrastructure services (for example, Wi-Fi for the office).
- IT resources (for example, servers, switches, and routers) deployed in your environment participate (directly or indirectly) in some IT service that serves end users.
Therefore, it is important to have line of sight between IT resources and their impact on users.
OpsRamp’s service maps offer a way to organize your IT resources into a hierarchical structure, so that you can easily tie the health of your resources to end user impact.
Manage from the cloud
OpsRamp is a SaaS application. You can simply log into OpsRamp through a browser and manage your environments from a single point.
Extend the platform
You can extend OpsRamp to monitor any type of IT resource. Multiple options are available to you to configure or write your own custom monitors, including APIs. Extensive APIs are provided for integrating OpsRamp into your operational task flows.
Monitor process workflow
The monitoring management process workflow involves:
|Metrics||Metrics are atomic elements indicating the exact attributes that help you retrieve the health and performance of the target resource or application.|
|Monitor||A monitor is a logical group of metrics that you can customize to monitor any specific technology or resource.|
|Template||Templates contain a group of monitors that are applied on either single or multiple devices.|
The following mechanisms are used to monitor devices:
- PING: PING monitoring continuously checks hosts for availability to detect connection failures. PING measures the packet loss and round trip time using ICMP.
- SNMP: Simple Network Management (SNMP) Protocol is a well-known and popular protocol for network management used for collecting information and configuring network devices such as Servers, Printers, Hubs, Switches, and Routers on an Internet Protocol (IP) network.
- WMI: Windows Management Instrumentation (WMI) describes the processes and utilities required to scan systems remotely for early warning signs of potential failure. WMI is the primary management technology for Microsoft Windows operating systems.
- API: OpsRamp uses application-specific APIs to monitor application or devices.
|Templates||Apply a monitoring template to a particular target resource or a set of target resources of the same type.|
|SNMP Traps||Monitor your SNMP devices using SNMP Traps configurations. You can create SNMP Trap monitors and receive traps for the devices.|
|Synthetic Monitoring||Track the performance of your websites and internet services and remove bottlenecks before impacting the performance of your website.|
|Gateway based Application Monitoring Adapters||Monitor your applications using OpsRamp Gateway using the application monitoring adapters before impacting the performance of your website.|
|Custom Monitors||Create Agentless Custom Monitors for Linux and Windows devices.|
|Event Log Monitoring||Monitor the event logs generated in the system viewer of all Windows devices in your network.|
|Native Monitors||You can add monitors, such as StatsD, Process Statistics, Linux File Integrity monitor, to monitor certain attributes in your Windows and Linux devices.|
After monitoring your resources, track the responses from the Alerts view, Metrics and Monitors tab in Infrastructure.
Types of monitors
OpsRamp supports two types of monitors:
- Native Monitors
- Custom Monitors
The following table describes the different Agent G1 monitors:
|Performance Monitors||Validate the metric availablity. For example CPU, disk utilization, and memory utilization. Selecting Disk and Memory monitors for Linux OS generates graphs each for disk and memory usage in percentage and gigabytes.|
|Application Monitors||Set threshold and frequency for an application and generate alerts. For example, to set threshold for Memory Utilization(%) and Disk Utilization(%) application, select:|
|SNMP Monitors||Initiate SNMP monitoring and set thresholds to receive alerts.|
|Event Log Monitor||Monitor event logs generated in the system viewer of all Windows devices in your network.|
|Windows Services Monitor||Track the Windows services status by observing application availability and failure detection using service names.|
|Other Monitors||Set up monitoring using various Linux and Windows supported monitors.|
|Agent Custom Monitors||Set thresholds to validate custom monitor availabilty and generate alerts.|
These monitors can be used with modifications.
A custom monitor is a user-defined monitor that enables you enables you to write OpsRamp-supported scripts to expand your monitoring metrics beyond native monitors.
OpsRamp supports two types of custom monitors:
- Agent Custom Monitors
- Agentless Custom Monitors
OpsRamp supports the following types of execution modes:
- BATCH FILE
A monitoring template defines the parameters needed to monitor your target resource. Templates can capture the behavioral and performance metrics of servers, applications, networks, storage, database instances, and more across hybrid and multi-cloud environments.
A monitoring template defines:
- Which data to collect
- How to collect the data
- Data collection frequency
- The type of collector to use to collect the data, such as SNMP or the VMware API
You manually apply a monitoring template to a particular resource or a set of resources of the same type, to standardize monitoring functionality across your organization.
You need the appropriate permission-level to work with templates, depending on your usage requirements. Y can select from the following permission levels:
- Create and Edit
The following template types are supported:
|Global template||Global Templates are default templates that are visible to partners and clients. You can only create copies from a global template and cannot modify them.|
|Partner template||A Partner template is visible only to a specific partner and a partner user is created from scratch. All clients across a partner can access the partner templates./td>|
|Client template||A Client template is visible only to a specific client. You can either create a new client template or copy from an existing global template at the client scope. All client templates are applied to all devices in the client.|
Tracking monitoring resources
After assigning templates to resources, you can track the monitored metrics in the Alerts, Metrics, and Monitors tabs.
When to alert specification
The When to Alert option defines the scenario for receiving alerts and is applicable only to Performance and Application Monitors.
Threshold breach alerting
You can specify warning and critical threshold values for a metric to trigger an alert that indicates a threshold breach of threshold when the threshold value is crossed.
Threshold breach forecast
Forecasting helps you to visualize metric trends over an interval and can alert on a potential breach, such as a disk running out of space within the next five days.
Change detection identifies sudden changes in metric behavior. The change can be in a positive or negative direction. This feature is appropriagte for metrics with undefined thresholds, such as a change in response time performance.
Monitoring integration failures
Events generated from integration failures, both inbound and outbound configurations, can be monitored:
- Alerts are generated when an integration failures occur.
- Metrics are provided to monitor integration failures.
- Templates are available to create and assign to the integration.