Databases Reference
In-Depth Information
Other charts can be created and any other exposed runtime MBean attribute can be added.
The
QueueLength
attribute from the other Managed Servers of the
PROD_Cluster
cluster
can also be added to the same chart.
The chart polls for the online and real-time statistics, keeping by default
100 samples of 20 second intervals each, giving about 30 minutes of
time range.
See also
F
View Historical Data in the Monitoring Dashboard using a Database
Viewing historical data in the monitoring
dashboard using a database
In the previous recipe, a Dashboard custom view was created to display the
QueueLength
attribute of the
ThreadPoolRuntime
MBean of the Managed
Servers of the
PROD_Cluster
cluster.
The Dashboard can collect the data from two sources. One is from the exposed MBeans,
displaying polled runtime statistics like the previous recipe. The other form is from the WLDF
archive data collected from a WLDF harverster. This stored data is called collected metrics by
the Monitoring Dashboard.
In this recipe, the
PROD_Server01
,
PROD_Server02
,
PROD_Server03
, and
PROD_Server04
WLDF archives will be configured to use a database instead of the default
file-based archive to hold the data collected from a WLDF Harvester. A new custom view will
be created to display this data and it will be able to display all the collected historical data
instead of the default 30 minutes collected from the polled collector. The
QueueLength
attribute will be used.
The database is an Oracle database, running in the
dbhost
hostname and listening to the
port
1521
. The listener is accepting requests to the service named
dbservice
.
Getting ready
The recipe will use the database
dbhost
, so create a new JDBC data source named
ds-wldf-archive
, with a JNDI name
jdbc/ds-wldf-archive
targeted to the
PROD_Cluster
cluster.
The database tables
WLS_EVENTS
and
WLS_HVST
have to be created. WebLogic uses
these tables to store the WLDF archive data.
Search WWH ::
Custom Search