Help link
is a context-sensitive link to this Help topic.
Help for Foxhound Beta 1.08.3243a
Table of Contents [RisingRoad]
The Foxhound Options page lets you change a variety of Foxhound settings and perform a variety of Foxhound-specific tasks.
Settings in this page are global in nature: any changes you make will apply to all Foxhound users and sessions running on this copy of the Foxhound engine.
The New Menu link opens the Foxhound Menu page in a new browser window or tab.
The
Help link
is a context-sensitive link to this Help topic.
The About link opens the About Foxhound page in a new browser window or tab.
The button hides this Help frame from view, and brings it back.
The checkbox Show the Help frame on the right side by default changes Foxhound's behavior whenever a new page is opened: if checked, Foxhound will initially show the right-hand Help frame. If unchecked, Foxhound will not initially show the right-hand Help frame. It doesn't affect pages that are already open, just what happens for new pages.
You must click on the button if you want the checkbox setting value to be saved (not this fake button, but the real one on the Foxhound Options page :)
The Connection timeout: radio buttons control how long the Foxhound Monitor will wait for a response when trying to connect to a target database:
1 minute, or
never timeout.
You must click on the button if you want the new Connection timeout: value to be saved.
Most connection attempts either succeed or fail right away, and the Foxhound Monitor normally keeps trying to connect if it fails so that sampling can begin or resume as soon as a connection is possible.
Sometimes, however, an attempt to connect to a target database located far away on a WAN will take a very long time to receive a response if the connection fails. In some of these cases, the Foxhound engine is blocked from doing other work while waiting to receive the failed response, and this causes problems if the Foxhound Monitor keeps repeating this long wait while trying to monitor other databases at the same time.
In cases like this, it may be better to run the Foxhound engine on a computer that is located physically close to the target database server and communicates over a LAN rather than WAN. For more information on this topic see the Help section Introduction and Setup - Running Foxhound as a Service.
The connection timeout facility is provided to stop the Foxhound Monitor from continuously trying to connect to a database when the failure-to-connect response takes a long time. When a timeout occurs, Foxhound will stop trying to connect just as if you clicked on Cancel Request or Stop Sampling, and it will not try to connect again until you tell it Start Sampling.
If you get a lot of false timeouts, try the 1 minute setting.
If you are only monitoring one database, the never timeout is probably best: Foxhound's problems with long waits for failure-to-connect responses are not important, and sampling will begin as soon as the Foxhound Monitor is able to connect.
The Purge sample data: radio buttons how soon old Monitor sample data will be deleted:
after 1 week,
after 1 month,
after 1 year or
never purge anything.
You must click on the button if you want the new Purge sample data: value to be saved.
Foxhound's internal purge process runs every hour that the Foxhound engine is up. If you have a lot of old samples stored, and you shorten the purge period (say, from 1 year to 1 week) Foxhound won't delete all the stale data at once; instead, it will delete chunks of data on successive purge runs.
The Note: line tells you a bit about the Foxhound database itself:
the size of the file,
the amount of free space in the Foxhound database (which is available to store for new samples), and
the number of disk fragments used to store the file.
At the present time, the Foxhound database is not open for ad-hoc queries. However, support from RisingRoad is available, and the Export Samples feature is an alternative to sending in the entire Foxhound database.
The Export samples for database: field lets you pick which sample session is to be exported.
The To folder: field lets you enter the destination folder. The folder must exist.
Click on the button to write the following export files to the folder:
If the files exist, they will be overwritten.
If Foxhound encounters a run-time exception, it may store diagnostic information in an internal table. Foxhound also stores some informational messages in this table.
The button lets you display the most recent diagnostic data in reverse order by timestamp.
The Export diagnostics to file: field and the button let you write all the diagnostic data, sorted by timestamp. If the file exists, it will be overwritten.
The button lets you delete the diagnostic data from the Foxhound database.
The button will stop the Foxhound database engine. This button is disabled if the Foxhound engine is not running locally; you can't stop or start Foxhound remotely, you have to go to the computer where it's running.
The button will refresh the Foxhound Options page with new data.
The button will close the Foxhound Options browser window or tab.
[Top]
[Top]