Help for Foxhound 2.0.4215a

6. The Monitor Options Page

The Monitor Options page lets you set the default Alerts criteria as well as the Alerts criteria for individual target databases. It also allows you to force the default Alerts criteria onto all target databases, and to manage multiple Monitor sessions (define, start, stop and delete) using a tab-delimited file of connection strings.

The Monitor Options Menu

1. Global Overrides

2. Manage Multiple Monitor Sessions

3. Switch to a Different Set of Monitor Options

4. Save And Restore Monitor Options

5. Sample Schedule

6. Connection Sample Schedule

7. Alert Email Setup

8. Alert Email Schedule

10. AutoDrop Notice Email Setup

11. AutoDrop Schedule

12. AutoDrop Criteria

13. Do-Not-AutoDrop Lists

The Monitor Options Menu [Top]

The title shows [Default Settings] or the name of the DSN or Connection String of the target database to which various options apply.

If the target database GlobalDBId property is set to a non-default value, that value will be shown in (parentheses) after the DSN: or Connection String: title. This makes it easier to tell different remote databases apart in a replicating or synchronizing environment.

The New Menu link opens the Foxhound Menu page in a new browser window or tab.

The Foxhound Options link opens the Foxhound Options page in a new browser window or tab, where you can fill in the email server settings for sending Alert emails.

The button is a context-sensitive link to this Help topic. This button appears in many locations, each of them a link to a different Help topic in this frame.

Tip: To hide the Help for every new page, see the Show Help section on the Foxhound Options page.

The About link opens the About Foxhound page in a new browser window or tab.

1. Global Overrides [Top]

This section lets you quickly (and temporarily) turn off certain features without changing (or affecting) the dozens of others settings that otherwise control how those features work.

The Enable Emails checkbox lets you turn off the Alert email facility for all target databases being monitored by Foxhound. This checkbox does not affect any other email settings (for example, that you normally want Alert emails for database A but not database B, and you have set that up using the Monitor Options page), but it does override their effect when you uncheck this checkbox. When you check this checkbox again, all the other email settings take effect.

The Enable Schedules checkbox lets you turn off all the Schedule facilities for all target databases being monitored by Foxhound. This checkbox does not affect any other Schedule settings (for example, that you normally want to turn Alert emails on and off at certain times of the day for database A but not database B, and you have set that up using the Monitor Options page), but it does override their effect when you uncheck this checkbox. When you check this checkbox again, all the other Schedule settings take effect.

The Enable AutoDrop checkbox lets you turn off the AutoDrop facility for all target databases being monitored by Foxhound. This checkbox does not affect any other AutoDrop settings (for example, that you normally want to drop connections that are blocking other connections to database A but not database B, and you have set that up using the Monitor Options page), but it does override their effect when you uncheck this checkbox. When you check this checkbox again, all the other AutoDrop settings take effect.

You must click if you want your changes saved. Any one the Save buttons will save all the changes you have made anywhere on this page.

2. Manage Multiple Monitor Sessions [Top]

The Connection Strings file: field lets you provide the file specification for a text file containing connection strings for multiple target databases. The file contains one line per target database, with each line terminated by a carriage return - line feed pair ('\x0d\x0a'). Each line contains two fields, separated by a single tab character ('\x09'). The first field contains a unique name for the connection string, and the second is the connection string itself. Here is and example:

ddd001	ENG=benchmark; DBN=ddd001; UID=dba; PWD=sql; DRIVER=SQL Anywhere 12;
ddd002	ENG=benchmark; DBN=ddd002; UID=dba; PWD=sql; DRIVER=SQL Anywhere 12;
ddd003	ENG=benchmark; DBN=ddd003; UID=dba; PWD=sql; DRIVER=SQL Anywhere 12;
ddd004	ENG=benchmark; DBN=ddd004; UID=dba; PWD=sql; DRIVER=SQL Anywhere 12;

The button will save all the changes you have made anywhere on this page, including the Connection Strings file.

The Connection Strings file is used when you press each of the following four buttons. You can create different files for different purposes; e.g., for starting and stopping a large number of Monitor sessions in smaller batches.

