Database Monitors

• MySQL Port
  The number of the port on which the MySQL instance is listening. The default is 3306 .
• Username
  The user name that is required to log into the MySQL instance.
• Password
  The password that is required to log into the MySQL instance.
• Uptime
  The number of seconds that MySQL has been running.
• Questions
  The number of queries that have been sent to the database.
• Slow Queries
  The number of queries that take longer than long_query_time to complete.
  When started with the --log-slow-queries[=file_name] option, MySQL writes a log file containing all SQL statements that took more than the long_query_time to execute. The time taken to acquire the initial table locks is not counted as execution time.
  If the file_name value is not specified, the information is written to a file with the name of the host machine along with the suffix -slow.log . If a filename is given, but not as an absolute path name, the file is written to the default MySQL data directory.
  You can use the --log-queries-not-using-indexes option to log queries that do not use indexes to the slow query log.
  Queries handled by the query cache are not added to the slow query log, nor are queries that would not benefit from the presence of an index because a database table has no rows or just one row.
• Open Tables
  The number of database tables that are opened independently by each concurrent thread.
  Multiple clients can simultaneously issue queries for a given table. Each table is opened independently by each concurrent thread to ensure that multiple client threads do not have different states on the same table.
  For each concurrent thread, the table must be opened twice if two threads access the same table or if a thread accesses the table twice in the same query. Each concurrent open requires an entry in the table cache. The first time any table is opened, it takes file descriptors for the data file and the index file. Each additional use of the table takes only a descriptor for the data file. The index file descriptor is shared among all threads.
  The cache of open tables should be at the level specified by table_cache entries. The default value is 64 . MySQL may temporarily open more tables to execute queries.
  Unused tables are closed and removed from the table cache when any of the following occurs:
  
  • the cache is full and a thread tries to open a table that is not in the cache
  • the cache contains more than table_cache entries and a thread is no longer using a table
  • a table flushing operation occurs. This happens when someone issues a FLUSH TABLES statement, or executes either the mysqladmin flush-tables or mysqladmin refresh commands
  When the table cache fills up, the server locates a cache entry to release tables that are not currently in use, in least-recently used order. If a new table needs to be opened, but the cache is full and no tables can be released, the cache is temporarily extended as necessary.
  When the cache is in a temporarily extended state and a table goes from a used to an unused state, the table is closed and released from the cache.
• QPSA
  The average number of queries, per second, that must be exceeded before up.time generates an alert.
• Bytes Received
  The number of bytes received by the server.
• Bytes Sent
  The number of bytes sent by the server to all clients.
• Delayed Insert Threads
  Select a comparison method for the Warning and Critical Thresholds. Then, enter the number of delayed insert threads that must be exceeded before up.time sends an alert.
  The DELAYED option for the INSERT statement is a MySQL extension to standard SQL that you can use with clients that cannot wait for the INSERT statement to complete.
  When a client uses the INSERT DELAYED statement, the row is immediately queued to be inserted when the table is not in use by any other thread. INSERT DELAYED also bundles inserts from multiple clients and writes them in one block.
  The DELAYED option has the following constraints:
  
  • it only works with MEMORY tables
  • “ INSERT DELAYED ” can only be used for “ INSERT ” statements that specify value lists, as the server ignores “ DELAYED ” for “ INSERT DELAYED ... SELECT ” statements
  • the server ignores “ DELAYED ” for “ INSERT DELAYED ... ON DUPLICATE UPDATE ” statements
  • you cannot use “ LAST_INSERT_ID() ” to get the “ AUTO_INCREMENT ” value the statement might generate because the statement returns immediately before the rows are inserted
  • “ DELAYED ” rows are not visible to “ SELECT ” statements until they actually have been inserted
• Delayed Errors
  The number of delayed insert threads that had an error.
• Max Used Connections
  The maximum number of connections that have been in simultaneous use since the server was started.
• Open Files
  The number of open files that must be exceeded before up.time generates an alert.
• Open Streams
  The number of open data streams that must be exceeded before up.time generates an alert.
• Table Locks Immediate
  The number of times that a table lock is acquired immediately. For more information on table locks, see the Knowledge Base article“SQL Server Locks.”
• Table Locks Waited
  The number of table locks waited that must be exceeded before up.time generates an alert. For more information on table locks, see the Knowledge Base article“SQL Server Locks.”
