With increased organizations opting to move their applications to cloud-based environments, there is a fast-growing uptake in the use of datacentre and cloud infrastructure, even as office locations are dispersed, and users work from remote locations. As a result, IT administrators face many challenges in effectively monitoring such infrastructure's availability, performance, and security.
Veryx Cloudmon-ITIM provides a unified visualization of IT infrastructure for health and performance monitoring of servers, VMs, cloud, networks, and remote user devices. Cloudmon-ITIM equips IT and DevOps teams to manage and administer IT infrastructure from a single tool easily and thus ensure that they are fully aware of health and performance.
Cloudmon-ITIM has three components. They are controller, agent, and probe.
Cloudmon-ITIM Controller provides the monitoring console for the IT team and can be installed either in the public cloud or on-premises. It can be accessed using standard web browsers.
In typical installations, the Cloudmon-ITIM Controller gets server and host metrics from Cloudmon-ITIM Agents, which have been installed in servers (Linux and Windows) and hosts. Cloudmon-ITIM may also collect such information by polling SNMP-based servers, hosts, and network devices, where available.
Cloudmon-ITIM Controller gets availability and network quality of service (QoS) metrics from Cloudmon-ITIM probes.
The purpose of this document is to guide users of Cloudmon Controller or Dashboard. It covers both the installation and usage of the controller software.
This User Guide has been designed to enable system administrators to set up Veryx Cloudmon ITIM Controller for monitoring the IT infrastructure by users with the following roles:
Administrator | This role allows you to add, delete, and modify the entire infrastructure monitored in Cloudmon ITIM. This user assigns Operators and infrastructure (devices, IP endpoints, etc.) to Managers. |
Manager | This user role can administer only the infrastructure (devices, IP endpoints, etc.) associated with the user. This user can also assign infrastructure (devices, IP endpoints, etc.) visible to the user to Operators. |
Operator | This user role can only view details, summary, and metrics of the assigned infrastructure (devices, IP endpoints, etc.) |
Veryx Cloudmon ITIM consists of the following components, as described below.
Cloudmon Controller | A central server (cloud or on-premises-based) stores all the metrics and data. It provides a real-time dashboard of servers, networks, and user hosts. It provides alerts, raises alarms, and provides configuration and management capabilities for IT Administrators. |
Cloudmon Probe | Collects availability and performance data, such as delay, delay variation, and loss. It pushes such data periodically to the controller. Probes can be co-located with the controller and placed at other locations within the enterprise network or in branch locations. |
Cloudmon Agent | Collects metrics relating to servers, VMs, and hosts. It pushes them periodically to the controller. Agents are installed on Linux and Windows servers and in user host systems. |
In addition, Cloudmon ITIM Controller uses SNMP to monitor SNMP-capable network switches, servers, and hosts.
Cloudmon ITIM controller deployment on-premises
This figure shows the deployment of Veryx Cloudmon ITIM Controller on-premises with a co-located Cloudmon ITIM probe.
Cloudmon-ITIM monitors physical servers for various parameters relating to the hardware (CPU, memory, disk, etc.) and operating system. Cloudmon-ITIM monitors virtual machines (VMs) in private cloud environments (Linux KVM, VMWare ESXi, and Citrix Xen) and public cloud environments (AWS, Azure, and GCP).
Cloudmon-ITIM monitors network devices in the LAN for health and performance. It also performs WAN IP End-point monitoring for availability and performance.
Cloudmon-ITIM monitors the availability of business-critical applications or other critical resources supporting a high granularity of up to 1 second, thus ensuring that spikes are not missed during the monitoring interval.
Cloudmon-ITIM monitors remote endpoint devices for device hardware and software metrics.
Cloudmon-ITIM does not collect any personal information or 'see' any of the data or information accessed by individual remote endpoint device users.
A few of the unique features of the product include
Noise reduction using intelligent alerts: Many monitoring tools generate alerts, which become cumbersome for IT system administrators to review and remediate. With Cloudmon support for multi-level threshold settings, multiple alarms will not get raised for the same incident or in the same direction within the configured interval.
Automated Incident Remediation: Cloudmon supports an action engine that could be configured with the script for automated remediation.
Synthetic network monitoring: Cloudmon probes performs synthetic (active) monitoring to measure availability and QoS metrics.
High-Frequency monitoring: Cloudmon supports monitoring at a high granularity of up to 1 second for mission-critical resources, thus ensuring that spikes are not missed during the monitoring interval.
IPv4 and IPv6: Cloudmon supports IPv4 and IPv6-based networks and entities.
Support for cloud and on-premises installation: Cloudmon Controller may be installed in the cloud or on-premises server systems.
Cloudmon-ITIM is available in three editions, and the features supported in each edition vary.
| BASIC | STANDARAD | PRO | |
| Yes | Yes | Yes | |
| Yes | Yes | Yes | |
| Yes | Yes | Yes | |
| Yes | Yes | Yes | |
| Yes | Yes | Yes | |
| Yes | Yes | Yes | |
| Yes | Yes | Yes | |
| Yes | Yes | Yes | |
| Yes | Yes | Yes | |
| Yes | Yes | Yes | |
| Yes | Yes | Yes | |
| Yes | Yes | Yes | |
| Limited | Yes | Yes | |
| No | Limited | Yes | |
| Limited | Yes | Yes | |
| No | No | Yes | |
| No | Yes | Yes | |
| 25 | Up to 500 | Above 500 | |
| Yes | Yes | Yes |
Note:
* Limited to a total of 2 endpoints (IaaS or Network links)
* Limited to 10% of licensed nodes (for example, for 100 pack license - can monitor max of 10 endpoints
As businesses grow, network infrastructure grows across physical, virtual and cloud, often are bound to result in complexity and inefficiency. The very mission critical infrastructure that should help businesses realize the benefits of digital transformation and innovation, often plays spoil-sport because of unknown problems lurking on the network and the resulting performance and availability challenges.
With Veryx Cloudmon NTM, enterprise businesses get 100% network visibility and analytics of all traffic across their mission critical infrastructure – whether on-premise or cloud, enabling better control and the realization of the power of digital innovation, at a fraction of the cost of competing solutions.
Cloudmon NTM provides QoS measurements like latency and jitter based on passive monitoring.
100% visibility of end user experiences for application, whether accessed within the enterprise premises, in branch locations or remotely.
Network operations can be proactive and respond quickly resulting in reduced trouble-tickets by 50%
Hop by hop understanding of network performance makes it easy to identify issues and reduce mean time taken to repair (MTTR) by 40%
Further benefits include
Pro-actively eliminates potential failures leading to reduced mean time between failures (MTBF)
Provides IT a holistic view to quickly analyze and remediate problems resulting in improved user experiences
Licensed in pay-as-you-go model, without long-term contracts and hidden fees giving Flexibility and control. Available both for Cloud and on-premises
Monitor End User Experience
Cloudmon Digital Experience Monitoring (DEM) provides network administrators a near real-time visibility of individual users’ applications experience, whether they are working within the office premises or remotely.
In case of performance going below configured thresholds Cloudmon-DEM provides alerts for parameters crossing thresholds and can automatically run configured runbooks to provide immediate remediation.
When needed, network administrators may drill down to specific networks, to determine potential problems or troubleshoot to find the root cause of problems reported.
Troubleshoot Users’ Connectivity Problems
Cloudmon-DEM provides network administrators clear visibility regarding network quality on a hop-by-hop basis from end users’ viewpoint and even identify local connectivity problems in the user’s environment.
Thus, with Cloudmon-DEM network administrators can remotely troubleshoot and easily determine whether the root cause is with the user device, WiFi/LAN, WAN, or the application.
A few additional features of the product include
Chat bot:
- This is a distinctive feature called Chat box which includes Knowledge base, Tickets and Chat.
a) Knowledge Base:
- This includes FAQ, General questions and the basic troubleshooting method which may extend some support to the customer.
b) Tickets:
Click on the option and fill all the required details in the add ticket form and submit it. Ticket will be created and sent to the support team and also you will get to know the ticket number in the popup and you can reach out to the support team for further details.
c) Chat:
- You may get help from our bot, or you can directly chat with our support team regarding your queries.
You can use the credentials that have been sent to your registered mail id to login. After a successful login, you will receive an email with all the necessary details and the link with which you can be redirected to the default admin dashboard.
After successful registration and login, if you wish to create a new account with your own credentials, you can use the sign-up option to do that.
If you forget your password, you have an option to change it. Follow the below steps to change your password.
Step 1: Click on the forgot password.
Step 2: Enter your registered mail ID or username.
Step 3: Enter the verification code that you have received in your email id from noreply.cloudmon@veryxtech.com.
Step 3: Click on the Installation ID and e-mail the copied Installation ID to support@veryxtech.com.
Step 4: Enter the License Key provided by support@veryxtech.com and click on Extend License.
Step 3: Click on the Installation ID and e-mail the copied Installation ID to support@veryxtech.com.
Step 4: Enter the License Key provided by support@veryxtech.com and click on Extend License.
Step 3: Click on the Installation ID and e-mail the copied Installation ID to support@veryxtech.com.
Step 4: Enter the License Key provided by support@veryxtech.com and click on Extend License.
To upgrade Cloudmon components to the latest versions, click on the icon in the top bar right corner of the Cloudmon Controller. Click on the check for updates to check for the latest software updates. Click on the Upgrade button to initiate the upgrade process if updates are available.
Note: Existing configurations will remain undisturbed after the software upgrade.
We have four levels of software upgrade such as major, minor, patch and build upgrade.
Major Upgrade:
A popup with the option to upgrade will be displayed if there is any major upgrade in the cloudmon controller and the other pages of the cloudmon controller will be disabled and the user could access the cloudmon controller only after the upgrade is completed.
Minor Upgrade:
A popup with the option to upgrade will be displayed if there is any minor upgrade in the cloudmon controller and the other pages of the cloudmon controller will be disabled and the user could access the cloudmon controller only after the upgrade is completed.
Patch Upgrade:
A popup with the option to upgrade will be displayed if there is any patch upgrade in the cloudmon controller and they can either upgrade or upgrade it later according to the preference.
Note: User can access the cloudmon portal even though they haven’t updated the controller to the latest patch.
Build Upgrade:
A popup with the option to upgrade will be displayed if there is any build upgrade in the cloudmon controller and they can either upgrade or upgrade it later according to the preference.
Note: User can access the cloudmon portal even though they haven’t updated the controller to the latest build.
Features | Basic | Standard | Pro | Notes |
Physical Server and desktop monitoring | Yes | Yes | Yes | |
VM monitoring | Yes | Yes | Yes | |
Public cloud (AWS, Azure, GCP) instance monitoring | Yes | Yes | Yes | |
Network device monitoring | Yes | Yes | Yes | |
Remote user device monitoring | Yes | Yes | Yes | |
Synthetic Network QoS monitoring (IPv4) | Yes | Yes | Yes | |
Intelligent alerting - noise reduction | Yes | Yes | Yes | |
Email notification | Yes | Yes | Yes | |
Report | Yes | Yes | Yes | |
Network path trace | Yes* | Yes | Yes | |
Process monitoring | Yes* | Yes | Yes | |
Application package details | Yes* | Yes | Yes | Installed software list |
Automated remediation | Yes* | Yes | Yes | Runbook |
MSTeams notification | No | Yes | Yes | |
Slack notification | No | Yes | Yes | |
SMS notification (Twillio) | No | Yes | Yes | |
Zoho Integration | No | Yes | Yes | |
Multi-site (distributed) | No | Yes | Yes | Option to add remote probe |
Custom Dashboard | No | Yes | Yes | |
Custom Webhook integration | No | No | Yes | |
Multi-tenancy (MSP) | No | No | Yes | Option to create manager role |
LDAP/AD Integration | No | No | Yes | |
Docker monitoring | No | No | Yes | |
Synthetic Network QoS monitoring (IPv6) | No | No | Yes | |
Mobile application | No | No | Yes | |
Limits | ||||
Netpath interval (minimum) | 6h | 30m | 1m | |
Polling interval (minimum) | 5m | 1m | 1s | |
Reporting interval (minimum) | 5m | 1m | 1m | |
User accounts (max) | 1 | 5 | 10 | |
Data Retention period | 1w | 2M | 1Y | |
Notes | ||||
* for 30 days |
The Dashboard gives a comprehensive overview of data from various sources. We have Eight dashboards such as Admin dashboard, Alarm dashboard, Alarm triage, NTM Summary, NTM Network, NTM Activity, DEM and Custom. Any of this dashboard can be made as a default dashboard by clicking on the pinned symbol.
The Dashboard gives a comprehensive overview of data from the dashboard provides the overall health status of the devices configured to it. The admin dashboard displays the following information:
The license includes the total number of endpoints, number of endpoints used, total number of probes, the number of probes used, and license expiry date.
Agents - Devices monitored by Cloudmon ITIM using agent-based monitoring is shown here. This includes the number of reporting agents, non-reporting agents, alarmed entities, agents under the Linux platform, and agents under the Windows platform.
Network Devices - Network devices monitored using Cloudmon ITIM agent-less mode is shown here. This includes the number of active devices, inactive devices, alarmed devices, recently booted devices, and devices with critical alarms.
IP Endpoints - This includes the number of active IP Endpoints, inactive IP Endpoints, alarmed IP Endpoints, and IP Endpoints with critical alarms.
Probes - Cloudmon ITIM probe monitors the network endpoints. This includes the number of active and inactive probes.
Users - This includes the number of active, inactive, blocked, and never active users and has the number of users with admin, manager, and operator roles. Note: Operators are not allowed to configure or edit anything.
Map - This shows the geolocation of all the entities available in this Cloudmon ITIM controller.
Infrastructure Snapshot - This includes the summary of all networks, types of devices, OS, CPU, cloud, platform, hypervisors, and users.
On the top right corner, you can see the below icons:
| By clicking on this icon, you can see the alarms categorized as Critical. |
| By clicking on this icon, you can see the alarms categorized as Trouble. |
| By clicking on this icon, you can see the alarms categorized as Attention. |
| This will provide you quick access to search everything configured over here. |
| This will show you the below options.
|
Note: In Navbar -> Dashboard, you can create a new dashboard by clicking on the following icon
The alarm dashboard shows only the alarming devices for troubleshooting. It displays the following information:
Recent alarms - include all the recently raised alarms in detail with their alarm description, device name, device IP, and the alarm raised time. You could find this icon on the top right side of the recent alarms by selecting the required options via drop down; you could categorize the alarms based on their severity.
View Metrics - This will help you get details of current Statistics.
View Process - This will help you to have a look at the process involved.
Export - By clicking on it, you can export the summary page as a PNG file.
E-mail - By clicking on the e-mail icon and entering the mail id, it will send the report to the destination mail id.
Acknowledge Alarm - This will help you acknowledge the alarm directly acknowledges the alarm directly.
Execute Run book - The script for all the issues has been updated in Run book, by clicking on the play button, you can manually run the script based on the issue.
View Network Path - You can see the Network path of the IP Endpoint, by clicking on this.
Add Notes for Reference here - you can add any description in this for reference.
Active alarms by severity - This includes the number of active alarms grouped based on severity such as Critical, Attention, and Trouble.
Active alarms by device type- This includes the number of active alarms grouped based on device type, such as laptop, desktop, server, switch, etc.
Active alarms by metric- This includes the number of active alarms grouped based on a metric such as CPU load, CPU temperature, memory usage, jitter, latency, etc.
Active alarms by group - This includes the number of active alarms grouped based on group or departments such as production, service, finance, HR, etc.
Active alarms by operator - This includes the number of active alarms, which are grouped based on user as operators.
An alarm heat map is a graphical representation of data depicting the values by color and group.
Alarm pending >24 hours - If any raised alarms remain open for more than 24 hours, they will show here.
Alarm triage- This includes all the active alarms, which are grouped based on severity (such as Attention, Critical, and Trouble), metric (such as CPU.load, CPU.temp, mem.usage, etc.), department (such as production, finance, sales, etc.), and metric category (such as CPU, mem, etc.) to make the investigation quite simple.
Alarm trend - This chart includes the open alarm count and closed alarm count on a timely basis.
Active alarms - This shows the total number of active alarms.
Average MTTR - This shows the average time it takes to recover from the defect caused. (MTTR - Mean Time to Recover).
Active alarms by severity - This includes the number of active alarms grouped based on severity such as Critical, Attention, and Trouble.
This shows the Number of sources and number of interfaces associated and further details such as Source Entity, Type, IP, In Utilization, Out Utilization, Traffic In, Traffic Out, Interfaces and the overall Flows.
The Network Dashboard gives a pictorial view of the health of your network. It shows the overview of the speed and time at which bytes and packets are entering and exiting the network.
Cloudmon NTM collector collects the data from the source and pushes this data to the controller. It shows the following details Throughput Rate, Top 10 Applications, Packets Trend, Packets Rate, Packet Count by Protocol and Bytes by Protocol.
By default, the last 15 minute data are shown and can change the time selector to view the last 5 minutes,30 minutes, 1 hour, 12 hours, 24 hours, and 7 days performance. And you can customize the period with the help of Quick selection.
Throughput Rate -> It shows the actual measure of data transmitted in a specific period of the source
Top 10 Applications -> It shows the bandwidth usage of Top 10 Applications of the source with respect to time.
Packets Trend -> It shows the packet flow of the source with respect to time.
Packets Rate -> It shows the packet per second of source with respect to time.
Packet Count by Protocol -> It shows the Packet count with respect to the protocols. Bytes by protocol -> It shows the bandwidth usage of the protocols with respect to time.
It shows the overall activity of the source. It lists the Top Applications, Top Protocols, Endpoints, Top Conversation In and Top Conversations Out of the source.
By default, the last 15 minute data are shown and can change the time selector to view the last 5 minutes,30 minutes, 1 hour, 12 hours, 24 hours, and 7 days performance. And you can customize the period with the help of Quick selection.
On the top right corner of each table, you can see the below icons:
- You can customize the column by clicking on this icon.
- You can filter the data by clicking on this icon.
- You can download the list of the table by clicking on this icon.
- You can have a table view of the device by clicking on this icon.
- You can export the custom data by clicking on this icon.
-You can search for the required data using this option.
Cloudmon Digital Experience Monitoring (DEM) provides network administrators a near real-time visibility of individual users’ applications experience, whether they are working within the office premises or remotely.
In case of performance going below configured thresholds Cloudmon-DEM provides alerts for parameters crossing thresholds and can automatically run configured run books to provide immediate remediation.
When needed, network administrators may drill down to specific networks, to determine potential problems or troubleshoot to find the root cause of problems reported.
Cloudmon-DEM provides network administrators clear visibility regarding network quality on a hop-by-hop basis from end users’ viewpoint and even identify local connectivity problems in the user’s environment.
Thus, with Cloudmon-DEM network administrators can remotely troubleshoot and easily determine whether the root cause is with the user device, Wi-Fi/LAN, WAN, or the application.
DEM Endpoints shows the details such as Active Agents, User Experience Trend chart and User Experience Pie chart. It has both Map and Table View.
It locates the agent based on the locations, and you can navigate by clicking the agent indicated with OS symbol in the Map. It also lists the agents details in table with respect to Application, Location, Countries and Service Providers. You can navigate to corresponding agent by clicking on it.
On the top right corner of each table, you can see the below icons:
- You can customize the column by clicking on this icon.
- You can filter the data by clicking on this icon.
- You can download the list of the table by clicking on this icon.
- You can have a table view of the device by clicking on this icon.
- You can export the custom data by clicking on this icon.
-You can search for the required data using this option.
You can navigate to agent by clicking on the agent in the DEM agent table. It shows the details like Agent name, User experience value, Last seen, User Experience Trend chart and Pictorial representation of user experience value for Endpoint, Wi-Fi/Ethernet, Local Area Network, Internet, and Application.
To know more details of Endpoint,Wi-Fi/Ethernet,Local Area Network,Internet and Application, you can navigate to corresponding tabs.
Endpoint
-> It gives the details such as Device, Operating System,Hardware,Storage and Resource Usage.
-> Resource Usage includes CPU, RAM, and Disk Usage.
-> You can see the Events on the right side which shows the SLA breach and SLA recovery.
Wi-Fi/Ethernet
Internet
-> It shows the User Experience value of the application and its target and has an option to export the details. It also has Availability,Delay,Loss, and Jitter widget.
-> By navigating to each widget, you can view its corresponding chart.
-> It also shows the Traceroute of the target.
Application
-> It shows the User Experience value of the application and its target and has an option to export the details. It also shows the Waiting time,DNS Lookup Handshake,TLS Handshake,Time to Request, Time to First Byte, Time to Download and Total time widget.
-> By navigating to each widget, you can see its corresponding chart.
Custom Dashboard is used to create dashboard of an user’s choice. The user can name the dashboard and select widgets from the drop-down like Top 10 Interfaces by Traffic, Top 10 Interfaces by Percent, Top 10 Devices by CPU Utilization, 10 Devices by Disk Utilization, 10 Devices by Memory Utilization. Also, they can choose the height and width of the widget.
Once the Dashboard is created with the widgets, you can see the list under Created Dashboards. There, you can edit and remove the widgets of the dashboard.
It shows the Bandwidth Distribution, Bandwidth Trend and Top Protocols.
Bandwidth Distribution -> It shows the Bandwidth Distribution of each protocol in pie chart.
Bandwidth Trend -> It shows the bandwidth usage of the protocols with respect to time.
Top Protocols -> It lists the top protocols of the source in the table.
On the top right corner of each table, you can see the below icons:
- You can customize the column by clicking on this icon.
- You can filter the data by clicking on this icon.
- You can download the list of the table by clicking on this icon.
- You can have a table view of the device by clicking on this icon.
- You can export the custom data by clicking on this icon.
-You can search for the required data using this option.
You can deep dive to see more details of each protocol by clicking on the specific protocols to navigate to the protocol page which shows the details such as LAN, WAN, Sessions vs Throughput Rate, list of Endpoints (In)and Endpoints (Out)of the protocol.
It shows the Session Distribution, Bandwidth Distribution and Top Applications.
Bandwidth Distribution -> It shows the Bandwidth Distribution of each application in pie- chart.
Session Distribution-> It shows the Session Distribution of each application in bar chart.
Top Applications -> It lists the top Applications of the source in the table.
On the top right corner of each table, you can see the below icons:
- You can customize the column by clicking on this icon.
- You can filter the data by clicking on this icon.
- You can download the list of the table by clicking on this icon.
- You can have a table view of the device by clicking on this icon.
- You can export the custom data by clicking on this icon.
-You can search for the required data using this option.
You can deep dive to see more details of each Application by clicking on the specific application to navigate to the application page which shows the details such as LAN, WAN, Flows vs Throughput Rate, list of Endpoints (In)and Endpoints (Out)of the application.
It shows the Flow Trend and Logs of the associated source.
Flow Trend-> It shows the bandwidth usage of the flow with respect to timestamp.
Logs -> It lists the Flow id,Server,Client,Protocol,Application and Bandwidth in the table.
By clicking on the Id in the Logs table, you can see the Flow Overview and you can see the respective flow trend chart with respect to client,server,protocol, and applications by clicking on it in the Logs table.
On the top right corner of each table, you can see the below icons:
- You can customize the column by clicking on this icon.
- You can filter the data by clicking on this icon.
- You can download the list of the table by clicking on this icon.
- You can have a table view of the device by clicking on this icon.
- You can export the custom data by clicking on this icon.
-You can search for the required data using this option.
Server monitoring and VM monitoring refer to continuously monitoring the health and performance of computer servers and virtual machines (VMs), respectively.
Servers and VMs form part of the critical IT infrastructure of any organization since business-critical enterprise applications are hosted in them. These may also typically store and process information that needs to be provided to other applications and users on-demand and simultaneously support hundreds or even thousands of requests.
Cloudmon ITIM performs Server and VM monitoring by continuously monitoring hundreds of server parameters relating to server components and VMs, providing alerts when they cross configured thresholds.
Cloudmon ITIM performs monitoring using both agent-based and agent-less modes. In agent-based mode, Cloudmon ITIM relies on Cloudmon ITIM agents installed in the device – either server, VM, or end-user hosts. Cloudmon ITIM requires the device to be monitored to support SNMP for agent-less mode.
Cloudmon ITIM auto-discovers all the servers and VMs where Cloudmon ITIM Agent is installed. Click on the Devices menu to view the discovered devices lists.
On the top right corner of the devices page, you can see the below icon:
- You can customize the column by clicking on this icon.
- You can filter the device list by clicking on this icon.
- You can download the list of devices by clicking on this icon.
- You can have a table view of the device by clicking on this icon.
- You can have the list view of the devices by clicking on this icon.
- You have the heat map view of the devices by clicking on this icon.
- You can export the custom data by clicking on this icon.
-You can search for the required data using this option.
- You can add a device by clicking on this icon.you need to fill the mandatory like Probe, Host name or IP, display name, SNMP credential and Monitoring template.
Also, you can categorize the devices and list them based on the following factors:
All Devices.
Top by CPU Utilization.
Top by Memory Utilization.
Top by Disk Utilization.
Top by Network Utilization.
Device information
From Devices List, click on a specific device with the type 'Virtual Machine' to view the device information and its monitored performance metrics.
Select any VMs to view the device summary. The device summary shows availability timeline, device status, host name, IP, OS, CPU information (core, processor, speed, vendor, model), location, device type, disk space, total memory available, tags, boot time, last seen, number of interfaces, monitoring profile, alarm rule, properties (group, if VM is public cloud instance it has instance-id, AMI, public IP, private IP, security group, region, availability zone).
Click on the Interfaces tab to view the list of available network interfaces of the device. Click on any available network interfaces to view the interface statistics.
Click on the Installed Software tab to view the list of apps installed on the device.
Click on the Process tab to view the list of processes running and top by CPU and memory utilization. This is to show which process utilizes more CPU and memory.
Click on any of the process names in the Processes List to view a specific process's CPU and memory statistics.
If you have installed docker in your machine, you can get the docker info, details of containers, images, and volumes. And, you can see the list of containers that are running as well as exited.
To get the statistics of the running container, click on the container that is running and you could be able to find statistics.
Cloudmon ITIM Agent periodically collects the performance statistics of the server/virtual machine and pushes them to the Cloudmon ITIM Controller at every monitoring interval. Click on the System Metrics tab to view performance statistics. By default, the last 1-hour statistics are shown and can change the time selector to view the performance based on the time you chose. To view all the static and dynamic system metrics of agents refer to Appendix 1.
Note: By clicking on icon you can download a report of the page in PDF.
By default, performance monitoring is enabled for agent-based monitoring devices, as shown by the icon. To enable performance monitoring for any device, navigate Settings > Monitoring > Hosts/agents and under the Actions column, click on the toggle icon.
Disable performance monitoring
Navigate to Settings > Monitoring > Hosts/agents and select the device for which you wish to disable monitoring. Under Actions, click on the toggle icon to disable performance monitoring of the device. This means that performance monitoring is disabled successfully. Upon successful update, the icon changes to show that the device is not being monitored.
To remove a host/agent, navigate Settings > Monitoring > Hosts/agents and select the device to delete. Under Actions, click on the delete icon to remove the device from the Cloudmon ITIM controller.
Modify monitoring profile
By default, the monitoring profile default is configured for every entity. The default profile includes all the metrics for monitoring and can be modified if required. The configuration of monitoring profile steps is discussed in section 11.2.1. The steps to change the profile from default to the user-defined profile are below.
Step 1:
Before modifying the default profile, create a new monitoring profile. Navigate to Settings > Configurations > Monitoring profile and click on the Agents tab.
Step 2:
Click on the new icon to add a new monitoring profile for the device. Configure the required details, then click on the Save button to save the profile.
Step 3:
To change the monitoring profile, navigate Settings > Monitoring > Hosts/agents after disabling performance monitoring for the device.
Step 4:
Under Actions, click on the Edit icon, select the newly created monitoring profile you wish to activate, and click on the Save button to save the configuration. Here profile is changed from default to CPU load, with only the CPU.load metric.
Step 5:
After changing the monitoring profile, enable performance monitoring for the device.
High frequency monitoring can be enabled in PRO version. To enable high frequency, the polling interval should be less than the reporting interval. For example, if polling interval is 10sec and reporting interval in 1min then for every 10 sec data will be polled and reports data as min, max average of every minute. Follow the below steps to enable high frequency,
Step 1:
Navigate to Settings > Configurations > Monitoring profile and click on the Agents tab.Click on the New icon to add a new monitoring profile for the device. Configure the required details like Name, Polling interval, reporting interval and monitors. Then click on the Save button to save the profile.
Note: Here the polling interval should be less than the reporting interval.
Step 2:
Associate this monitoring profile to the devices for which the high frequency monitoring must be enabled.
Alarm rules are set up to trigger actions when entity metrics cross configured threshold values. Cloudmon ITIM alarm rules are powerful since they can be set up so that alarm noise (repeated alarms for the same issue) is drastically reduced.
Follow the steps below to modify alarm rules for a device:
Step 1:
Navigate to Settings > Monitoring > Hosts/Agents and disable performance monitoring for the device.
Step 2:
Click on the Edit icon under Actions, select the alarm rule and click on the Save button.
Step 3:
Enable the performance monitoring of the device.
Navigate to Settings > Monitoring > Hosts/agents and select the device for which you wish to assign users. Under Actions, click on the edit button, then add the users listed in the Assigned to option.
Note: If the assigned user role is operator, they can only view the device assigned to them.
Cloudmon ITIM Probe is the component that helps perform IP Endpoint availability monitoring. Initially, if the probe is not yet set up, follow the below steps to add a Probe.
Step 1:
Navigate to settings > Monitoring > probes, and click on the New icon to configure the probe.
Step 2:
Configure Name and hostname/IP (supported format IPv4/IPv6/domain name) and click on the Save button to add the probe.
Note : You can update the collector by clicking on this icon.
For the selected Cloudmon ITIM Probe, click on the Edit icon under Actions and navigate to Network Devices tab. Click on the New icon to configure the network device .
After configuring the required details like Display Name, Hostname or IP,SNMP Credential,Monitoring Template and Tags. click on the Save button to add the network device.
To view the list of network devices, navigate to Devices > All Devices in the menu bar.
Click on the Interfaces tab to view the list of available network interfaces of the device. Click on any available network interfaces to view the interface statistics.
You can enable interface monitoring for a specific interface by doing the following: Enable monitoring status of the specific interface by clicking on the following icon , and your interface will be monitored from then on.
When monitoring is enabled, an alarm should be triggered if an interface is down, and an email with interface alarm details should be sent to an user assigned to the device.
Click on the Installed Software tab to view the list of apps installed on the device. Software are shown for server based network devices.
Using SNMP, Cloudmon ITIM periodically collects information regarding the process running in the network device. Processes are shown for server based network devices. Click on the Process tab to view the list of processes sorted by CPU utilization.
Click on any of the processes to view the CPU utilization of a specific process.
Using SNMP, Cloudmon ITIM periodically collects the performance statistics of the network device. Click on the System Metrics tab to view performance statistics. By default, the last 1-hour statistics are shown and can change the period to view the last 2-hour, 1-day, 2-day, 1-week, 2-week, and 4-week performance. To view all the static and dynamic system metrics of network devices refer to Appendix 2.
By default, network performance monitoring is automatically enabled when new network devices are added. If network performance monitoring is not enabled, click on thetoggle icon to enable it.
Navigate to Settings > Monitoring > Probes, click on the Edit icon, and click on the Network Devices tab. Under Actions, click on thetoggle icon to disable performance monitoring of the Endpoint. Once the toggle icon is de-selected, performance monitoring is stopped.
Navigate to Settings > Monitoring > Probes and click on the Edit icon to delete network devices. Then click on the Network Devices tab. Under Actions, click on the Delete icon to delete the network device from Cloudmon ITIM.
Alarm rules are configured to set triggers for threshold values crossing specified ranges.
Follow the steps below to configure an alarm rule:
Step 1:[Text Wrapping Break]Navigate to Settings > Configurations > Alarm rules in the Devices tab and click on the new icon to add an alarm rule.
Step 2:
A dialog box to configure the alarm rule will appear.
Configure the required information - Name, devices, notify to, and a run book. Select the required devices to which must assign an alarm rule.
An alarm action is to initiate remediation steps automatically when a device metric crosses the configured threshold value. Cloudmon ITIM supports the inclusion of automated scripts executed from its action engine when thresholds are crossed. Supported language interpreters are node, python, and shell script.
Step 3:
Click on a dialog box to add a trigger that will appear.
The threshold types are defined to categorize the severity of the alarm. shows to trigger of an alarm when the given metric value is above the 90% threshold and a critical alarm is triggered. A trouble alarm is triggered if its value is above the 60% threshold. An attention alarm is triggered if its value is above the 30% threshold. If its value is less than equal to the 5% threshold, the device is in a normal/clear state.
Step 4:
Click on the OK button to save the added trigger. After adding the list of triggers, click on the Save button to add the alarm rule configured.
Navigate to Settings > configurations > Alarm rules and click on the Devices tab. Under the Actions column, click on the Edit icon a dialog box to edit the alarm rule will appear. Can modify the rule based on the need.
Step 1:
Navigate to Devices > All Devices. Select the network device for which you want to assign the users.
Step 2:
Navigate to the Settings tab of the device, Under Assigned To add the users so that the assigned users can view the device for monitoring.
Note: If the assigned user role is operator, they can only view the device assigned to them.
Cloudmon ITIM Probe must perform IP Endpoint availability monitoring and network monitoring.
For the selected Cloudmon ITIM probe, click on the Edit icon under Actions, then navigate to the IP endpoints tab.
Click on the New icon to configure the service.
Note: IPv6 endpoints are supported only in Cloudmon ITIM Pro edition. If you want to monitor IPv6 endpoints, upgrade the Cloudmon ITIM license to Pro edition with the assistance of the Veryx support team.
Configure the required details like Name, Host name/IP, IP version as IPv4 or IPv6, and Packet type as ICMP/TCP. If TCP is selected, configure the destination port, and click on the Save button to add the IP endpoint service.
Note: IPv6 version is supported for the Pro version only.
Once an IP endpoint is added, Cloudmon ITIM monitors the connection status, diagnostic trace path, and QoS metrics.
To view the list of IP Endpoints and corresponding status information, navigate to IP Endpoints> All IP Endpoints in the menu bar.
On the top right corner of the IP Endpoints page, you can see the below icon:
- By clicking this icon, you can see the topology view. It shows how the IP endpoints are connected to the probe. By hovering over the IP endpoint, you can summarize the IP endpoint and show the medium via which it has been connected (TCP\ICMP). If the flow has been marked in Dotted lines, it denotes the loss.
- By clicking on this, you can see how the IP endpoint is connected automatically to the probe based on the location.
- You can customize the column by clicking on this icon.
- You can filter the IP Endpoints list by clicking on this icon.
- You can download the list of IP Endpoints by clicking on this icon.
- You can have the list view of the IP Endpoints by clicking on this icon.
- You have the heat map view of the IP Endpoints by clicking on this icon.
- You can export the custom data by clicking on this icon.
- You can search any required data with the help of this icon.
- you can add a IP Endpoint by clicking on this icon.you need to fill the mandatory like Probe, Name, Hostname or IP and Packet type.
Also, you can categorize the IP Endpoints and list them based on the following factors:
All IP Endpoints.
Top by Loss.
Top by Latency.
Top by Jitter.
To view the summary status of any IP Endpoint, click on its Name. The summary gives basic information about the IP endpoint, such as its Name, host name, status, last seen, alarm status, alarms, monitoring profile, probe (to know in which probe this service is configured), users, and its current time statistics.
By default, availability monitoring is enabled when an endpoint is added. If availability monitoring is not enabled for an IP Endpoint, click on the toggle icon to enable availability monitoring.
Navigate to Settings > Monitoring > Probes, click on the Edit icon and select the IP Endpoints tab. Under Actions, click on thetoggle icon to disable availability monitoring of the Endpoint. Once disabled, the toggle icon will appear de-selected, indicating that availability monitoring of the Endpoint has been stopped.
If you no longer want to monitor an IP endpoint, you may disable or delete the IP endpoint from Cloudmon ITIM.
To delete an IP endpoint, navigate Settings > Monitoring > Probes, click on the edit icon, and click on the IP endpoints tab. Under Actions, click on thedelete icon to delete Cloudmon ITIM.
Follow the steps below to modify the monitoring profile of an IP Endpoint.
Step 1:
Create a monitoring profile for IP endpoints.
Step 2:
Navigate to IP Endpoints> All IP Endpoints. Select the Endpoint for which you want to modify the profile.
Step 3:
Navigate to the Settings tab of that IP endpoint; you should disable the availability monitoring before updating the profile.
Step 4:
Now modify the default monitoring profile and click on the save button.
Step 5:
On successful update, enable availability monitoring.
High frequency monitoring can be enabled in PRO version. To enable high frequency, the polling interval should be less than the reporting interval. For example, if polling interval is 10sec and reporting interval in 1min then for every 10 sec data will be polled and reports data as min, max average of every minute. Follow the below steps to enable high frequency,
Step 1:
Navigate to Settings > Configurations > Monitoring profile and click on the IP Endpoints tab. Click on the New icon to add a new monitoring profile for the device. Configure the required details like Name, Polling interval, reporting interval,trace path interval,DSCP and monitors. Then click on the Save button to save the profile.
Note: Here the polling interval should be less than the reporting interval.
Step 2:
Associate this monitoring profile to the IP endpoints for which the high frequency monitoring must be enabled.To modify the monitoring profile for an IP endpoint.
Alarm rules are set up to trigger actions when entity metrics cross configured threshold values. Cloudmon ITIM alarm rules are powerful since they can be set up so that alarm noise (repeated alarms for the same issue) is drastically reduced.
To configure an alarm rule for the IP endpoint.
Navigate to Settings > configurations > Alarm rules and click on the IP Endpoints tab. Under Actions, click on the Edit icon a dialog box to edit the alarm rule will appear. Can modify the rule based on the need.
Step 1:
Navigate to IP Endpoints> All IP Endpoints. Select the IP endpoint for which you want to assign the users.
Step 2:
Navigate to the Settings tab of the device, Under Assigned to add the users so that the assigned users can view the IP endpoints for monitoring.
Note: If the assigned user role is operator, they can only view the IP endpoints assigned to them.
To view the active alarms, navigate to Alarms > Active Alarms. Click on the entity to view the device information.
To view all active and inactive alarms raised for an entity, navigate to Alarms > All Alarms. Click on the entity to view the device information.
By Clicking on the icon, you can categorize the alarms based on ID, Entity, Host name, IP, Message, Triggered on.
The events dashboard provides a record of all the actions performed in the controller. It is categorized based on the event level, such as info, debug, warning, and error. To view the list of events, navigate to Events. You can also change the period you want the view by selecting the appropriate period on the top right .
On the top right corner, you can see the filter icon via which you can filter the events based on Devices, IPs, Levels, and Categories.
Also, we can fetch the events of each device with the below path,
Device -> All Devices -> Click on to the device -> Events.
To generate the report, navigate to Reports > ITIM and click the New icon; provide the required details such as Name, template, frequency (hourly, daily, monthly, weekly), notify to (pre-requisite configure notification with service as e-mail), and click on the Save button to add report configurations .
To edit the configured report, click on the Edit icon under Actions.
To delete the configured report, click on the Delete icon under Actions.
To send the report to notifiers, click on Send icon under Actions.
To view the generated report in pdf format, click on the Pdf icon under Actions .
You will receive a report with top 50 on the list in a pdf format.
In the top right corner, you can see Generate Report button. By clicking on it, an overlay appears in which the fields like report name, report from and to, entity type device or IP endpoints must be filled. If you select device as entity type, then choose the devices and metrics from the dropdown which has CPU, Memory, Disk, Interface to generate a report. If you select IP endpoints as entity type, then select IP endpoints and metrics from the dropdown which has Jitter, Latency, Loss to generate a report. After entering of all fields, click “Generate” button to generate your custom report. Also you can reset the form by clicking “Reset” button and “Close” to close the form.
To generate the report, navigate to Reports > NTM and click the New icon; provide the required details such as Name,status, template, filter,schedule,, notification (pre-requisite configure notification with service as e-mail) and click on the Save button to add report configurations
ITIM
To configure the Cloudmon ITIM controller hostname/IP, navigate to Settings > General Settings > Controller>ITIM. By default, the controller hostname/IP is configured but click on the edit button if you need to change the IP address.
NTM
To configure the Cloudmon ITIM controller hostname/IP, navigate to Settings > General Settings > Controller>NTM. By default, the controller hostname/IP is configured but click on the edit button if you need to change the IP address.
Navigate to Settings > General Settings > Mail Server to configure the mail server. Specify the required details such as hostname, port (587 - SMTP), from address, enable secure only if the given address is secured, enable auth, and email-id will be automatically configured as noreply.cloudmon@veryxtech.com and its password will also be configured automatically.
Click on the Edit button to update any of the configurations. Click on the Test Mail button to send a test mail from the configured Cloudmon ITIM server. Provide the destination mail address and click the Send button.
An LDAP integration allows your Cloudmon instance to use your existing LDAP server as the primary source of user data.
Port: Port 389 has historically been used for unencrypted connections to an LDAP server.
Port 636 is used for legacy SSL connections.
Host Name: This is the server address or name where the Active Directory service is running.
Base DN: The Base DN is the starting point an LDAP server uses when searching for user's authentication within your Directory. Example: DC=example-domain, DC=com.
AD Domain: LDAP provides a means to manage user and group membership stored in Active Directory. LDAP is a protocol to authenticate and authorize granular access to IT resources, while Active Directory is a database of user and group information.
Administrators group: The set of user and group accounts that Dynamo creates during account initialization depends on the application modules included in your application.
Filters: The filter should contain information about which object class the group entries have. We can narrow down the users based on the filters.
LDAP Attributes Mapping: Map the username, first name, last name, and Email field.
You can integrate LDAP by navigating to General Settings -> LDAP Integration and fill the required details and save it
Click on the Edit button to update any of the field in SMS Integration. Click on the Test SMS button to send a test SMS from the configured number. Provide the Recipient phone number and click the Send button.
Cloudmon ITIM incident notification feature supports sending incident notifications by messaging (e-mail, teams, SMS) and ITSM /trouble-ticketing tools (Slack, Zoho Desk). If an e-mail service is required, provide the mail address to which notification must be sent, or else provide the hook URL of its service.
To configure the notification, navigate to Settings > General Settings > Notification. Specify the required details such as Name, and select either e-mail, URL, Zoho Desk or SMS service service.
To edit the configured notifications, click on the Edit icon under Actions. To delete a configured notification, click on the Delete icon under Actions.
This feature aims to initiate remediation steps automatically when a device metric crosses the configured threshold value. Cloudmon ITIM supports the inclusion of automated scripts that can be executed from its action engine when thresholds are crossed. Supported language interpreters are node, python, and shell script. This configured action must be added while configuring the alarm rule.
To configure remediation action, navigate to Settings > General Settings > Runbook. Configure the required details such as Name, select language interpreter, script file, and click on the Save button to save the configuration.
To Edit the configured action, click on the Edit icon under Actions. Click on the delete icon under Actions to delete the action.
A certificate signing request (CSR) is one of the first steps toward getting your SSL/TLS certificate. Generated on the same server, you plan to install the certificate. The CSR contains information (e.g., common name, organization, country) that the Certificate Authority (CA) will use to create your certificate.
To generate security settings, navigate to Settings > General Settings > Security and click on Generate, providing the required information. And have other options like self-signed certificate and import certificate as a Security option.
If you select self-signed certificate option, click on the ‘create’ button. A digital certificate not signed by any publicly trusted Certificate Authority (CA) will be applied to your controller.
The Import Certificate option is to upload the valid certificate (.crt file) signed by any publicly trusted CA
Cloudmon ITIM supports the following three types of account roles:
An administrator is a super-user and has all privileges to add/edit/delete entities.
The manager has privileges to add/edit/delete entities.
The operator has only view privileges for the assigned. Add/edit/delete actions are not possible.
Go to Settings > General Settings > User Accounts, to add new user accounts. Click on the New icon, provide the required details like Name, role, email, username, and password, and check the blocked field to block the user; if UI Notification is enabled for the user, any action performed by the user will be notified, and click on the Save button.
The generated logs of all the components like the agent, server, collector, probe-agent, Nginx, and probe are available under Settings > General Settings > System Logs.
Step 1:
To create a new monitoring profile for devices, navigate Settings > Configurations > Monitoring profile and click on the Agents tab.
Step 2:
Click on the New icon and provide the required information - Name, interval (by default, both polling and reporting interval is 60sec), and list of monitors and click on the Save button.
Note: Polling interval can be changed by the user only when the controller is in the Pro version
To Edit the configured profile, click on the Edit icon under Actions. To Delete the profile, click on the Delete icon under Actions.
Step 1:
To create a monitoring profile for IP Endpoints, navigate Settings > Configurations > Monitoring profile and click on the IP endpoints tab.
Step 2:
Click on the New icon and provide the required information - Name, interval (by default, both polling and reporting interval is 60sec), and list of monitors and click on the Save button.
Note: Polling interval can be changed by the user only when the controller is in the Pro version
To Edit the configured profile, click on the Edit icon under Actions. To Delete the profile, click on the Delete icon under Actions.
Step 1:
To create a monitoring profile for IP Endpoints, navigate Settings > Configurations > Monitoring profile and click on the Network Devices tab.
Step 2:
Click on the New icon and provide the required information - Name, Reporting interval and add monitors and click on the Save button.
Click on the Add Monitors button and fill the required details like SNMP OID,Name,Unit to add monitoring profiles.
To Edit the configured profile, click on the Edit icon under Actions. To Delete the profile, click on the Delete icon under Actions.
To configure SNMP support in Cloudmon ITIM, navigate Settings > Configurations > SNMP credential and click on the New icon to provide the required details such as Name, SNMP version, and click on Save to add SNMP. If SNMP version v3 is selected, provide a username, protocol password, and privacy password. Supported protocols are MD5 and SHA. Supported encryptions are AES128 and DES.
To edit the configured SNMP, click on the Edit icon under Actions. To delete SNMP configuration click on the Delete icon under Actions.
Alarm rules are set up to trigger actions when entity metrics cross configured threshold values. Cloudmon ITIM alarm rules are powerful since they can be set up so that alarm noise (repeated alarms for the same issue) is drastically reduced.
Follow the below-given steps to configure the alarm rule:
Step 1:
Navigate to Settings > Configurations > Alarm rules in the Devices tab and click on the new icon to add an alarm rule.
Step 2:
A dialog box to configure the alarm rule will appear. configure the required information - Name, devices, notify_to, and Run book. Select the required devices to which must assign an alarm rule. Notify_to and Run book can be configured in Settings > General settings.
Runbook is to initiate remediation steps automatically when a device metric crosses the configured threshold value. Cloudmon ITIM supports the inclusion of automated scripts executed from its action engine when thresholds are crossed. Supported language interpreters are node, python, and shell script.
Step 3:
Click on a dialog box will appear to add a trigger.
The threshold types are defined to categorize the severity of the alarm. shows to trigger an alarm when the given metric value is above the 90% threshold; a critical alarm is triggered. A trouble alarm is triggered if its value is above the 60% threshold. An attention alarm is triggered if its value is above the 30% threshold. If its value is less than equal to the 5% threshold, the device is in an intermediate/clear state.
Step 4:
Click on the OK button to save the added trigger. After adding the list of triggers, click on the Save button to add the alarm rule configured.
To edit the configured alarm rule, click on the Edit icon under Actions. To delete an alarm rule, click on the Delete icon under Actions.
Alarm rules are set up to trigger actions when entity metrics cross configured threshold values. Cloudmon ITIM alarm rules are powerful since they can be set up so that alarm noise (repeated alarms for the same issue) is drastically reduced.
Follow the steps given below to configure an alarm rule:
Step 1:
Navigate to Settings > Configurations > Alarm rules in the IP Endpoints tab and click on the New icon to add an alarm rule.
Step 2:
A dialog box to configure the alarm rule will appear.
From , configure the required information - Name, endpoints, notify, and a run book. Select the required devices to which must assign an alarm rule.
Step 3:
Click on a dialog box will appear to add triggers.
The threshold types are defined to categorize the severity of the alarm.shows to trigger an alarm when the given metric value is above the 50ms threshold, a critical alarm is triggered. A trouble alarm is triggered if its value is above the 35ms threshold. An attention alarm is triggered if its value is above the 20ms threshold. If its value is less than equal to the 5ms threshold, the device is in a normal/clear state.
Step 4:
Click on the OK button to save each trigger.
After adding the list of triggers, click on the Save button to add the alarm rule configured.
Navigate to Settings > Configuration > DEM Profile page which consists of Agent Mapping, Profile Mapping, Endpoint SLA, Wi-Fi/Ethernet SLA, Local Area Network SLA, Internet/Application SLA.
Agent mapping can be mapped by navigating to Settings > Configuration > DEM Profile> Agent Mapping. Click to edit the configured agent and to delete the configured agent. While editing provide fields like Name, Description, Profile, Asset.Click save, reset, and close button to perform the required operations. Click to add profile for which more information is available in profile mapping section
Profile Mapping
Profile mapping can be mapped by navigating to Settings> Profile> Profile Mapping. Click icon to view the mapped profiles. You can view the fields like Name, Endpoint, Wi-Fi/Ethernet, Local Area Network, Internet/Application, Notification fields. You can close the form by clicking close button. Click icon to delete the mapped profile.
On the top right corner of each table, you can see the below icons:
- You can customize the column by clicking on this icon.
- You can filter the data of the by clicking on this icon.
- You can download the list of the table by clicking on this icon.
- You can have a table view of the device by clicking on this icon.
- You can export the custom data by clicking on this icon.
- You can search the required data using this icon.
Endpoint Service Level Agreement shows Name and Signal Strength which is categorized as Good, Bad and Trouble.
You can view then by clicking icon to view the endpoint SLA. Click icon to delete the endpoint. You can close the form by clicking close button.
On the top right corner of each table, you can see the below icons:
- You can customize the column by clicking on this icon.
- You can filter the data of the by clicking on this icon.
- You can download the list of the table by clicking on this icon.
- You can have a table view of the device by clicking on this icon.
- You can export the custom data by clicking on this icon.
- You can search the required data using this icon.
Wi-Fi/ Ethernet SLA
Wi-Fi/Ethernet Service Level Agreement shows Name, CPU, RAM, Disk level of usage which is categorized as Good, Bad and Trouble.
You can view then by clicking icon to view the Wi-Fi/Ethernet SLA. Click icon to delete the endpoint. You can close the form by clicking close button.
On the top right corner of each table, you can see the below icons:
- You can customize the column by clicking on this icon.
- You can filter the data of the by clicking on this icon.
- You can download the list of the table by clicking on this icon.
- You can have a table view of the device by clicking on this icon.
- You can export the custom data by clicking on this icon.
- You can search the required data using this icon.
Local Area Network SLA
Local Area Network Service Level Agreement shows Name,Delay, Jitter, Loss level of usage which is categorized as Good, Bad and Trouble.
You can view then by clicking icon to view the Local Area Network SLA. Click icon to delete the endpoint. You can close the form by clicking close button.
On the top right corner of each table, you can see the below icons:
- You can customize the column by clicking on this icon.
- You can filter the data of the by clicking on this icon.
- You can download the list of the table by clicking on this icon.
- You can have a table view of the device by clicking on this icon.
- You can export the custom data by clicking on this icon.
- You can search the required data using this icon.
Internet/Application SLA
Internet/Application SLA shows Name,Hostname/IP, Delay, Jitter, Loss level of usage which is categorized as Good, Bad and Trouble and Total time.
You can view then by clicking icon to view the Local Area Network SLA. Click icon to delete the endpoint. You can close the form by clicking close button.
On the top right corner of each table, you can see the below icons:
- You can customize the column by clicking on this icon.
- You can filter the data of the by clicking on this icon.
- You can download the list of the table by clicking on this icon.
- You can have a table view of the device by clicking on this icon.
- You can export the custom data by clicking on this icon.
- You can search the required data using this icon.
Go to Monitoring>Probes,You can add and edit probe details in this section. Once the probe has been added,Network devices and IP Endpoints can be added to that probe.
Go to Monitoring>Hosts/Agents,You can enable or disable the monitoring of the hosts/agents added.
You can see the list of Flow Exporter that have configured already. You can configure Flow Exporter by navigating by Settings -> Monitoring -> Flow Exporter. Select the type of data sources like Flow Analyzer, Netflow, Ipfix you wish to configure.
If Netflow is selected, then provide required details such as Name, IP, Version, Timeout, Retries and Port Number. If V1 or V2C is chosen, provide community string, or V3 is chosen, provide Username, Authentication Password and Privacy Password. Supported protocols are MD5 and SHA. Supported encryptions are AES128 and DES.
Similarly, if flow exporter type IPfix is selected, then provide required details as mentioned above for Netflow selection.
Once the configuration has been done, you can synchronize it using sync button. At the bottom, you can find Close, Reset, Save button to perform the required operations.
S. No. | Issue | Solution |
1 | Unable to install Cloudmon controller | Verify whether the setup satisfies Cloudmon controller system requirements. For more details, check the log /var/log/cloudmon-install-yyyy-mm-dd_hh-mm-ss.log |
# | Metric | Description | Unit | Example |
1 | timestamp | Timestamp when the statistics were recorded | seconds | 1640190227 |
2 | uuid | Device uuid | string | ec20a4b2-093d-a2d5-f8cc-c6852433c830 |
3 | version | Cloudmon ITIM Agent version | string | 1.7.0-2 |
4 | hostname | Device name | string | localhost.localdomain |
5 | boottime | Device's last boottime | seconds | 1625489595 |
6 | location | Device location | string | Mumbai, Maharashtra, India |
7 | ip | Device ip address | string | 10.1.4.229 |
8 | type | Device type | string | Virtual Machine |
9 | network | Network ip address | string | 10.1.4.0/24 |
10 | mon_type | Device monitoring type | string | agent |
11 | vendor | vendor | string | Dell |
12 | system.model | system model | string | HVM domU |
13 | system.version | system version | string | 4.2.amazon |
14 | system.serial | system serial number | string | ec20a4b2-093d-a2d5-f8cc-c6852433c830 |
15 | os.arch | Operating system processor | string | x86 |
16 | os.codename | Name of operating system, while it is in development | string | core |
17 | os.kernel | Kernel is the vital component of an os manages operations of system and hardware | string | 3.10.0-1062.12.1.el7.x86_64 |
18 | os.distro | Distribution of operating system | string | Windows 10 Pro Edition |
19 | os.platform | Platform of operating system | string | Linux |
20 | os.release | OS version | string | 7.6 |
21 | cpu.load | CPU load average | % | 51.6 |
22 | cpu.user | Time spent in running un-niced user processes | % | 37.98 |
23 | cpu.sys | Time spent in running kernel processes | % | 13.64 |
24 | cpu.nice | Time spent in running niced user processes | % | 0 |
25 | cpu.idle | Time spent in the kernel idle handler | % | 48.39 |
26 | cpu.irq | CPU interrupts | % | 0.01 |
27 | cpu.temp | CPU temperature | Degree celcius | 30 |
28 | mem.usage | Total memory usage | % | 41.56 |
29 | mem.buffcache | Memory buffcache | B | 1564131328 |
30 | mem.swap | Memory swap | B | 1310720 |
31 | fs.name | File system name | string | /dev/mapper/centos-root |
32 | fs.usage | File system usage | % | 39.52 |
33 | fs.rbps | Rate at which filesystem read operation is done | bps | 13540.23 |
34 | fs.wpbs | Rate at which filesystem write operation is done | bps | 115540.69 |
35 | disk.rops | Number of disk read requests per second | Requests per sec | 3.12 |
36 | disk.wops | Number of disk write requests per second | Requests per sec | 5.23 |
37 | iface.name | Interface name | string | enp5s5f0 |
38 | iface.speed | Interface current speed | bps | 1000000000 |
39 | iface.operstate | Operational status of the interface | string | up |
40 | iface.tx_bps | Number of bits transmitted by the interface per second | bps | 12085.74 |
41 | iface.rx_bps | Number of bits received by the interface per second | bps | 1522.91 |
42 | iface.tx_discards | Number of packets discarded by the transmitted interface | count | 0 |
43 | iface.rx_discards | Number of packets discarded by the received interface | count | 5356 |
44 | iface.tx_errors | Number of errors at the transmitting interface
| count | 0 |
45 | iface.rx_errors | Number of errors at receiving interface | count | 5356 |
46 | process.id | Id of the process | integer | 1 |
47 | process.name | Name of the process | string | mongod |
48 | process.ppid | Parent id of the process | integer | 8932 |
49 | process.path | Running path of the process | string | /usr/bin |
50 | process.started | start time of the process | seconds | 1639551133 |
51 | process.params | Process params | string | -f /etc/mongod.conf |
52 | process.command | Command of the process | string | mongod |
53 | process.state | state of the process | string | sleeping |
54 | process.cpu | CPU utilized by the process | % | 3.4 |
55 | process.mem | Memory utilized by the process | % | 15.66 |
56 | properties.virtual_host | Type of virtual host | string | Xen |
57 | properties.public_ip | Public ip address of public cloud instance | string | 13.127.3.90 |
58 | properties.private_ip | Private ip address of public cloud instance | string | 10.1.4.229 |
59 | properties.image_id | AMI of public cloud instance | string | ami-026f33d38b6410e30 |
60 | properties.instance_type | AMI of public cloud instance | string | t2.medium |
61 | properties.availability_zone | Availability zone of public cloud instance | string | ap-south-1a |
62 | properties.region | Region of public cloud instance | string | ap-south-1 |
63 | properties.security_groups | Security group to control incoming and outgoing traffic of public cloud instance | string | launch-wizard-2 |
# | Metric | Description | Unit |
1 | timestamp | Timestamp when the statistics was recorded | seconds |
2 | ip | Device IP address | string |
3 | hostname | Device hostname | string |
4 | boottime | Device’s last boottime | seconds |
5 | vendor | Vendor of the device | string |
6 | cpu.load | CPU usage of the device | % |
7 | iface.name | Interface name | string |
8 | iface.speed | Interface current speed | bps |
9 | iface.operstate | Operational status of the interface | string |
10 | iface.tx_bytes | Network TX bytes | B |
11 | iface.rx_bytes | Network RX bytes | B |
12 | iface.tx_discards | Number of packets discarded by the transmitted interface | count |
13 | iface.rx_discards | Number of packets discarded by the received interface | count |
14 | iface.tx_errors | Number of errors at the transmitting interface | count |
15 | iface.rx_errors | Number of errors at receiving interface | count |
16 | iface.tx_unicast | Network TX unicast pkts | count |
17 | iface.rx_unicast | Network RX unicast pkts | count |
Probe is the agent for availability monitoring. It actively monitoring for network link availability statistics of Ip endpoint and pushes them to Cloudmon Collector.Probe collects the following metrics
# | Metric | Description | Unit | Example |
1 | timestamp | Timestamp when the statistics was recorded | seconds | 1640190227 |
2 | mon_id | Monitoring ID for monitoring the asset link | string | 1 |
3 | latency | Latency faced by the asset link | ms | 123.45 |
4 | jitter | Jitter faced by the asset link | ms | 3.2 |
5 | loss | Loss faced by the asset link | % | 0 |