Note: If you enter a new value in the Connection Strings file field, and then press one of the other buttons Create Connection Strings, etc., the new Connection Strings file value will be saved in the Foxhound database even though you didn't press Save. In this case, only that value will be saved, not any of the changes you might have made elsewhere on this page.

The button uses the data in the Connection Strings file to create or replace Connection Strings in the Foxhound database.

After pressing this button, the individual connection strings will be visible in the String tab of the Foxhound Menu page. However, the target databases won't be visible in the Monitor tab of the Foxhound Menu page unless the connection strings had previously existed and monitoring had been started at some point in the past.

The button reads the connection string names from the Connections Strings file and starts a Monitor session for each corresponding target database if that session is not already running or in the process of starting.

After pressing this button, the target databases will be visible in the Monitor tab of the Foxhound Menu page.

The button reads the connection string names from the Connections Strings file and stops the Monitor session for each corresponding target database if it is running or cancels that session if it is in the process of starting.

After pressing this button, the target databases will still be visible in the Monitor tab of the Foxhound Menu page.

The button reads the connection string names from the Connections Strings file and deletes the Monitor session for each corresponding target database if that session is not already running or in the process of starting.

After pressing this button, the target databases will no longer be visible in the Monitor tab of the Foxhound Menu page. However, the connection strings will still be visible in the String tab of the Foxhound Menu page.

3. Switch to a Different Set of Monitor Options [Top]

The Switch Set of Monitor Options link lets you pick which set of Monitor Options settings you want to edit.

There is one set of Monitor Options for each target database that has had a Monitor session started at some point, even if that session is not currently running.

There is another set of options called [Default Settings] which will be used to initialize the Monitor Options for a new target database when a Monitor session for that database is first started.

The [Default Settings] can also be forced (pushed) onto all the other sets of Monitor Options by pressing the button; see the next section.

4. Save And Restore Monitor Options [Top]

The buttons in this section let you manipulate entire sets of Monitor Options in different ways.

Which buttons are enabled, and how they work, depend on whether the [Default Settings] or some other set of options is currently displayed.

The button does two things:

First, it works just like a button: it saves all the values on this page for use with the current target database.
Second, it saves the same values as the [Default Settings].

The button does two things:

First, it replaces all the values on this page with the [Default Settings].
Second, it works just like a button: it saves all the values on this page as the options set used for the current target database.

The button does two things:

First, it replaces all the values on this page with the original Foxhound "Factory Settings" that were in effect when Foxhound was first installed.
Second, it works just like a button: it saves all the values on this page as the [Default Settings], or as the options set used for the current target database, depending on which set of options is currently displayed.

The button does two things:

First, it replaces most of the values on this page with extremely aggressive settings.
Second, it works just like a button: it saves all the values on this page as the [Default Settings], or as the options set used for the current target database, depending on which set of options is currently displayed.
CAUTION: These settings are primarily intended for demonstrating how various Foxhound features work.

The button does two things:

First, it works just like a button: it saves all the values on this page as the [Default Settings].
Second, it saves all the values on this page as the current settings for each and every target database.
CAUTION: This operation may take some time. It also affects every target database, and there is no "undo" feature.

5. Sample Schedule [Top]

The Enforce the Sample Schedule lets you enable the automated Sample Schedule feature for this target database, which in turn lets you turn sampling off and on at different times of the day.

While a Sample Schedule is in effect for a particular target database, Foxhound does not allow sampling to be manually started or stopped via the "Start Sampling" or "Stop Sampling" buttons on the Monitor or Foxhound Menu pages. Instead, a link to the Monitor Options page is displayed: "...Sample Schedule in effect" on those pages.

Each Sample Schedule consists of 7 strings of 96 characters...

     AM                                              PM           
     12  1   2   3   4   5   6   7   8   9   10  11  12  1   2   3   4   5   6   7   8   9   10  11                                
Mon  YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYyYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
Tue  YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYyYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY  
Wed  ...............................................^................................................ 
Thu  YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYyYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY  
Fri  YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYyYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
Sat  YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYyYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
Sun  YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYyYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY

Here's how it works:

Each character represents one 15-minute period, from 12:00 midnight to 12:14:59.999 AM, 12:15 AM to 12:29:59.999 AM, and so on, 24 hours a day, 7 days a week.
You type "Y" or "y" for "yes, sampling is enabled for this 15-minute period".
Anything else means "no, sampling is stopped for this 15-minute period".
Foxhound will change the "anything else" to "." or "^" when you click on Save.
Foxhound displays "^" and lower-case "y" to show you which column includes the current clock-on-the-wall time... but be careful, the display isn't updated automatically.
If you type too many characters in one day, Foxhound will chop off the extra characters on the right.
If you don't fill all the characters in one day, Foxhound will pad the day to the right with "." or "^" characters.
The button changes the day to all "Y" and "y" characters.
The button changes the day to all "." and "^" characters.
The button shifts all the characters to the left by one position, filling the right-most position with "." or "^"; in other words, it shifts but it doesn't wrap.
The button shifts all the characters to the right by one position, filling the left-most position with "." or "^"; in other words, it shifts but it doesn't wrap.
The button sets all the characters from 9:00 AM to 4:45 PM to "Y" or "y", and sets the rest to "." or "^".
The button sets all the characters from 5:00 AM to 8:45 PM to "Y" or "y", and sets the rest to "." or "^".
You can also copy-and-paste into each day's string of characters.

You must click if you want your changes saved. Any one the Save buttons will save all the changes you have made anywhere on this page.

6. Connection Sample Schedule [Top]

The Enforce the Connection Sample Schedule lets you enable the automated Connection Sample Schedule feature for this target database, which in turn lets you turn the collection of connection-level sample data off and on at different times of the day.

The Connection Sample Schedule has no effect for periods where the Sample Schedule has turned sampling off, or if sampling has been manually stopped.

The Connection Sample Schedule has no effect when the Foxhound Options - Connection Sample Threshold has suppressed the collection of connection-level data because the threshold connection count is exceeded.

Each Connection Sample Schedule consists of 7 strings of 96 characters...

     AM                                              PM           
     12  1   2   3   4   5   6   7   8   9   10  11  12  1   2   3   4   5   6   7   8   9   10  11                                
Mon  YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYyYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
Tue  YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYyYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY  
Wed  ...............................................^................................................ 
Thu  YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYyYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY  
Fri  YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYyYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
Sat  YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYyYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
Sun  YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYyYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY

Here's how it works:

Each character represents one 15-minute period, from 12:00 midnight to 12:14:59.999 AM, 12:15 AM to 12:29:59.999 AM, and so on, 24 hours a day, 7 days a week.
You type "Y" or "y" for "yes, connection-level sample data will be recorded for this 15-minute period".
Anything else means "no, connection-level sample data will not be recorded for this 15-minute period".
Foxhound will change the "anything else" to "." or "^" when you click on Save.
Foxhound displays "^" and lower-case "y" to show you which column includes the current clock-on-the-wall time... but be careful, the display isn't updated automatically.
If you type too many characters in one day, Foxhound will chop off the extra characters on the right.
If you don't fill all the characters in one day, Foxhound will pad the day to the right with "." or "^" characters.
The button changes the day to all "Y" and "y" characters.
The button changes the day to all "." and "^" characters.
The button shifts all the characters to the left by one position, filling the right-most position with "." or "^"; in other words, it shifts but it doesn't wrap.
The button shifts all the characters to the right by one position, filling the left-most position with "." or "^"; in other words, it shifts but it doesn't wrap.
The button sets all the characters from 9:00 AM to 4:45 PM to "Y" or "y", and sets the rest to "." or "^".
The button sets all the characters from 5:00 AM to 8:45 PM to "Y" or "y", and sets the rest to "." or "^".
You can also copy-and-paste into each day's string of characters.

You must click if you want your changes saved. Any one the Save buttons will save all the changes you have made anywhere on this page.

7. Alert Email Setup [Top]

The Send Alert emails checkbox specifies whether or not you want Alert, All Clear and Cancelled emails to be sent.

Note: The Send Alert emails checkbox does not affect whether AutoDrop Notice emails are sent, but the remainder of the fields in this section do apply to AutoDrop Notice emails.