• Threads Cached
  The number of threads in the thread cache that must be exceeded before up.time generates an alert.
• Threads Connected
  The maximum number of clients that can be connected to the database at any one time.
• Threads Running
  The number of threads that are running, which can be used to determine whether or not the database is becoming overloaded.
  If the database is overloaded, the monitor will report an increased number of running queries. However, you can have values that exceed this limit for very short times.
• QCache Queries in Cache
  The number of queries in the query cache (QCache) that must be exceeded before up.time generates an alert.
• QCache Inserts
  The number of queries added to the query cache.
  You should compare the value of the qcache_hits to the total number of select queries to determine the current hit rate. You can increase or decrease query_cache_size to find the value which provides optimal performance.
• QCache Hits
  The number of hits to the query cache ( qcache_hits ) to determine the number of query results taken directly from the cache instead of executing them. When this number is exceeded, up.time generates an alert.
  This metric shows the number of query results taken directly from the query cache instead of executing them. You should compare the value of QCache Hits to the total number of your SELECT queries to determine the current hit rate. Then, you can increase or decrease the query_cache_size to find the value which provides optimal performance.
• QCache Lowmem Prunes
  The number of QCache_lowmem_prunes that can be deleted from the cache because of low memory.
  This variable counts the number of queries that have been removed from the cache to free up memory for caching new queries. The query cache removes the least-recently used queries from the cache.
• QCache Not Cached
  The maximum number of queries that are not cached.
• QCache Free Memory
  The amount of free memory for the query cache.
• QCache Free Blocks
  The number of free memory blocks in query cache.
• QCache Table Blocks
  The amount of query cache memory fragmentation.
• Response Time
  Enter the Warning and Critical Response Time thresholds for the overall time required to perform a service check. For more information, see Configuring Warning and Critical Thresholds

• Timing Settings (see Adding Monitor Timing Settings Information for more information)
• Alert Settings (see Monitor Alert Settings for more information)
• Monitoring Period settings (see Monitor Timing Settings for more information)
• Alert Profile settings (see Alert Profiles for more information)
• Action Profile settings (see Action Profiles for more information)

Complete the following fields:

• Port Check (Optional)
  Select this option to open a socket connection that determines whether or not the database is listening on the defined port.
• Username
  The user name that is required to login to the MySQL database.
• Password
  The password that is required to login to the MySQL database.
• Database
  The name of the MySQL database instance.
• Script
  Type or copy the script that you want up.time to match against the database. Use this option if your script is short or will not regularly change. This option is required if you do not have access to the file system on the Monitoring Station.
• Script File
  As an alternative to directly entering a script, enter the full path on the Monitoring Station to the script that this monitor will run against the database.
• Match
  Enter a string that you want to match against the return value from the script.
• Response Time
  Enter the Warning and Critical Response Time thresholds. For more information, see Configuring Warning and Critical Thresholds.

• Timing Settings (see Adding Monitor Timing Settings Information for more information)
• Alert Settings (see Monitor Alert Settings for more information)
• Monitoring Period settings (see Monitor Timing Settings for more information)
• Alert Profile settings (see Alert Profiles for more information)
• Action Profile settings (see Action Profiles for more information)

• Port
  The number of the port on which the Oracle service is listening.
  Note - If you enter a value in the SID field, up.time can capture the port value from the SID of the Oracle instance.
• Port Check (Optional)
  Select this option to open a socket connection that determines whether or not the database is listening on the defined port.
• Username
  The user name that is required to login to the Oracle database.
• Password
  The password that is required to login to the Oracle database.
• SID
  The Oracle System Identifier (SID) that identifies the Oracle instance. The SID defaults to the database name.
  If you enter a value in this field, up.time can capture the number of the port on which Oracle is listening.
• Script File
  Click the Script File check box and then enter the full path on the Monitoring Station to the script that this monitor will run against the database.
  Note - If you configured your database to allow logins with a user name and password and you specify the script file but no login information, the script will fail and an error message appears in the Global Scan panel. The script will run if you have configured your database to allow logins without a user name and password.
• Script
  Select this option and then type or copy the script that you want up.time to against the database into this text box. Use this option if you do not have access to the file system on the Monitoring Station or if your script is short or will not regularly change.
• Match
  Enter a string that you want to match against the return value from the script.
