Out-of-Box Inbuilt Reports

Overview

Discover the wealth of information available at your fingertips with Motadata AIOps' extensive library of built-in reports. Organized into two main categories - Performance and Availability - and also segmented by infrastructure types such as Network, Server, Process, Service Check, Wireless, and Virtualization, these reports offer valuable insights to optimize your IT environment.

Navigation

Go to Menu, Select Reports .

The Reports screen is displayed.

Reports Screen

Categorisation of Reports

Explore the conveniently and intelligently organized reports on the left-side panel, categorized into the following sections:

Performance Reports

Gain deep insights into your infrastructure's performance metrics, including CPU utilization and network performance, and more to identify bottlenecks, monitor resouce utilization, and make data-driven decisions to optimize your IT infrastructure.

Availability Reports

Ensure the uptime and availability of critical components by tracking downtime incidents and addressing areas that require immediate attention.

Reports based on Infrastructure type

Access reports tailored to your organization's specific monitoring needs, categorized into different infrastructure types including Network, Server, Process, Service Check, Wireless, and Virtualization sections.

Capacity Planning Reports

Capacity Planning reports facilitates the understanding of how much a particular resource is overutilized, underutilized, or is in the Idle state. Motadata AIOps provides insights to CPU utilization, Memory utilization, and Disk utilization that facilitates capacity planning in each of these aspects for a monitor.

Motadata AIOps continously measures CPU utlization, Memory utlization, and Disk utilization that facilitates a deep insight into each aspect of a monitor and in turn allows to take an informed decision for Capacity planning.

Motadata AIOps uses an efficient and in-depth rubrics that determines totale utilization of Memory, Disk, and CPU with respect to time and categorizes monitors accordingly as Idle, Under utilized, or Over utilized. Below is the rubrics that helps with the categorization of the monitors:

Category	Logic	Capacity Planning Implications
Monitors will be considered Overutilized	When CPU Utilization is greater than 90%. When Memory Utilization is greater than 90%. When Disk Utilization is greater than 90%. OR Any of the above conditions exceeding 90% utilization persists for more than 50% of the time duration.	Immediate Action: Investigate and address resource constraints (e.g., increase RAM, upgrade storage, optimize resource allocation). Long-term Planning: Consider upgrading hardware, implementing virtualization technologies, or optimizing applications to improve resource utilization.
Monitors will be considered Underutilized	CPU Utilization is less than 50%. Memory Utilization is less than 50%. Total Disk Utilization is less than 50%. OR Any of the above conditions stay under 50% and it persists for more than 50% of the time duration.	Potential for Optimization: Investigate opportunities to consolidate resources or reallocate underutilized capacity to other systems. Cost Savings: Consider right-sizing resources to reduce energy consumption and operational costs.
Monitors will be considered Idle	CPU Utilization is less than 30%. Memory Utilization is less than 30%. Total Disk Utilization is less than 30%. OR Any of the above conditions stay under 30% and it persists for more than 50% of the time duration..	Potential for Consolidation: Consider consolidating idle resources to improve server utilization and reduce hardware costs. Resource Re-allocation: Investigate opportunities to reallocate resources to other critical systems.

Let's look at an example to understand the above statement clearly:

For instance, an ESXi monitor is present in the underutilized monitor report displaying that 100% of time CPU utilization was less than 50% (refer the screenshot below).

The same monitor is also present under the Idle monitor report diplaying 82% of time the CPU utilization was less than 30% (refer the screenshot below). Let's understand what insight can be extracted from this information.

Since capacity planning reports are always generated for a time period of 1 day, it is known that monitor data we have here is for last 24 hours.

Out of those 24 hours, 100% of the time CPU was underutilized (less than 50%). Which means, for whole 24 hours CPU did not exceed 50% of utilization. And for 82% of the time the CPU was Idle (less than 30%). Which means, for 19.68 hours CPU did not exceed 30% of utilization.

From the above findings, it can be deduced that monitor was utilized for roughly 4.5 hours.

Foreceast Reports

Forecast Reports helps in understanding the future course of Disk, CPU, and Memory utilization. Motadata AIOps uses advances algorithms to predict the utilization of a resource in the future based on its historical data points. Once enough data has been gathered, Motadata AIOps forecasts a timeline that predicts when a particular monitor will breach a particular threshold. Data gathering process will continue for maximum of 90 days.

Motadata AIOps predicts the timeline of your monitor to reach the below thresholds:

Threshold Points
Greater than or equal to 80% utilization.
Greater than or equal to 90% utilization.
Equal to 100% utilization.

Motadata AIOps assigns Forecast conditions to the monitors. These conditions are based upon their current status with respect to the thresholds defined above. Motadata AIOps continuously monitors chunks of data to continuously improve and deliver accurate forecasting of the data. Below aree the Forecast conditions that are assigned by Motadata AIOps:

Forecast Condition	Description
No Growth	There is no considerable growth in utilization, indicating stable usage.
Already Reached	The resource utilization has already reached its maximum capacity.
Insufficient Data	Insufficient data collection period (less than 3 days).

For better understanding, let's take an instance to view the correlation between Thresholds and Forecast conditions.

For instance, a monitor has been added to the system that currently is at 30% utlization. Motadata AIOps will gather data points for a minimum of 3 days to understand the utilization spikes, idle time, and regular load of the monitor. Once the system has enough data points, it will predict a timeline for when the monitor will breach the 80% threshold, 90% threshold, and 100% threshold.

For instance, a monitor has been added to the system that currently and has been monitored for 24 hours. Below-mentioned is its utilization data:

Report Details

You can view the details related to the created reports on this screen as follows:

Field	Description
Name	The name of the report. Click on this report name to view the report.
Description	The description of the what the report shows.
Type	Indicates the type of data displayed (e.g., alert, performance, availability).
Schedule	Use this button to schedule the report to be sent to specific users at a scheduled time.
Download	Use this button to download the report in PDF format.
Actions	Select the button to display the following options: - Clone Report : Select this button to create a report similar to the selected report. - Email This Report : Select this button to send the report as an E-mail.