Use the Email address(es) for Alerts and AutoDrop Notices: field to specify one or more email addresses, separated by semicolons, that are to receive the Alert, All Clear, Cancelled and AutoDrop Notice emails.

Click on the Use HTML in emails: checkbox if you want the email alerts to be formatted using HTML.

The Host[:port] for URLs in emails: field may be used to specify where the Foxhound web server is located relative to the computer receiving the emails, so that HTML links pointing to Foxhound History pages from inside the email alerts can find the right web pages. The default is localhost which works if the emails are being received on the same computer that's running Foxhound. If you start Foxhound on some port other than 80, you can specify a value like localhost:12345. If Foxhound is running on a different computer you'll have to change localhost to that computer's domain name or IP address; e.g., xyz.com:12345.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

The button may be used to check that the email settings are correct.

The Test result: field will display OK if the test email was sent ok, or an error message if there was a problem. However, you should also check that the email was received at the other end; just because a message was sent doesn't mean it will actually arrive.

For more information see this Q&A entry:

Message: SMTP send email failed with return code ... when sending "..."

8. Alert Email Schedule [Top]

The Enforce the Alert Email Schedule lets you enable the automated Alert Email Schedule feature for this target database, which in turn lets you turn the sending of Alert emails off and on at different times of the day.

Each Alert Email Schedule consists of 7 strings of 96 characters...

     AM                                              PM           
     12  1   2   3   4   5   6   7   8   9   10  11  12  1   2   3   4   5   6   7   8   9   10  11                                
Mon  YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYyYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
Tue  YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYyYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY  
Wed  ...............................................^................................................ 
Thu  YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYyYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY  
Fri  YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYyYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
Sat  YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYyYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
Sun  YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYyYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY

Here's how it works:

Each character represents one 15-minute period, from 12:00 midnight to 12:14:59.999 AM, 12:15 AM to 12:29:59.999 AM, and so on, 24 hours a day, 7 days a week.
You type "Y" or "y" for "yes, emails will be sent for Alert, All Clear and Cancelled messages issued during this 15-minute period".
Anything else means "no, emails will not be sent for Alert, All Clear and Cancelled messages issued during this 15-minute period".
Foxhound will change the "anything else" to "." or "^" when you click on Save.
Foxhound displays "^" and lower-case "y" to show you which column includes the current clock-on-the-wall time... but be careful, the display isn't updated automatically.
If you type too many characters in one day, Foxhound will chop off the extra characters on the right.
If you don't fill all the characters in one day, Foxhound will pad the day to the right with "." or "^" characters.
The button changes the day to all "Y" and "y" characters.
The button changes the day to all "." and "^" characters.
The button shifts all the characters to the left by one position, filling the right-most position with "." or "^"; in other words, it shifts but it doesn't wrap.
The button shifts all the characters to the right by one position, filling the left-most position with "." or "^"; in other words, it shifts but it doesn't wrap.
The button sets all the characters from 9:00 AM to 4:45 PM to "Y" or "y", and sets the rest to "." or "^".
The button sets all the characters from 5:00 AM to 8:45 PM to "Y" or "y", and sets the rest to "." or "^".
You can also copy-and-paste into each day's string of characters.

You must click if you want your changes saved. Any one the Save buttons will save all the changes you have made anywhere on this page.

9. Alert Criteria [Top]

An alert is a message automatically displayed and/or sent via email whenever one or more target database conditions match user-defined criteria. The Monitor Options page lets you specify these criteria for a particular target database. Individual criteria may include a threshold amount and/or a duration or waiting period.