• Response Time
  Enter the Warning and Critical Response Time thresholds. For more information, see Configuring Warning and Critical Thresholds.

• Timing Settings (see Adding Monitor Timing Settings Information for more information)
• Alert Settings (see Monitor Alert Settings for more information)
• Monitoring Period settings (see Monitor Timing Settings for more information)
• Alert Profile settings (see Alert Profiles for more information)
• Action Profile settings (see Action Profiles for more information)

• Port
  The number of the port on which the Oracle service is listening. The default is 1521 .
• Username
  The user name that is required to login to the Oracle database.
• Password
  The password that is required to login to the Oracle database.
• SID
  The Oracle System Identifier (SID) that identifies the Oracle instance. The SID defaults to the database name.
  The SID is a unique name for an Oracle instance to switch between Oracle databases. The SID is included in the CONNECT DATA paths of the connect descriptors in the tnsnames.ora file. As well, the SID is in the definition of the TNS listener in the listener.ora file.
  Note - If you do not complete the Username , Password , SID fields up.time will attempt to connect to the database. If connection fails, the database returns a SQL exception error.
• Full Warning Threshold (Mandatory)
  Enter a value that will change the status of the Oracle Tablespace Check from OK to Warning.
  The warning threshold should be a percentage of the maximum file size, against which the monitor will check data files and log files.
• Full Critical Threshold (Mandatory)
  Enter a value that will change the status of the Oracle Tablespace Check from OK to Warning.
  The critical threshold should be a percentage of the maximum file size, against which the monitor will check data files and log files.
• Response Time
  Enter the Warning and Critical Response Time thresholds for the length of time that a service check takes to complete. For more information, see Configuring Warning and Critical Thresholds.

• Timing Settings (see Adding Monitor Timing Settings Information for more information)
• Alert Settings (see Monitor Alert Settings for more information)
• Monitoring Period settings (see Monitor Timing Settings for more information)
• Alert Profile settings (see Alert Profiles for more information)
• Action Profile settings (see Action Profiles for more information)

• SQL Server Port
  The number of the port on which SQL Server is listening.
  SQL Server uses Static Port Allocation or Dynamic Port Allocation ports. For more information, see the Knowledge Base article“SQL Server Ports.”
• Port Check (Optional)
  Select this option to open a socket connection that determines whether or not the database is listening on the defined port.
  You should perform a port check because SQL Server can communicate statically on a defined or default port, or communicate dynamically on a port assigned by the operating system.
• Username
  The user name that is required to log into the SQL Server database.
• Password
  The password that is required to log into the SQL Server database.
• Instance
  The name of the SQL server instance to which you want to connect.
  You can install multiple versions of Microsoft SQL Server on one computer. When installing a new version of SQL Server 2000, or maintaining an existing installation, you can specify it as:

1. • A default instance of SQL Server
     This instance is identified by the network name of the computer on which it is running. SQL Server version 6.5 or SQL Server version 7.0 servers can operate as default instances. However, a computer can have only one version functioning as the default instance at one time.

• • A named instance of SQL Server
    This instance is identified by the network name of the computer plus an instance name, in the format <computername>\<instancename> .
    Most applications must use SQL Server 2000 client components to connect to a named instance. However, you can use the SQL Server version 7.0 Client Network Utility to configure a server alias name that the SQL Server version 7.0 client components can use to connect to a named instance.
    A computer can concurrently run any number of named instances of SQL Server. An instance name cannot exceed 16 characters.
• Database
  The name of the SQL Server database that you want to monitor.
  up.time views each database along the path /<system>/<instance>/<database> .
  Each instance of SQL Server has four system databases - master , model , tempdb , and msdb - and one or more user databases. Depending on their permissions, users can access some or all of the databases in an instance.
  A connection to an instance is associated with a particular database on the server, called the current database . You can switch from one database to another using the Transact-SQL USE database_name statement.
  up.time gathers information from all of the databases in all instances on a system and aggregates this information in the metrics it returns to you. Unless you must identify a particular database on your system - for example, you have applied a name to the default instance - you should leave the Database field blank.
• Script File
  Click the Script File check box and then enter the full path on the Monitoring Station to the script that this monitor will run against the database.
  Note - If you configured your database to allow logins with a user name and password and you specify the script file but no login information, the script will fail and an error message appears in the Global Scan panel. The script will run if you have configured your database to allow logins without a user name and password.
