| eG Monitoring |
|---|
|
Detailed Analysis of a chosen Measure in the MEASURES page This page appears when you click on the
The eG Enterprise system embeds an optional detailed diagnostic capability that provides a detailed diagnosis of certain measures. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. For example, when the CPU usage of a host reaches the threshold, the agent can be configured to provide more details – e.g, the top 10 processes that are consuming more CPU resources. Optionally, this capability can also be configured to generate detailed measures even if no problems occur. This tab page allows you to view the detailed diagnosis of the chosen measure, by default. Additonally, once you navigate to this tab page from the Measures page, you can view the name of the Component for which the meassure is chosen, the name of the Test that collects the chosen measure and the agent that collects the required measure will be displayed in the Measured By field. If the Test is descriptor based, you can choose a descriptor for which you need to view the detailed measures for the chosen measure from the Description list box. By default, the chosen measure will be listed in the Measurement list box. If the Test that collects the chosen measure also collects some additional measures for which the detailed diagnosis capability is enabled, such measures will also be listed in the Measurement list box. The period for which detailed measures need to be generated can be specified by selecting an option from the Timeline list. You can either provide a fixed time line such as 1 hour, 2 days, etc., or select the Any option from the list to provide a From and To date/time for DD generation. Clicking on the Submit button will retrieve the detailed measures for the selection of your choice. You can save the detailed measures as a CSV file by clicking on the CSV button, or print the measures by clicking on the PRINT button, or analyse the chosen measure by clicking on the Analysis button.
The eG Enterprise system includes a variety of graphing capabilities for manual diagnosis. A measure graph is used by a user to plot the instantaneous value of any of the measurements made by the eG Enterprise system with time of day. By default, this tab page shows the measure graph for the chosen measure from the MEASURES page. You can also view the measure graph for any other measure reported by this test, by selecting that measure from the Measure list box. The period for which the variations of the selected measurements have to be analyzed can be specified using the Timeline list. You can either provide a fixed time line such as 1 hour, 2 days, etc., or select the Any option from the list to provide a From and To date/time for graph generation. If you want the measure graph to plot the past values too, select the Lookback check box. If the Lookback option is chosen, then proceed to select an Interval for the past values. For example, if the Timeline for the current measures is set to 1 hour, then the current measure graph will be plotted for the last one hour - say, for 12.00 PM to 1.00 PM of February 22, 2012. If the Interval is set to 1 day, then eG Enterprise will plot the values reported between the same hour (i.e., 12.00 PM and 1.00 PM), but for the previous day - i.e., February 21, 2012. If the test that is reporting the chosen measure is descriptor based, then the Description list box will list out all the descriptors that are available for the chosen measure. The agent that collects the required measure will be displayed in the Measured By field. To view the graph for the values that fall within the range of your choice, you can use the Data Range option. The Graph button can be utilized to view the graph. The DATA button will enable the user to view the table of data corresponding to the graph. The user can print the graph using the PRINT button or save it using the SAVE button.
The summary graph gives an overall picture of the percentage of good, bad and unknown measurements over a period of time. By default, this tab page shows the summary graph for the chosen measure from the MEASURES page. You can also view the summary graph for any other measure reported by this test, by selecting that measure from the Measure list box. If the test that is reporting the chosen measure is descriptor based, then the Description list box will list out all the descriptors that are available for the chosen measure. The agent that collects the required measure will be displayed in the Measured By field. Users can also opt to view the hourly, daily or monthly variations of measures in the case of summary graphs by selecting an appropriate option from the Duration list box. The period for which the variations of the selected measurements have to be analyzed can be specified using the Timeline list. You can either provide a fixed time line such as 1 hour, 2 days, etc., or select the Any option from the list to provide a From and To date/time for graph generation. Click the Graph button to view the summary graph. The user can print the graph using the PRINT button or save it using the SAVE button.
Graphs showing the measurements over time are ideal for real-time analysis of metrics. For capacity planning or for long term historical analysis, trend graphs that denote trends in the data values over time are more appropriate. The eG Enterprise manager computes trend values from the raw measurement data as part of its day-end activity. Trend values are computed on an hourly, daily, and monthly basis. Since these values represent the results of the analysis of the raw measurement results, the trend values take up much less storage space in the eG database than the measurement values. The trend graph option in the eG monitoring console allows users to view and analyze the computed trend values over time. Besides revealing normal performance levels, trend analysis also aids administrators in forecasting future usage trends and accordingly planning the capacity of target servers. By default, this tab page shows the trend graph for the chosen measure from the MEASURES page. You can also view the trend graph for any other measure reported by this test, by selecting that measure from the Measure list box. The period for which the variations of the selected measurements have to be analyzed can be specified using the Timeline list. You can either provide a fixed time line such as 1 hour, 2 days, etc., or select the Any option from the list to provide a From and To date/time for graph generation. If the test that is reporting the chosen measure is descriptor based, then the Description list box will list out all the descriptors that are available for the chosen measure. The agent that collects the required measure will be displayed in the Measured By field. By default, the eG manager uses statistical quality control techniques to compute the upper and lower bounds of each metric in the database. This computation removes the outliers among the data values for the chosen period. The default Min/Max selection from the Graph list shows the upper/lower bounds for each measurement over time. In some cases, capacity planners may prefer to view hourly/daily/monthly averages of metrics. The Average option in the Graph list displays such a graph. For instance, you can plot a trend graph that depicts how many user connections on an average were established with a critical Terminal server, every day during a couple of weeks; besides indicating the normal load on the Terminal server, such a graph also enables you to understand whether the Terminal server has been adequately tuned to handle higher loads, and thereby helps you make effective sizing recommendations for the future. Many of the measurements made by eG agents represent data values over time - eg., the rate of requests handled by a web site, the rate of traffic to and from a network node, etc. While data rates are good indicators of the workload from a monitoring perspective, from a capacity planning perspective a better indicator would be the total volume of requests or data handled. In the case of a web site, for example, the total number of requests handled by the web site per hour, day, and month would be of interest. The Sum option of the trend graph provides this capability. If the unit of the selected measure is a number - eg., requests handled in the last measurement period - the Sum graph plots the sum of the measure values over time. If the measure is a rate (e.g., Request/second handled by the web site), then eG Enterprise manager converts the rate into an absolute value by multiplying the rate with the measurement period, and computes the hourly, daily, and monthly sums of these absolute values during the trending process. The results of this computation can be plotted over time in the Sum graph. Users can also opt to view the hourly, daily or monthly variations of measures in the case of summary graphs by selecting an appropriate option from the Duration list box. Click the Graph button to view the graph. The user can print the graph using the PRINT button, or save it using the SAVE button. Clicking on the DATA button reveals the trend data that has been plotted on the graph. Note: The capability of the eG manager to compute the Sum and Average of metrics is governed by the Compute average/sum of metrics while trending flag in MANAGER SETTINGS page (Configure -> Manager Settings) in the eG administrative interface. By default, this flag is set to Yes indicating that eG Enterprise computes and stores the average and sum values of every performance metric in the database, by default. If, for some reason, you want to disable this capability, just set this flag to No, and Update the changes. Unlike average values, Sum computation could be meaningless in the case of a few measures (eg., Availability, Percentage usage of disk space, etc.). Therefore, instead of maintaining the Sum values for all measures in the database, you can configure the eG manager to compute Sum for specific measures only. To do so, follow the steps given below:
The user can keep track of the problems arising in his/her environment and the solutions to these problems by making an entry in the feedback form that can be obtained on clicking the Fix Feedback tab page. This page enables you to record the details of how specific problems were identified and how the problems were fixed. This information is maintained in the eG database and represents a location-specific knowledge base that can be queried by the user at a later point of time. When a problem occurs, the user can query the knowledge base to determine how a similar problem had been fixed in the past.
The set of problems that are entered via the feed back form can be viewed in the FIX HISTORY tab page. This FIX HISTORY tab page can also be accessed using the HISTORY image in the layer model page of the chosen component. In this page you can view the list of problems associated with a particular component, test, and measure combination, and the steps suggested / taken for fixing each problem. By default, the Show Feedback from All Components/Descriptors check box will be selected in this tab page. If fixes pre-exist for a given Test-Measure-Description combination, but for components other than the chosen one, then, by default, the details of such fixes will also be displayed. This way, users can quickly access all the fixes related to a given problem from a single console. To view the fix feedback recorded for the chosen component alone, deselect the Show Feedback from All Components/Descriptors check box. If the feedback provided on a problem includes a URL, then while viewing the feedback history, the URL will be automatically hyperlinked by the eG Enterprise system, so that administrators can click on the URL in the history and directly connect to the web page that sheds more light on the issue at hand and the means of correcting it. Note: By default, monitor users have access to the fix history of problems pertaining to only those components that have been assigned to them. To grant the monitor users access to the fix history of all the monitored components in the environment, do the following:
|