An alert may be issued as soon as a condition is met (e.g. Alert #9), when a threshold has been reached (e.g. Alert #5) or it may include a waiting period such as "for 10 or more recent samples" (e.g. Alert #2).

An all clear is issued when the alert criteria is no longer met. If a waiting period is specified, Foxhound waits for approximately half that time before issuing the all clear.

A cancelled message is issued as soon as some alert criteria is changed or disabled using this page. At that point the alert testing process "starts over"; it doesn't matter what the change is. For example, even if the new alert condition is already met when the change is made, if there is a waiting period it is honored before a new alert is issued.

9a. Alerts 1 - 10 [Top]

Alert #1 - Database unresponsive
Alert #2 - Long heartbeat
Alert #3 - Long sample time
Alert #4 - CPU usage
Alert #5 - Database disk space
Alert #6 - Temp disk space
Alert #7 - Log disk space
Alert #8 - Other disk space
Alert #9 - Arbiter unreachable
Alert #10 - Partner unreachable

Alert #1 - Database unresponsive - Foxhound has been unable to gather samples for [1m] or longer. [Top]

The Alert #1 enabled checkbox specifies whether or not you want Foxhound to check for this condition.

The "unable to gather samples for xxx" duration uses the "d h m s" input format; e.g., 1m for one minute, 10s for ten seconds, 3d for three days, 1h 30m for one hour and 30 minutes.

This Alert is issued if

the elapsed time since the last successful sample was recorded, or
the elapsed time since Foxhound was last restarted after being stopped,
whichever is shorter,
is greater than or equal to the threshold duration; e.g., 1m.

A subsequent All Clear is issued when a subsequent successful sample is recorded.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

Alert #2 - Long heartbeat - The heartbeat time has been [1.0s] or longer for [10] or more recent samples. [Top]

The Alert #2 enabled checkbox specifies whether or not you want Foxhound to check for this condition.

The "heartbeat time has been xxx" duration uses the "d h m s" input format; e.g., 10s for 10 seconds, 3d for 3 days, 1h 30m for 1 hour and 30 minutes.

This alert is based on measurements made by Foxhound itself.

The "for xxx or more recent samples" text box contains a count of samples taken by the Foxhound Database Monitor.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

Alert #3 - Long sample time - The sample time has been [10.0s] or longer for [10] or more recent samples. [Top]

The Alert #3 enabled checkbox specifies whether or not you want Foxhound to check for this condition.

This alert is based on measurements made by Foxhound itself.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

Alert #4 - CPU usage - The CPU time has been [90]% or higher for [10] or more recent samples. [Top]

The Alert #4 enabled checkbox specifies whether or not you want Foxhound to check for this condition.

This alert is based on the following properties: NumLogicalProcessorsUsed, NumProcessorsAvail, NumProcessorsMax and ProcessCPU.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

Alert #5 - Database disk space - The free disk space on the drive holding the main database file has fallen below [1GB]. [Top]

The Alert #5 enabled checkbox specifies whether or not you want Foxhound to check for this condition.

This alert is based on the sa_disk_free_space system procedure. This alert is not produced if the free disk space drops to exactly zero because that is most likely a problem with the sampling process itself.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

Alert #6 - Temp disk space - The free disk space on the drive holding the temporary file has fallen below [1GB]. [Top]

The Alert #6 enabled checkbox specifies whether or not you want Foxhound to check for this condition.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

Alert #7 - Log disk space - The free disk space on the drive holding the transaction log file has fallen below [1GB]. [Top]

The Alert #7 enabled checkbox specifies whether or not you want Foxhound to check for this condition.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

Alert #8 - Other disk space - The free disk space on one or more drives holding other database files has fallen below [1GB]. [Top]

The Alert #8 enabled checkbox specifies whether or not you want Foxhound to check for this condition.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

Alert #9 - Arbiter unreachable - The high availability target database has become disconnected from the arbiter server. [Top]

The Alert #9 enabled checkbox specifies whether or not you want Foxhound to check for this condition.

This alert is based on the ArbiterState property.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

Alert #10 - Partner unreachable - The high availability target database has become disconnected from the partner database. [Top]

The Alert #10 enabled checkbox specifies whether or not you want Foxhound to check for this condition.

This alert is based on the PartnerState property.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

9b. Alerts 11 - 20 [Top]

Alert #11 - HA failover
Alert #12 - HA mode change
Alert #13 - File fragmentation
Alert #14 - Waiting requests
Alert #16 - I/O operations
Alert #17 - Checkpoint urgency
Alert #18 - Recovery urgency
Alert #19 - Cache size
Alert #20 - Cache satisfaction

Alert #11 - HA failover - The high availability target database server has switched over to [server2]. [Top]

The Alert #11 enabled checkbox specifies whether or not you want Foxhound to check for this condition.

This alert is based on the ServerName property.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

Alert #12 - HA mode change - The high availability target database has changed from [read only] to [updatable]. [Top]

The Alert #12 enabled checkbox specifies whether or not you want Foxhound to check for this condition.

This alert is usually raised when Foxhound is monitoring the read-only secondary HA database and a failover occurs. Foxhound remains connected to the same database, which is now the primary database, and the mode has changed from read-only to updatable. This alert is cleared as soon as all three HA servers become operational. Foxhound does not wait for the mode to change back to its original value.

This alert is based on the ReadOnly property.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

Alert #13 - File fragmentation - There are [1000] or more fragments in the main database file. [Top]

The Alert #13 enabled checkbox specifies whether or not you want Foxhound to check for this condition.

This alert is based on the DBFileFragments property.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

Alert #14 - Waiting requests - The number of requests waiting to be processed has reached [5] or more for [10] or more recent samples. [Top]

The Alert #14 enabled checkbox specifies whether or not you want Foxhound to check for this condition.

This alert is based on the UnschReq property.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

Alert #16 - I/O operations - There have been [1000] or more disk and log I/O operations per second for [10] or more recent samples. [Top]

The Alert #16 enabled checkbox specifies whether or not you want Foxhound to check for this condition.

This alert is based on the DiskRead, DiskWrite and LogWrite properties.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

Alert #17 - Checkpoint urgency - The Checkpoint Urgency has been [100] % or more for [10] or more recent samples. [Top]

The Alert #17 enabled checkbox specifies whether or not you want Foxhound to check for this condition.

This alert is based on the CheckpointUrgency property.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

Alert #18 - Recovery urgency - The Recovery Urgency has been [1000] % or more for [10] or more recent samples. [Top]

The Alert #18 enabled checkbox specifies whether or not you want Foxhound to check for this condition.

This alert is based on the RecoveryUrgency property.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

Alert #19 - Cache size - The cache has reached [100] % of its maximum size for [10] or more recent samples. [Top]

The Alert #19 enabled checkbox specifies whether or not you want Foxhound to check for this condition.

This alert is based on the CurrentCacheSize and MaxCacheSize properties.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

Alert #20 - Cache satisfaction - The cache satisfaction (hits/reads) has fallen to [50] % or lower for [10] or more recent samples. [Top]

The Alert #20 enabled checkbox specifies whether or not you want Foxhound to check for this condition.

This alert is based on the CacheHits and CacheRead properties.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

9c. Alerts 21 - 29 [Top]

Alert #21 - Temp file usage
Alert #22 - Conn temp file usage
Alert #23 - Blocked connections
Alert #24 - Conn blocking others
Alert #25 - Locks
Alert #26 - Connections
Alert #27 - Connection CPU
Alert #28 - Long transaction
Alert #29 - Cache panics

Alert #21 - Temp file usage - The total temporary file space used by all connections has been [1G] or larger for [10] or more recent samples. [Top]

The Alert #21 enabled checkbox specifies whether or not you want Foxhound to check for this condition.

This alert is based on the TempFilePages property.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

Alert #22 - Conn temp file usage - At least one single connection has used [500M] or more of temporary file space during [10] or more recent samples. [Top]

The Alert #22 enabled checkbox specifies whether or not you want Foxhound to check for this condition.

This alert is based on the TempFilePages property.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

Alert #23 - Blocked connections - The number of blocked connections has reached [10] or more during [10] or more recent samples. [Top]

The Alert #23 enabled checkbox specifies whether or not you want Foxhound to check for this condition.

This alert is based on the BlockedOn property.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

Alert #24 - Conn blocking others - At least one single connection has blocked [5] or more other connections during [10] or more recent samples. [Top]

The Alert #24 enabled checkbox specifies whether or not you want Foxhound to check for this condition.

This alert is based on the BlockedOn property.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

Alert #25 - Locks - The number of locks has reached [1,000,000] or more during [10] or more recent samples. [Top]

The Alert #25 enabled checkbox specifies whether or not you want Foxhound to check for this condition.

This alert is based on the LockCount property.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

Alert #26 - Connections - The number of connections has reached [1000] or more for [10] or more recent samples. [Top]

The Alert #26 enabled checkbox specifies whether or not you want Foxhound to check for this condition.

This alert is based on the ConnCount property.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

Alert #27 - Connection CPU - The approximate CPU time has been [25]% or higher or more for at least one connection during [10] or more recent samples. [Top]

The Alert #27 enabled checkbox specifies whether or not you want Foxhound to check for this condition.

This alert is based on the ApproximateCPUTime property.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

Alert #28 - Long transaction - The transaction running time has reached [1m] or more for at least one connection during [10] or more recent samples. [Top]

The Alert #28 enabled checkbox specifies whether or not you want Foxhound to check for this condition.

This alert is based on the TransactionStartTime property.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

Alert #29 - Cache panics - There have been [1] or more cache panics in [10] or more recent samples. [Top]

The Alert #29 enabled checkbox specifies whether or not you want Foxhound to check for this condition.

This alert is based on the CachePanics property.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

10. AutoDrop Notice Email Setup [Top]

The Send AutoDrop Notice emails checkbox specifies whether or not you want Foxhound to send an email Notice when a connection has been dropped by the AutoDrop facility.

Note: There is no separate "AutoDrop Email Schedule" feature.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

11. AutoDrop Schedule [Top]

The Enforce the AutoDrop Schedule lets you enable the automated AutoDrop Schedule feature for this target database, which in turn lets you turn the AutoDrop process off and on at different times of the day.

Note: There is no separate "AutoDrop Email Schedule" feature.

Each AutoDrop Schedule consists of 7 strings of 96 characters...

     AM                                              PM           
     12  1   2   3   4   5   6   7   8   9   10  11  12  1   2   3   4   5   6   7   8   9   10  11                                
Mon  YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYyYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
Tue  YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYyYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY  
Wed  ...............................................^................................................ 
Thu  YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYyYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY  
Fri  YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYyYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
Sat  YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYyYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
Sun  YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYyYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY

Here's how it works:

Each character represents one 15-minute period, from 12:00 midnight to 12:14:59.999 AM, 12:15 AM to 12:29:59.999 AM, and so on, 24 hours a day, 7 days a week.
You type "Y" or "y" for "yes, connections will be subject to the AutoDrop process during this 15-minute period".
Anything else means "no, connections will not be subject to the AutoDrop process during this 15-minute period".
Foxhound will change the "anything else" to "." or "^" when you click on Save.
Foxhound displays "^" and lower-case "y" to show you which column includes the current clock-on-the-wall time... but be careful, the display isn't updated automatically.
If you type too many characters in one day, Foxhound will chop off the extra characters on the right.
If you don't fill all the characters in one day, Foxhound will pad the day to the right with "." or "^" characters.
The button changes the day to all "Y" and "y" characters.
The button changes the day to all "." and "^" characters.
The button shifts all the characters to the left by one position, filling the right-most position with "." or "^"; in other words, it shifts but it doesn't wrap.
The button shifts all the characters to the right by one position, filling the left-most position with "." or "^"; in other words, it shifts but it doesn't wrap.
The button sets all the characters from 9:00 AM to 4:45 PM to "Y" or "y", and sets the rest to "." or "^".
The button sets all the characters from 5:00 AM to 8:45 PM to "Y" or "y", and sets the rest to "." or "^".
You can also copy-and-paste into each day's string of characters.

You must click if you want your changes saved. Any one the Save buttons will save all the changes you have made anywhere on this page.

12. AutoDrop Criteria [Top]

AutoDrop processing differs from Alert processing:

AutoDrop processing is only performed on target databases running on SQL Anywhere Version 9 and above. The LoginTime connection property is not available on earlier versions so Foxhound cannot uniquely identify different connections with 100% safety.
When a connection is dropped by AutoDrop processing, it is a one-time event, whereas when an Alert comes into effect it is a continuing condition. This means that while Alerts messages have corresponding All Clear messages, AutoDrop messages do not.
AutoDrop tracking is immediately cancelled whenever the connection sinks below the tracking threshold, whereas an All Clear may or may not be issued immediately after an Alert condition is no longer satisfied.
AutoDrop tracking is immediately cancelled whenever a sample is lost; e.g., when Foxhound could not connect to the target database.
If AutoDrop tracking is in progress when you change the corresponding AutoDrop threshold, the new threshold is immediately applied and tracking may or may not continue depending on the threshold. This differs from Alert tracking which is immediately cancelled whenever the corresponding Alert threshold is changed, no matter what the new threshold is.

AutoDrop #1 - Blocking others
AutoDrop #2 - Blocked by other
AutoDrop #3 - Long transaction
AutoDrop #4 - Temp file usage
AutoDrop #5 - CPU usage
AutoDrop #6 - Locks

AutoDrop #1 - Blocking others - Automatically drop each connection that has been blocking [5] or more other connections for [10] or more recent samples. [Top]

The AutoDrop #1 enabled checkbox specifies whether or not you want Foxhound to check for this condition.

This AutoDrop process is based on the BlockedOn property.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

AutoDrop #2 - Blocked by other - Automatically drop each connection that has been blocked by another connection for [10] or more recent samples. [Top]

The AutoDrop #2 enabled checkbox specifies whether or not you want Foxhound to check for this condition.

This AutoDrop process is based on the BlockedOn property.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

AutoDrop #3 - Long transaction - Automatically drop each connection with a transaction that has been running for [10m] or longer. [Top]

The AutoDrop #3 enabled checkbox specifies whether or not you want Foxhound to check for this condition.

This AutoDrop process is based on the TransactionStartTime property.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

AutoDrop #4 - Temp file usage - Automatically drop each connection that uses [512M] or more of temporary file space for [10] or more recent samples. [Top]

The AutoDrop #4 enabled checkbox specifies whether or not you want Foxhound to check for this condition.

This AutoDrop process is based on the TempFilePages property.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

AutoDrop #5 - CPU usage - Automatically drop each connection that uses [25]% or more of approximate CPU time for [10] or more recent samples. [Top]

The AutoDrop #5 enabled checkbox specifies whether or not you want Foxhound to check for this condition.

This AutoDrop process is based on the ApproximateCPUTime property.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

AutoDrop #6 - Locks - Automatically drop each connection that has [1,000,000] or more locks for [10] or more recent samples. [Top]

The AutoDrop #6 enabled checkbox specifies whether or not you want Foxhound to check for this condition.

This AutoDrop process is based on the LockCount property.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

13. Do-Not-AutoDrop Lists [Top]

Do-Not-AutoDrop User Id List: Exclude this semicolon-separated list of user ids from being AutoDropped: [xxx;xxx] [Top]

The Do-Not-AutoDrop User Id List enabled checkbox specifies whether or not you want Foxhound to check user ids against this list before dropping any connections.

Use semicolons to separate multiple user ids, and don't include any extra spaces; for example:

g.mikhailov;e.reid;n.simpson;x.wang;c.ryan

Note that Foxhound already excludes the following connections; you don't have to specify them in either Do-Not-AutoDrop list:

The AutoDrop process does not touch Foxhound's own connections; i.e., AutoDrop ignores connections names that begin with "Foxhound".
The AutoDrop process does not touch internal connections; i.e., AutoDrop ignores connections where the UserID is empty.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

Do-Not-AutoDrop Connection Name List: Exclude this semicolon-separated list of connection names from being AutoDropped: [xxx;xxx] [Top]

The Do-Not-AutoDrop Connection Name List enabled checkbox specifies whether or not you want Foxhound to check connection names against this list before dropping any connections.

Use semicolons to separate multiple connection names, and don't include any extra spaces; for example:

app;payroll

Note that Foxhound already excludes the following connections; you don't have to specify them in either Do-Not-AutoDrop list:

The AutoDrop process does not touch Foxhound's own connections; i.e., AutoDrop ignores connections names that begin with "Foxhound".
The AutoDrop process does not touch internal connections; i.e., AutoDrop ignores connections where the UserID is empty.

You must click if you want your changes saved. Any one of the Save buttons will save all the changes you have made anywhere on this page.

[Top]