• Script
  Click the Script checkbox and then type or copy the script that you want up.time to against the database into this text box. Use this option if you do not have access to the file system on the Monitoring Station or if your script is short or will not regularly change.
• Match
  The value to match the script results against, which can be either a string or a regular expression. For more information, see Comparison Methods. For example, you can enter the following in the Match text box:
  ^[OK]+
  Where:
  
  •  ^ means start the match at the beginning of the line.
  •  [OK] is the pattern to match.
  •  + is the pattern to match anywhere on the line.
    The value that your script returns can be a string that you can match to. If you match to the value you checked for, the status of the service monitor is OK. Otherwise, the status of the service monitor is Critical.
• Response Time
  Enter the Warning and Critical Response Time thresholds. For more information, see Configuring Warning and Critical Thresholds.

• Timing Settings (see Adding Monitor Timing Settings Information for more information)
• Alert Settings (see Monitor Alert Settings for more information)
• Monitoring Period settings (see Monitor Timing Settings for more information)
• Alert Profile settings (see Alert Profiles for more information)
• Action Profile settings (see Action Profiles for more information)

• Lock Wait / Sec.
  The amount of time, in seconds, to wait for a database lock. For more information about locks, see the Knowledge Base article“SQL Server Locks.”
• Lock Requests / Sec.
  The number of new database locks and lock conversions that are requested from the lock manager every second. For more information about locks, see the Knowledge Base article“SQL Server 
  Locks.”
• Average Lock Wait Time
  The average time, in milliseconds, that you must wait for database locks to clear before up.time sends an alert.
• User Connections
  The number of user connections that are allowed before up.time sends an alert.
  For example, a single host is running two databases. There are five users logged on to the first database and three users logged on to the second database. The total number of user connections is eight.
• Transactions / Sec.
  In the Warning and Critical threshold fields, enter the number of transactions started for the databases across the host per second.
• Data File(s) Size / KB
  The cumulative size of all the files in all of the databases on the host system.
  This metric is returned from the SQL Server Database object. The Database object provides such information about the database as the amount of free log space available or the number of active transactions in the database. There can be multiple instances of this object.
• Total Latch Wait Time (ms)
  The total time, in milliseconds, that it takes to complete the latch requests that were waiting over the last second.
• Latch Waits / Sec.
  The number of latch requests that were not immediately granted, and which waited before being granted.
• Average Latch Wait Time (ms)
  The average time, in milliseconds, that latch requests had to wait before being granted.
• Maximum Workspace Memory (KB)
  The maximum amount of memory, in kilobytes, that the server has available to execute such processes as sort, bulk copy, hash, and index creation.
  This metric is returned by the SQL Server Memory Manager object, which monitors overall server memory usage. By monitoring overall server memory usage, you can determine whether or not:
  
  • Bottlenecks exist due to a lack of available physical memory for storing frequently accessed data in cache. If so, SQL Server must retrieve the data from the disk.
  • You can improve query performance by adding more memory or by making more memory available to the data cache or to SQL Server internal structures.
• Connection Memory (KB)
  The total amount of dynamic memory, in kilobytes, that the server is using to maintain connections.
• SQL Cache Memory (KB)
  The amount of memory, in kilobytes, that the server is using for the dynamic SQL cache.
• Total Server Memory (KB)
  The total amount of committed memory from the buffer pool, in kilobytes, that the server is using.
• Response Time
  Enter the Warning and Critical Response Time thresholds. If the amount of time taken to perform a check exceeds the defined thresholds, it could indicate a problem that requires investigation.

• Timing Settings (see Adding Monitor Timing Settings Information for more information)
• Alert Settings (see Monitor Alert Settings for more information)
• Monitoring Period settings (see Monitor Timing Settings for more information)
• Alert Profile settings (see Alert Profiles for more information)
• Action Profile settings (see Action Profiles for more information)

• SQL Server Port
  The number of the port on which the SQL Server is listening.
  SQL Server can use static or dynamic ports. For information about SQL ports and how to determine and configure port allocation, see the Knowledge Base article “Configuring SQL Server Ports.”
• Username
  The user name that is required to login to the SQL Server database.
  When a user connects through a Windows user account, SQL Server re-validates the account name and password by contacting a Windows domain controller to determine the network user name. SQL Server then verifies the credentials of the users, and then permits or denies login access.
