OneSight Administrator Guide

Specifying When to Delete Database Records
includes alerts that have action plans associated with them as well
as those that have no response configured.
Action Plans (Resolved) – Select the number of days that data about
resolved action plans should remain in the OneSight database.
Historical Data Settings – The Historical Data settings refer to the
types of data stored in the OneSight database for every item within
every web component that OneSight measures or tests.
Historical Data Detail – Type in the number of days that the
OneSight database should store information about every
measurement and alert that transpires for everything that OneSight
is measuring. From a resource perspective, this is “expensive”
information to store, so a lower number is best if you are concerned
about capacity.
Historical Data Hourly Summary – The OneSight database also
stores, for every hour that OneSight is monitoring an item, a value
that summarizes the measurements returned by that item. Select the
number of days you want the OneSight database to store that type
of information.
Audit Data – Specifies the number of days of data to store for the
Audit report. The Audit report provides an audit trail of OneSight
configuration activity. Specify the number of days you want the
OneSight database to store that type of information.
Log Files – Specifies the number of days to keep log files.
Auxiliary data – Specifies how long to store auxiliary data. This data
includes the saved HTML source from successful Oracle Test for
Web Applications Transaction monitor runs if the Save HTML from
successful runs check box on the General tab of the Oracle Test for
Web Applications Transaction monitor configuration is checked,
the saved HTML source from failing Oracle Test for Web
Applications Transaction monitor runs if the Save HTML from
failing runs check box on the General tab of the Oracle Test for
796 OneSight Administrator Guide