When looking at graphs, keep the following in mind:
The production of graphs is CPU-intensive. If you are monitoring CPU usage, an alert might fire when the graph is generated. To avoid firing such an alert, increase the number of failed polls before OpenEdge Management throws an alert.
Only resources that have defined monitors produce information that is graphed.
A yellow header in the viewlet graph on the Dashboard page indicates that the resource with which the viewlet is attached is not checked in. A red header in the viewlet graph indicates that the resource is offline. For more information about viewlets and the Dashboard page, see OpenEdge Management: Resource Monitoring.
Data averaging is displayed on all graphs and appears in the graph's legend.
Any discontinuity in the caching of a database resource's data will be reflected in the graphs. Caching discontinuity occurs when a resource goes off line or a resource monitor is disabled. Discontinuities are obvious in line graphs, as they appear as a break in the line. Note that caching discontinuities are harder to distinguish on area or column graphs, since gaps in area or column graphs can indicate either a zero value or caching discontinuity.
All graph data is stored in the OpenEdge Management work directory's cachedata folder (by default, in OpenEdge\wrk_oemgmt).If OpenEdge Management is not running, you can delete the database. Doing so, however, will cause you to lose all of your cached graph data.
By default, 15 days of graph data is stored for each database resource. You can choose a different setting on the Graph Cache Database Configure page.
You can access the Graph Cache Database Configure page by clicking Options > Graph Cache on the OpenEdge Management console. See OpenEdge Management and OpenEdge Explorer: Getting Started for more details about setting the graph cache.
All graphs except viewlets have three options in the top-right corner to customize the graphs. Using these options you can select a time period, ranging from 2 hours to 2 weeks, to display the data collected for that period of time, reload the graph, and select different forms of graphical interpretation. For information about customizing viewlets on the Dashboard page, see OpenEdge Management: Resource Monitoring.
The production of graphs is CPU-intensive. If you are monitoring CPU usage, an alert might fire when the graph is generated. To avoid firing such an alert, increase the number of failed polls before OpenEdge Management throws an alert.