• Password
  The password that is required to login to the SQL Server database.
  When a user connects with a specified login name and password from a non-trusted connection, SQL Server determines if a SQL Server login account has been set up and if the specified password matches the one previously recorded. If SQL Server does not find a login account, authentication fails and the user receives an error message.
  SQL Server authentication is provided for backward compatibility because applications written for SQL Server version 7.0 or earlier may require the use of SQL Server logins and passwords.
  Note - If you do not complete the Username and Password fields up.time will attempt to connect to the database. If the connection attempt fails, the database returns a SQL exception error.SQL Server can use one of the following authentication modes:
  
  • Windows Authentication Mode
    Enables users to connect to a SQL Server instance through a Windows user account.
  • Mixed Mode
    Enables users who to connect to a SQL Server instance through a Windows account to use either Windows authentication or SQL Server authentication.
• Instance
  The SQL Server instance name. This is usually the default instance.
  You can install multiple instances of SQL Server on one computer. An instance can be:
  
  • The default instance
    This instance is identified by the network name of the computer on which it is running. Applications using client software from earlier versions of SQL Server can connect to a default instance. SQL Server version 6.5 or 7.0 servers can operate as default instances. A computer can have only one version functioning as the default instance at a time.
  • A named instance of SQL Server
    This instance is identified by the network name of the computer plus an instance name, in the format <computername>\<instancename> .
    Most applications must use SQL Server client components to connect to a named instance. However, you can use the SQL Server version 7.0 Client Network Utility to configure a server alias name that the version 7.0 client components can use to connect to a named instance of SQL Server. A computer can concurrently run any number of named instances of SQL Server. A named instance can run at the same time as an existing installation of SQL Server version 6.5 or SQL Server version 7.0. The instance name cannot exceed 16 characters.
  A new instance name must begin with a letter, an ampersand ( & ), or an underscore ( _ ), and can contain numbers, letters, or other characters. Do not use SQL Server sysnames and reserved names as instance names. For example, default is a reserved name and should not be used as an instance name.
  You can have multiple instances of SQL Server installed on one computer. Each instance operates independently from the other instances, and applications can connect to any of the instances.
• Full Warning Threshold
  Enter a percentage of the maximum file size you want to set as your warning threshold.
• Critical Warning Threshold
  Enter a percentage of the maximum file size you want to set as your critical threshold.
• Response Time
  Enter the Warning and Critical Response Time thresholds for the length of time a service check takes. For more information, see Configuring Warning and Critical Thresholds

• Timing Settings (see Adding Monitor Timing Settings Information for more information)
• Alert Settings (see Monitor Alert Settings for more information)
• Monitoring Period settings (see Monitor Timing Settings for more information)
• Alert Profile settings (see Alert Profiles for more information)
• Action Profile settings (see Action Profiles for more information)

• Port
  The number of the port number on which the database is listening. The default is 5000 .
• Port Check (Optional)
  Select this option to open a socket connection that determines whether or not the database is listening on the defined port.
• Username
  The user name that is required to login to the database.
• Password
  The password that is required to login to the database.
• Database
  The name of the Sybase database to which you want to connect.
• Script
  Click the Script checkbox and then type or copy the script that you want up.time to against the database into this text box. Use this option if you do not have access to the file system on the Monitoring Station or if your script is short or will not regularly change.
• Script File
  Click the Script File check box and then enter the full path on the Monitoring Station to the script that this monitor will run against the database.
  Note - If you configured your database to allow logins without a user name and password and you specify the script file but no login information, the script will fail and an error message appears in the Global Scan panel. The script will run if you have configured your database to allow logins without a user name and password.
• Match (Regular Expression)
  Enter a regular expression that you want to match against the string returned from the database. If the string matches, the status is OK. Otherwise, the status is Critical.
• Response Time
  Enter the Warning and Critical Response Time thresholds. For more information, see Configuring Warning and Critical Thresholds.

• Timing Settings (see Adding Monitor Timing Settings Information for more information)
• Alert Settings (see Monitor Alert Settings for more information)
• Monitoring Period settings (see Monitor Timing Settings for more information)
• Alert Profile settings (see Alert Profiles for more information)
• Action Profile settings (see Action Profiles for more information)