7 / 30 Reports


The 7/30 Reports is available for various attributes/resource of a particular monitor. The 7/30 reports, apart from displaying availability for the past 7 days or 30 days, they also display the following reports for each attribute/resource. These reports can be exported into PDF formats.

History Report

History Report in Applications Manager provides detailed history of the particular attribute of a monitor. You can also generate history trend across business hours for a particular attribute. This provides you with an understanding to the amount of resources that has been utilized by the particular attribute over a period of time (week/month/year).

Archiving: All the data are archived and stored every one hour. Eg. Data from 10 AM to 11 AM are archived and marked as 11 AM when stored. If the monitor instance is completely down during the archiving interval of one hour, archiving will not take place for that hour.

Minimum value: It represents the lowest value from the collected values in an hour. Eg. 6 on Sep 01, 2008 - 14:00 hours represents the lowest value '6' collected on Sep 01, 2008 between 13:00 and 14:00 hours.

Maximum value: It represents the highest value from the collected values in an hour. Eg. 12 on Sep 01, 2008 - 14:00 hours represents the highest value '12' collected on Sep 01, 2008 between 13:00 and 14:00 hours.

Hourly Average: It represents the average value from the collected values in an hour. Eg. 9 on Sep 01, 2008 - 14:00 hours represents the average value '9' collected on Sep 01, 2008 between 13:00 and 14:00 hours.

Top

Hour of Day Report

A sample Hour of Day Report is shown below. This report generates hour's average for a particular time period (week/month/year) for the particular attribute. For example, if you have selected last 7 days data, the report generates hour's minimum, maximum and hourly average. This report helps you visualize the various bottlenecks that appear for this attribute / resource during a particular time period. This allows you to plan future impact of bottleneck on this attribute / resource.

Minimum value: It represents the lowest value among the collected values in a particular hour of the day over a period of time. Eg. The lowest value '41' represents the data collected between 13:00 - 14:00 hours from Dec 4, 2008 3:55 PM to Dec 11, 2008 3:55 PM.

Maximum value: It represents the highest value among the collected values in a particular hour of the day over a period of time. Eg. The highest value '81' represents the data collected between 13:00 - 14:00 hours from Dec 4, 2008 3:55 PM to Dec 11, 2008 3:55 PM.

Hourly Average: It represents the average value of the collected values in a particular hour of the day over a period of time. Eg. The average value '62' represents the data collected between 13:00 - 14:00 hours from Dec 4, 2008 3:55 PM to Dec 11, 2008 3:55 PM.

Top

Day of Week Report

A sample of Day of Week Report is shown below. This report generates average of a day for a particular time period (week/month/year) for the particular attribute. For example, if you have selected last 7 days data, the report generates everyday's minimum, maximum and hourly average and is shown below in this report. As shown in the graph below, the connection time for Oracle DB server has been highest for Wednesday and lowest for Monday. This implies that the traffic on Wednesday has been high when compared to rest of the days during the week. This would allow you to ensure that the connection time of Oracle DB server remains low for that particular day and help you troubleshoot performance issue quickly.

Minimum value: It represents the lowest value among the collected values in a particular day of the week over a period of time. Eg. The lowest value '41' represents the data collected on Wednesdays from Nov 11, 2008 3:55 PM to Dec 11, 2008 3:55 PM.

Maximum value: It represents the highest value among the collected values in a particular day of the week over a period of time. Eg. The highest value '81' represents the data collected on Wednesdays from Nov 11, 2008 3:55 PM to Dec 11, 2008 3:55 PM.

Hourly Average: It represents the average value of the collected values in a particular day of the week over a period of time. Eg. The average value '62' represents the data collected on Wednesdays from Nov 11, 2008 3:55 PM to Dec 11, 2008 3:55 PM.

Top

Statistical Report

A sample Statistical Report is shown below. This report represents the standard deviation of this attribute over a period of time. For eg. lets consider CPU utilization attribute over a period of time. X-axis represents CPU Utilization range in percentage and Y-axis represents Count in percentage. Lets consider peak value of Count percentage to be 55% and is within the range of 70% - 80%. This means that for 55% of the polled value is within the range of 70% and 80%. This data can be used to re-allocate or organize resources for the server accordingly.

 Top

Heat Report

A sample Heat Report is shown below. This report is largely useful to compare the similar types of monitors and to check their performance of each monitor with other monitors. These heat charts are plotted based on how the attribute of the particular monitor type performs according to the threshold configured for that particular monitor. If a threshold is configured for the attribute of a particular monitor, then the threshold is taken and heat chart is plotted. There are three colors by which heat chart is plotted.

Red color indicates critical breach in threshold, Orange color indicates warning, and Green color is clear.

If the threshold is breached, then the color of the heat chart changes accordingly. This implies drop in performance, thus providing clear understanding of various monitors performance of the same type. If the threshold value for each attribute for that particular monitor is not set, then the common threshold value is automatically assumed and this heat chart is generated.

The 'Edit' option provided in this chart will facilitate the user to view the heat chart in any other threshold definition on the fly. Please note that by editing threshold the view won't affect the original threshold configured for the attribute. 

Top