Schedule demo

Oracle Database Servers


Overview

Applications Manager's Database monitoring tool provides out-of-the-box performance metrics and helps you visualize the health and availability of an Oracle Database server farm. Database administrators can login to the web client and visualize the status and Oracle performance metrics.

Creating a new Oracle DB monitor

Supported Versions: Applications Manager supports monitoring of Oracle database servers of versions 9i, 10g, 10.1.3, 11g, 12c, 18c, 19c, 21c & 23ai.

Prerequisites for monitoring Oracle DB metrics:Click here

Using the REST API to add a new Oracle DB monitor:Click here

Follow the given steps to create a Oracle database server monitor:

  1. Click on New Monitor link.
  2. Select Oracle DB Server.
  3. Enter the IP Address or hostname of the host.
  4. Enter the Subnet Mask of the network.
  5. Enter the Port where the server is running.
  6. Specify the Discovery Interval in minutes to define the interval at which child resources are automatically discovered and monitored.
  7. Enter the polling interval time in minutes.
  8. If you are adding a new monitor from an Central Server, select a Probe Server.
  9. Provide the user name of the admin user ('system' is the default username) and its corresponding password.
  10. Provide a valid System Identifier / Host Connection String.
  11. Select the 'SSL is enabled' option if you have enabled SSL authentication for a given port in Oracle.
  12. Choose Discover Pluggable Database (PDB) as 'Yes' to discover and monitor pluggable databases associated with the Oracle DB server (Applicable only for CDB instance of an Oracle Multitenancy-enabled server). To add only the required PDB(s), choose 'No' and add the PDB(s) via Add PDB link available under 'PDB' tab in Oracle DB monitor.
  13. Provide the Socket Read Timeout and Query Execution Timeout values in seconds.
  14. Choose the Monitor Group from the combo box with which you want to associate Oracle database server Monitor (optional). You can choose multiple groups to associate your monitor.
  15. Click Add Monitor(s). This discovers Oracle database server from the network and starts monitoring them.

Monitored Parameters

Go to the Monitors Category View by clicking the Monitors tab. Click on Oracle Server under the Database Servers Table. Displayed is the Oracle servers bulk configuration view in three tabs:

  • Availability tab gives the availability history for the past 24 hours or 30 days.
  • Performance tab gives the health status and events for the past 24 hours or 30 days.
  • List view enables you to perform bulk admin configurations.
Note: To create a new Oracle database monitor, you should have admin privileges. Minimum User Privileges → user with CONNECT and SELECT_CATALOG_ROLE roles.

Click on the monitor name to see all the server details listed under the following tabs:

Note: The server details marked with * symbol is supported in Oracle database servers version 10g and above.

Overview

Note: Metrics marked with ** are the only Database Status metrics that are mapped under Settings → Performance Polling.

Applications Manager allows you to enable/disable data collection of the selected metrics. Once enabled, you can also customize the polling interval of these metrics. To enable metrics monitoring:

  • Go to the Settings tab.
  • Click Performance Polling under Discovery and Data Collection.
  • Under Performance Polling, click on the Optimize Data Collection tab.
  • Select Oracle from the Monitor Type drop-down menu.
  • For Oracle DB Links metrics, select Oracle DB Links from the Metric Name drop-down menu. For Average Executions**, select Average Executions for database instance and select Database Size Statistics for Database Size** monitoring.
  • Select how you wish to configure the queries:
    • By Monitor Type - This will be the default polling status, for any new monitor added. All the monitors of this type, will have the default polling status, until any exclusive customization is done for the monitor. You can choose between three different polling settings: Never collect data, Collect data in every polling and Collect data at customized time interval. Changing the polling status of 'Monitor Type', will also change any configuration done for its 'Monitors'.
    • By Monitors - Use this option to change the polling status of any particular monitor(s).
Note: To ignore certain Oracle log alerts, go to Settings → Performance Polling → Database Servers, and enter the necessary errors in the Errors to Ignore for Oracle Alert Log field. By enabling the 'Clear scheduled job run status alerts in the next poll' option, any critical or warning alert that is generated for the Last Run Status attribute will be automatically cleared in the next poll.
 
ParametersTypeDescription
Monitor Information
NameStringName of the Oracle server monitor
Oracle VersionStringThe version of the Oracle Database.
Oracle Start TimeStringThe time when Oracle server was started.
AvailabilityStringThe status of the database server - available or not available.
Today's Availability
Current StatusStringAvailability history graph with uptime
Connection Statistics
Response TimeStringThe time taken to connect to the database.
Session Activity
Number of Session UsersNumericGraph for the number of users executing an SQL Statement. vs time
Table spaces with least free bytes
NameStringThe name of the table space.
Free Bytes (MB)NumericThe free space available in bytes.
% of Free BytesNumericThe percentage of free space available in bytes.
Database Details
VersionNumericVersion of the database.
DB TypeStringIndicates whether the added Oracle DB Sever is a CDB instance or Non-CDB instance.
Database Created TimeStringCreation time of the database.
Open ModeStringIndicates the Open mode of the Instance which can be either Read Write or Read.
FRA StatusStringIndicates whether Flashback is enabled for the database instance.
Log ModeStringThe two Log Modes are:
  • NOARCHIVELOG - When you run your database in NOARCHIVELOG mode, you disable the archiving of the redo log.
  • ARCHIVELOG - When you run a database in ARCHIVELOG mode, you enable the archiving of the redo log.
DB RoleStringCurrent role of the database:
  • LOGICAL STANDBY
  • PHYSICAL STANDBY
  • PRIMARY
Control File typeStringType of control file:
  • STANDBY - Indicates that the database is in standby mode
  • CLONE - Indicates a clone database
  • BACKUP | CREATED - Indicates the database is being recovered using a backup or created control file
  • CURRENT - database is available for general use
Switch over statusStringIndicates whether switchover is allowed:
  • NOT ALLOWED - Either this is a standby database and the primary database has not been switched first or this is a primary database and there are no standby databases.
  • SESSIONS ACTIVE - Indicates that there are active SQL sessions attached to the primary or standby database that need to be disconnected before the switchover operation is permitted. Query the V$SESSION view to identify the specific processes that need to be terminated.
  • SWITCHOVER PENDING - This is a standby database and the primary database switchover request has been received but not processed.
  • SWITCHOVER LATENT - The switchover was in pending mode, but did not complete and went back to the primary database.
  • TO PRIMARY - This is a standby database and is allowed to switch over to a primary database.
  • TO STANDBY - This is a primary database and is allowed to switch over to a standby database.
  • RECOVERY NEEDED - This is a standby database that has not received the switchover request.
  • PREPARING SWITCHOVER - Either this is a primary database that is accepting redo data from a logical standby database in preparation for switch over to the logical standby database role, or it is a logical standby database sending redo data to a primary database and other standby databases in preparation for switch over to the primary database role. In the latter case, a completed dictionary has already been sent to the primary database and other standby databases.
  • PREPARING DICTIONARY - This is a logical standby database that is sending redo data to a primary database and other standby databases in the configuration in preparation for switch over to the primary database role.
  • TO LOGICAL STANDBY - This is a primary database that has received a complete dictionary from a logical standby database.
  • FAILED DESTINATION -On a primary database, this status indicates that one or more standby destinations are in an error state.
  • RESOLVABLE GAP - On a primary database, this status indicates that one or more standby databases have a redo gap that can be automatically resolved by fetching the missing redo from the primary database or from another standby database.
  • UNRESOLVABLE GAP - On a primary database, this status indicates that one or more standby databases have a redo gap that cannot be automatically resolved by fetching the missing redo from the primary database or from another standby database.
  • LOG SWITCH GAP - On a primary database, this status indicates that one or more standby databases are missing redo due to a recent log switch.
Protection ModeStringProtection mode currently in effect for the database:
  • MAXIMUM PROTECTION - Database is running in maximized protection mode
  • MAXIMUM AVAILABILITY - Database is running in maximized availability mode
  • RESYNCHRONIZATION - Database is running in resynchronization mode
  • MAXIMUM PERFORMANCE - Database is running in maximized protection mode
  • UNPROTECTED - Database is unprotected (this normally occurs when the primary database is mounted and not open)
Open reset logsStringIndicates whether the next database open allows or requires the resetlogs option
  • NOT ALLOWED
  • ALLOWED
  • REQUIRED
Guard StatusStringProtects data from being changed:
  • ALL - Indicates all users other than SYS are prevented from making changes to any data in the database.
  • STANDBY - Indicates all users other than SYS are prevented from making changes to any database object being maintained by logical standby.
  • NONE - Indicates normal security for all data in the database.
Force loggingStringIndicates whether the database is under force logging mode (YES) or not (NO).
Database Status
Database Size **NumericSize of the database in Megabytes.
Free Space **NumericSize of free extents in all tablespaces in the database (Size in MB).
Used Space **NumericSize of used extents in all tablespaces in the database (Size in MB).
Used Space Percentage **NumericPercentage of used extents in all tablespaces in the database.
Free Space Percentage **NumericPercentage of free extents in all tablespaces in the database.
Database Block SizeNumericThis refers to the lowest possible storage area for an Instance in bytes.
Invalid/Unusable Index CountNumericNumber of Invalid/Unusable indexes in the database.
Average Executions **NumericThis is the average number of executions that happen during the execution of every SQL Statement.
ReadsNumericRefers to the number of reads from the database.
WritesNumericRefers to the number of writes to the database.
Database CPU Time RatioNumericRatio of DB CPU time to DB time. Ideal value is greater than 90%.
Data transferred via SQL*NetNumericTotal data sent and received via SQL*Net services in MB.
Current SCNNumericCurrent System Change Number (SCN) of the database.
Hit Ratio
Buffer Cache Hit RatioNumericThe buffer cache hit ratio calculates how often a requested block has been found in the buffer cache without requiring disk access. It is the percentage of cache hits taking place from the buffer cache.
Data Buffer Hit RatioNumericThe Data Buffer Hit Ratio Oracle metric is a measure of the effectiveness of the Oracle data block buffer. It is the percentage of logical reads taking place from the data block.
Data DictionaryNumericThe ratio of the data gets to the data misses in the row cache is Data Dictionary Hit Ratio.
LibraryNumericThe Library cache stores all shared SQL and PL/SQL blocks, along with their parse trees. In OLTP environments where a large numbers of users are entering and exchanging data, there is a great chance for overlapping the parse and execute needs of those different queries. Such an overlap in the library is called a cache hit and the ratio determined to the misses and hits is called Library Cache Hit Ratio.
SGA Details
Buffer Cache SizeNumericThe total size of the Buffer Cache given in bytes.
Shared Pool SizeNumericThe size of the shared pool given in bytes.
Shared Pool Used SizeNumericAmount of space utilized in the shared pool in percentage.
Redolog Buffer SizeNumericThe size of the buffers for the Redo Logs in mb.
Library Cache SizeNumericThe size of the Library Cache given in bytes.
Data Dictionary Cache SizeNumericThe cache size of the data dictionary or row cache in bytes.
SQL Area SizeNumericThe size of the SQL Area for usage of SQL/PL statements in bytes.
Fixed Area SizeNumericThe size of the SGA, which is fixed throughout the instance.
Oracle DB Links
DB link nameStringName of the database link
OwnerStringOwner of the database link
UserStringName of the user when logging in
Oracle Net connect stringStringHost Name
Creation timeStringCreation time of the database link
Invalid Objects
OwnerStringOwner of the invalid dba object.
Object NameStringName of the invalid object.
StatusStringStatus of the invalid object.
Invalid/Unusable Indexes
Index NameString Name of the index
Tablespace NameString Name of the tablespace containing the index
OwnerString Owner of the index
Table NameString Name of the indexed object
Index StatusStringIndicates whether a nonpartitioned index is VALID or UNUSABLE. We list all UNUSABLE indexes.
Datafiles Utilization
Maximum Allocated DatafilesNumericThe maximum number of database files that can be opened for this database.
Datafiles UsedNumericNumber of datafiles used in the database.
Datafiles AvailableNumericNumber of datafiles available in the database.
Datafiles Used PercentageNumericThe percentage of the used datafiles in the database.
Datafiles Available PercentageNumericThe percentage of the free datafiles in the database.

 

PDB

ParameterTypeDescription
Pluggable Database (PDB) Details
NameStringName of the pluggable database.
Open ModeStringDisplays the open mode information like MOUNTED, READ WRITE, READ ONLY.
Database SizeNumericSize of the pluggable database in MB.
Database Block SizeNumericSize of the pluggable database block in MB.

By clicking over the PDB name, you will be redirected to the Oracle PDB monitoring dashboard.

Tablespace

Applications Manager allows you to enable/disable data collection of the Tabespace metrics. Once enabled, you can also customize the polling interval of these metrics. To enable metrics monitoring:

  • Go to the Settings tab.
  • Click Performance Polling under Discovery and Data Collection.
  • Under Performance Polling, click on the Optimize Data Collection tab.
  • Select Oracle from the Monitor Type drop-down menu.
  • For metrics of the Tablespace Details and Table Space Status, select TableSpace Statistics from the Metric Name drop-down menu. For metrics of the Performance of Data Files, select Performance of Data Files. For metrics of the Objects Approaching MAX Extents, select Objects Approaching MAX Extents.

    Note: Data collection is scheduled to take place during each poll. Users have the option to change the schedule using the 'Optimize Data Collection' feature. In the event of Objects approaching MAX Extents, the default data collection time is set to 24 hours.

  • Select how you wish to configure the queries:
    • By Monitor Type - This will be the default polling status, for any new monitor added. All the monitors of this type, will have the default polling status, until any exclusive customization is done for the monitor. You can choose between three different polling settings: Never collect data, Collect data in every polling and Collect data at customized time interval. Changing the polling status of 'Monitor Type', will also change any configuration done for its 'Monitors'.
    • By Monitors - Use this option to change the polling status of any particular monitor(s).
ParameterTypeDescription
Table Space Details
NameStringRefers to the name of the Table space.
Allocated BytesNumericRefers to the size of the Table space in bytes.
Allocated BlocksNumericRefers to the number of allocated blocks in Table space.
Data FilesNumericRefers to the number of data files in Table space.
Table Space Status
NameStringRefers to the name of the Table space.
StatusStringTablespace status: ONLINE, OFFLINE, or INVALID (tablespace has been dropped)
Free BytesNumericRefers to the available free space in bytes.
Free BlocksNumericRefers to the number of free blocks in Table space.
ReadsNumericRefers to the number of reads from the Table space.
WritesNumericRefers to the number of writes on the Table space.
Read TimeNumericTime taken for a single read from the Table space.
Write TimeNumericTime taken for a single write on the Table space.
Performance of Data Files
Data File NameStringName and location of the data file.
Table Space NameStringName of the Table space.
StatusStringIf a data file is a part of the system table space, its status is SYSTEM (unless it requires recovery). If a data file in a non-SYSTEM table space is online, its status is ONLINE. If a data file in non-SYSTEM table space is offline, its status can be either OFFLINE OR RECOVER.
AutoExtendStringIndicates whether AutoExtend is enabled for this data file or not.
Created BytesNumericSize of the Data file in bytes.
ReadsNumericRefers to the number of reads from the Data file.
WritesNumericRefers to the number of writes to the Data file.
Average Read TimeNumericRefers to the average read time.
Average Write TimeNumericRefers to the average write time.
Objects Approaching MAX Extents
OwnerStringOwner name of the table space.
TableSpace NameStringName of the TableSpace.
Segment NameStringName of the segment approaching maximum extents
Segment TypeStringThe type of segment approaching maximum extents
ExtentsNumericNumber of extents allocated to the segment
Max ExtentsNumericMaximum allowed extents that can be filled in a segment
Next Extent (MB)NumericNext extent size in MB

Session

Applications Manager allows you to enable/disable data collection of Session metrics. Once enabled, you can also customize the polling interval of these metrics. To monitor query metrics:

  • Go to the Settings tab.
  • Click Performance Polling under Discovery and Data Collection.
  • Under Performance Polling, click on the Optimize Data Collection tab.
  • Select Oracle from the Monitor Type drop-down menu.
  • For Session Details and Session Wait metrics, select Session Details from the Metric Name drop-down menu. For the Users metrics, select Users from the Metric Name drop-down
  • Select how you wish to configure the queries:
    • By Monitor Type - This will be the default polling status, for any new monitor added. All the monitors of this type, will have the default polling status, until any exclusive customization is done for the monitor. You can choose between three different polling settings: Never collect data, Collect data in every polling and Collect data at customized time interval. Changing the polling status of 'Monitor Type', will also change any configuration done for its 'Monitors'.
    • By Monitors - Use this option to change the polling status of any particular monitor(s).
ParameterTypeDescription
Session Metrics
TOTAL SESSIONSNumericTotal number of sessions.
ACTIVE SESSIONSNumericSessions currently executing SQL.
INACTIVE SESSIONSNumericSessions that are inactive and either have no configured limits or have not yet exceeded the configured limits.
KILLED SESSIONSNumericSessions marked to be terminated.
CACHED SESSIONSNumericSessions temporarily cached for use by Oracle*XA.
SNIPED SESSIONSNumericAn inactive session that has exceeded some configured limits (for example, resource limits specified for the resource manager consumer group or idle_time specified in the user's profile). Such sessions will not be allowed to become active again.
Session Details
IDStringSession Identifier for the connected session.
StatusStringCurrent status: ONLINE, OFFLINE, or INVALID (tablespace has been dropped).
MachineStringName of the operating system user.
User NameStringName of the Oracle process user.
Elapsed TimeNumericTime elapsed in seconds after which the user has logged into the oracle server.
CPU UsedNumericCPU centiseconds (divide by 100 to get real CPU seconds) used by this session.
Memory SortsNumericNumber of memory sorts performed.
Table ScansNumericNumber of table scans performed.
Physical ReadsNumericPhysical reads for the session.
Logical ReadsNumericSum of consistent gets and db block gets.
CommitsNumericNumber of commits made by user in a second.
CursorNumericNumber of cursor currently in use.
Buffer Cache Hit RatioNumericPercentage of session logical reads taking place from the buffer (1 - physical reads/session logical reads * 100).
Session Waits
IDStringSession Identifier for the connected session.
User NameStringName of the Oracle process user.
EventNumericResource or event for which the session is waiting
StateNumericWait state:
0 - WAITING (the session is currently waiting)
-2 - WAITED UNKNOWN TIME (duration of last wait is unknown)
-1 - WAITED SHORT TIME (last wait <1/100th of a second)
>0 - WAITED KNOWN TIME (WAIT_TIME = duration of last wait)
Wait TimeNumericA non-zero value is the session's last wait time (in milliseconds). A zero value means the session is currently waiting.
Seconds in WaitNumericIf WAIT_TIME = 0, then SECONDS_IN_WAIT is the seconds spent in the current wait condition. If WAIT_TIME > 0, then SECONDS_IN_WAIT is the seconds since the start of the last wait, and SECONDS_IN_WAIT - WAIT_TIME / 100 is the active seconds since the last wait ended.
Users
UsernameStringThe username assigned to the user.
Expiry DateStringThe date when the user account expires.
Days to ExpiryNumericThe number of days to account expiration.
Account StatusStringThe current status of the user account.
User ProfileStringThe profile name of user.

Performance

ParameterTypeDescription
Active Long Running Query Details/ Inactive Long Running Query Details
Session IDNumericUnique Session identifier
Serial NumberNumericThe serial number of the session.
Start TimeStringThe approximate start time of the session's last active query.
Elapsed Time(min)NumericThe time taken for the query execution.
UsernameStringThe database username associated with the session.
Program NameStringThe name of the program that is connected to the database.
Module NameStringThe application module or component that is running the session.
QueryStringThe actual SQL statement being executed by the session
Query Execution Plan Details
SQL IDNumericA unique identifier for a SQL statement
Schema NameStringThe schema in which the SQL statement was parsed.
Old Hash ValueNumericThe hash value of the execution plan for the SQL statement from historical data.
Current Hash ValueNumericThe hash value of the current execution plan for the SQL statement.
Old CostNumericThe optimized cost associated with the historical execution plan.
Current CostNumericThe optimized cost associated with the current execution plan.
Cost DifferenceNumericThe absolute difference between the current and old optimizer costs.
QueryStringThe actual SQL statement text.

Rollback & Corrupted blocks

Applications Manager allows you to enable/disable data collection of the metrics of the Blocks Corrupted. Once enabled, you can also customize the polling interval of these metrics. To enable metrics monitoring:

  • Go to the Settings tab.
  • Click Performance Polling under Discovery and Data Collection.
  • Under Performance Polling, click on the Optimize Data Collection tab.
  • Select Oracle from the Monitor Type drop-down menu.
  • For the metrics of Blocks Corrupted, select Backup jobs and Blocks Corrupted from the Metric Name drop-down menu.
  • Select how you wish to configure the queries:
    • By Monitor Type - This will be the default polling status, for any new monitor added. All the monitors of this type, will have the default polling status, until any exclusive customization is done for the monitor. You can choose between three different polling settings: Never collect data, Collect data in every polling and Collect data at customized time interval. Changing the polling status of 'Monitor Type', will also change any configuration done for its 'Monitors'.
    • By Monitors - Use this option to change the polling status of any particular monitor(s).

Note: Data collection is scheduled to take place once every 12 hours. Users can utilize the 'Optimize Data Collection' option to modify the schedule.

ParameterTypeDescription
Rollback Segment
Segment NameStringName of the rollback segment.
Table Space NameStringName of the tablespace containing the rollback segment.
StatusStringONLINE if the segment is online, or PENDING OFFLINE if the segment is going offline but some active (distributed) transactions are using the rollback segment. When the transaction(s) complete, the segment goes OFFLINE.
Current SizeNumericCurrent size in bytes of the rollback segment.
Initial ExtentNumericInitial extent size in bytes.
Next ExtentNumericSecondary extent size in bytes.
Min. ExtentNumericMinimum number of extents.
Max. ExtentNumericMaximum number of extents.
Hit RatioNumericRatio of gets to waits. This should be >= 99%.
HWMSizeNumericHigh Water Mark of rollback segment size.
ShrinksNumericNumber of times rollback segment shrank, eliminating one or more additional extents each time.
WrapsNumericNumber of times rollback segment wraps from one extent to another.
ExtendNumericNumber of times rollback segment was extended to have a new extent.
Blocks Corrupted
File NumberNumericDatafile number
Data File NameStringName of the database file.
Block NumberNumericFirst block of the corrupted range
Number of corrupted blocksNumericNumber of contiguous blocks in the corrupted range
Type of block corruptionStringType of block corruption in the datafile:
  • ALL ZERO - Block header on disk contained only zeros. The block
    may be valid if it was never filled and if it is in an Oracle7 file. The
    buffer will be reformatted to the Oracle8 standard for an empty
    block.
  • FRACTURED - Block header looks reasonable, but the front and back
    of the block are different versions.
  • CHECKSUM - optional check value shows that the block is not
    self-consistent. It is impossible to determine exactly why the check
    value fails, but it probably fails because sectors in the middle of the
    block are from different versions.
  • CORRUPT - Block is wrongly identified or is not a data block (for
    example, the data block address is missing)
  • LOGICAL - Specifies the range is for logically corrupt blocks.
    CORRUPTION_CHANGE# will have a nonzero value.
Fast Recovery Area
FRA NameStringCurrent location of the FRA.
FRA Space LimitNumericThe maximum amount of disk space that the database can use for the flash recovery area (in MB).
FRA Space UsedNumericThe amount of disk space used by flash recovery area files created in current and all previous flash recovery areas (in MB).
Used PercentageNumericThe percentage of disk space used by flash recovery area files created in current and all previous flash recovery areas.
FRA Space Reclaimable LimitNumericThe amount of flash recovery area that is reclaimable (in MB).
FRA Reclaimable PercentageNumericThe percentage of the amount of flash recovery area that is reclaimable.
FRA Actual Used PercentageNumericThe percentage of the amount of flash recovery area used, including reclaimable space.

SGA

ParameterTypeDescription
SGA Performance: Graph displaying value (in %) of Buffer Cache Hit Ratio, Data Buffer Hit Ratio, Data Dictionary Hit Ratio and Library Hit Ratio vs time
Buffer Cache Hit RatioNumericPercentage of cache hits taking place from the buffer cache.
Data Buffer Hit RatioNumericWhen a scan of the buffer cache shows that there are no free buffers, Database Block Writer determines which blocks to be eliminated based on a least recently used algorithm or LRU. Having a block required by a user process in the buffer cache already is called a buffer cache hit or is determined as a ratio. Hits are good because they reduce the amount of disk I/O required for the user process.
Data Dictionary Hit RatioNumericThe purpose of the row or dictionary cache is to store rows of information from the data dictionary in memory for faster access. The row cache is designed to hold the actual rows of data from objects in data dictionary. While this data is held in the row cache, the users of the database may access that information more quickly than if Oracle had to read the data into memory from disk. The ratio of the data gets to the data misses in the row cache is Data Dictionary Hit Ratio.
Library Hit RatioNumericThe Library cache stores all shared SQL and PL/SQL blocks, along with their parse trees. In OLTP environments where a large numbers of users are entering and exchanging data, there is a great chance for overlapping the parse and execute needs of those different queries. Such an overlap in the library is called a cache hit and the ratio determined to the misses and hits is called Library Cache Hit Ratio.
SGA Details
Buffer Cache SizeNumericThe total size of the Buffer Cache given in bytes.
Shared Pool SizeNumericThe size of the shared pool given in bytes.
Shared Pool Used SizeNumericAmount of space utilized in the shared pool in percentage.
Redolog Buffer SizeNumericThe size of the buffers for the Redo Logs in bytes.
Library Cache SizeNumericThe size of the Library Cache given in bytes.
Data Dictionary Cache SizeNumericThe cache size of the data dictionary or row cache in bytes.
SQL Area SizeNumericThe size of the SQL Area for usage of SQL/PL statements in bytes.
Fixed Area SizeNumericThe size of the SGA, which is fixed throughout the instance.
SGA Status
Buffer Hit RatioNumericWhen a scan of the buffer cache shows that there are no free buffers, Database Block Writer determines which blocks to be eliminated based on a least recently used algorithm or LRU. Having a block required by a user process in the buffer cache already is called a buffer cache hit or is determined as a ratio. Hits are good because they reduce the amount of disk I/O required for the user process.
Data Dictionary Hit RatioNumericThe purpose of the row or dictionary cache is to store rows of information from the data dictionary in memory for faster access. The row cache is designed to hold the actual rows of data from objects in data dictionary. While this data is held in the row cache, the users of the database may access that information more quickly than if Oracle had to read the data into memory from disk. The ratio of the data gets to the data misses in the row cache is Data Dictionary Hit Ratio.
Library Hit RatioNumericThe Library cache stores all shared SQL and PL/SQL blocks, along with their parse trees. In OLTP environments where a large numbers of users are entering and exchanging data, there is a great chance for overlapping the parse and execute needs of those different queries. Such an overlap in the library is called a cache hit and the ratio determined to the misses and hits is called Library Cache Hit Ratio.
Free MemoryNumericRefers to the size of the free memory in bytes.

Query

Query attributes are not monitored by default. Applications Manager allows you to enable/disable data collection of query metrics. Once enabled, you can also customize the polling interval of these metrics. To monitor query metrics:

  • Go to the Settings tab.
  • Click Performance Polling under Discovery and Data Collection.
  • Under Performance Polling, click on the Optimize Data Collection tab.
  • Select Oracle from the Monitor Type drop-down menu.
  • Select Buffer Gets-Top Queries (or) Disk Reads-Top Queries from the Metric Name drop-down menu.
  • Select how you wish to configure the queries:
    • By Monitor Type - This will be the default polling status, for any new monitor added. All the monitors of this type, will have the default polling status, until any exclusive customization is done for the monitor. You can choose between three different polling settings: Never collect data, Collect data in every polling and Collect data at customized time interval. Changing the polling status of 'Monitor Type', will also change any configuration done for its 'Monitors'.
    • By Monitors - Use this option to change the polling status of any particular monitor(s).
  • Choose the time range within which the history data has to be displayed, by clicking the Showdropdown. The available time period options are:
    • Last Polled Data: Displays the recently polled data.
    • Last 7 Days Data: Displays the last 7 days data.
    • Last 30 Days Data: Displays the last 30 days data.
    • Custom Period: Using this option, you can choose the From and To limit in calendar within which the data has to be collected and displayed.
ParameterTypeDescription
Buffer Gets - Top 10
SQL IDNumericThe unique identifier assigned to the SQL statement.
Child NumberNumericThe identifier for the specific child cursor under the given SQL ID.
ServiceStringThe name of the database service through which the query was executed.
QueryStringFirst thousand characters of the SQL text for the current cursor
Buffer GetsNumericNumber of buffer gets for the child cursor
ExecutionsNumericNumber of executions that took place on the object since it was brought into the library cache
Buffer Gets per ExecutionsNumericThe ratio of buffer gets to execution in the current polling interval
Last Active TimeNumericThe last time the SQL statement was active (executed).
Disk Reads
SQL IDNumericThe unique identifier assigned to the SQL statement.
Child NumberNumericThe identifier for the specific child cursor under the given SQL ID.
ServiceStringThe name of the database service through which the query was executed.
QueryStringFirst thousand characters of the SQL text for the current cursor
Disk ReadsNumericNumber of disk reads for this child cursor
ExecutionsNumericNumber of executions that took place on this object since it was brought into the library cache
Disk Reads per ExecutionsNumericThe ratio of disk reads to execution in the current polling interval
Last Active TimeNumericThe last time the SQL statement was active (executed).

Lock Statistics

Lock statistics are not monitored by default. Applications Manager allows you to enable/disable data collection of Lock statistics. Once enabled ,you can also customize the polling interval of these metrics. To monitor Lock statistics:

  • Go to the Settings tab.
  • Click Performance Polling under Discovery and Data Collection.
  • Under Performance Polling, click on the Optimize Data Collection tab.
  • Select Oracle from the Monitor Type drop-down menu.
  • Select Lock and Wait Statistics from the Metric Name drop-down menu.
  • Select how you wish to configure the Lock and Wait Statistics:
    • By Monitor Type - This will be the default polling status, for any new monitor added. All the monitors of this type, will have the default polling status, until any exclusive customization is done for the monitor. You can choose between three different polling settings: Never collect data, Collect data in every polling and Collect data at customized time interval. Changing the polling status of 'Monitor Type', will also change any configuration done for its 'Monitors'.
    • By Monitors - Use this option to change the polling status of any particular monitor(s).
ParameterTypeDescription
Sessions under lock
IdNumericSession identifier of Session holding a lock
Serial NumericSession serial number. Used to uniquely identify a session's objects. Guarantees that session-level commands are applied to the correct session objects if the session ends and another session begins with the same session ID.
MachineStringOperating system machine name.
PROGRAMStringOperating system program name.
Lock Wait StringAddress of lock waiting for; null if none.
Sessions waiting for a lock
Waiting Session IDNumericID of Session waiting for lock.
Holding Session IDNumericID of Session holding lock.
Lock TypeStringThe lock type.
Mode Held StringThe mode held.
Mode RequestedStringThe mode requested.
Lock ID1, ID2StringThe Lock IDs.
Lock Statistics
Object NameStringName of the locked object
Session Id NumericThe session ID of a locked object.
Serial   NumericThe session serial number. Used to uniquely identify a session's objects.
Lock ModeNumericThe lock mode in which the session holds the lock.
OS Process IDNumericThe operating system process identifier.
Blocked Session TimeNumericIf the session STATUS is currently ACTIVE, then the value represents the elapsed time in minutes since the session has become active. If the session STATUS is currently INACTIVE, then the value represents the elapsed time in minutes since the session has become inactive.
Time of logonStringLogin time.
Blocked Sessions
Waiting Session SerialNumericSerial number of the session waiting for lock.
Waiting Session IDNumericSession ID of the session waiting for lock.
Blocking Session IDNumericSession ID of the blocking session.
Waiting QueryStringThe SQL query that waiting for lock.
Blocked TimeNumericIf the session STATUS is currently ACTIVE, then the value represents the elapsed time (in minutes) since the session has become active. If the session STATUS is currently INACTIVE, then the value represents the elapsed time (in minutes) since the session has become inactive.
Instance IDNumericID of the database instance.
OS Process IDNumericThe operating system process ID.
MachineStringName of the machine where the blocking session is running.
ProgramStringName of the program where the blocking session is running.
LogOn TimeStringDate and time of logon.

Jobs & Backup

Applications Manager allows you to enable/disable data collection of the metrics of the Blocks Corrupted. Once enabled, you can also customize the polling interval of these metrics. To enable metrics monitoring:

  • Go to the Settings tab.
  • Click Performance Polling under Discovery and Data Collection.
  • Under Performance Polling, click on the Optimize Data Collection tab.
  • Select Oracle from the Monitor Type drop-down menu.
  • For metrics of the Blocks Corrupted, select Backup jobs and Blocks Corrupted from the Metric Name drop-down menu. For the metrics of Schedule jobs details and Schedule Jobs Stats select the Oracle Scheduled Jobs metric.
    Note:
    • Data collection for Backup Jobs and Blocks Corrupted is scheduled to occur every 12 hours. Users can utilize the 'Optimize Data Collection' option to modify the schedule.
    • Users can manually clear critical / warning alerts that are created for the Last Run Status attribute by enabling the 'Clear Last Run Status alert ' option present in the actions dropdown of the Schedule Jobs Details table under the Jobs and Backup tab.
  • Select how you wish to configure the queries:
    • By Monitor Type - This will be the default polling status, for any new monitor added. All the monitors of this type, will have the default polling status, until any exclusive customization is done for the monitor. You can choose between three different polling settings: Never collect data, Collect data in every polling and Collect data at customized time interval. Changing the polling status of 'Monitor Type', will also change any configuration done for its 'Monitors'.
    • By Monitors - Use this option to change the polling status of any particular monitor(s).
ParameterTypeDescription
Schedule jobs details
Job NameStringName of the job.
Current StateStringCurrent state of the job (DISABLED, RETRY SCHEDULED, SCHEDULED, RUNNING, COMPLETED, BROKEN, FAILED, REMOTE, SUCCEEDED, CHAIN_STALLED)
Last Run StatusStringStatus of the job run.
Last Run DateStringLast date on which the job started running.
Last Run Duration  (sec)NumericAmount of time the job took to complete during the last run (in seconds)
Next Run DateStringNext date on which the job is scheduled to run.
Schedule Jobs Stats
Job NameStringName of the job.
Run CountNumericNumber of times the job has run.
Failure CountNumericNumber of times the job has failed to run.
Retry CountNumericNumber of times the job has retried, if it is retrying.
Elapsed TimeNumericElapsed time since the job was started (in secs).
Running Backup Jobs Count
DB FULLNumericNumber of jobs running of type DB FULL.
RECVR AREANumericNumber of jobs running of type RECVR AREA.
DB INCRNumericNumber of jobs running of type DB INCR.
DATAFILE FULLNumericNumber of jobs running of type DATAFILE FULL.
DATAFILE INCRNumericNumber of jobs running of type DATAFILE INCR.
ARCHIVELOGNumericNumber of jobs running of type ARCHIVELOG.
CONTROLFILENumericNumber of jobs running of type CONTROLFILE.
SPFILENumericNumber of jobs running of type SPFILE.
Backup Jobs Details
Session KeyNumericThe Session identifier.
Backup TypeStringType of input files backed up in this session. Can have one of the following values:
  • DB FULL
  • RECVR AREA
  • DB INCR
  • DATAFILE FULL
  • DATAFILE INCR
  • ARCHIVELOG
  • CONTROLFILE
  • SPFILE
Last Backup TimeStringLast backup start time.
Backup StatusStringBack up status with the value FAILED.
Time TakenNumericTime Taken to complete last back-up (in seconds).
Backup Size (MB)NumericBackup size in megabytes.
Backup Jobs History Recent Backups
Backup TypeStringType of input files backed up in this session.
Session KeyNumericThe Session identifier.
Last Backup TimeStringLast backup start time.
Backup StatusStringBack up status with the value FAILED.
Time TakenNumericTime Taken to complete last back-up (in seconds).
Backup Size (MB)NumericBackup size in megabytes.

Click the Recent backups link on the top right-hand corner of the Backup Job Details table to view recent backup job details for each backup type.

PGA

ParameterTypeDescription
TOP 10 Process using PGA - Graphical representation of the PGA used by processes.
PGA Stats Per Process (TOP 10)
Process IdNumericOracle process identifier.
Program NameStringProgram in progress.
PGA used (MB)NumericAmount of PGA memory consumed in megabytes.
PGA Allocated (MB)NumericMaximum PGA memory allocated at one time since instance startup.
Max PGA Used (MB)NumericPGA memory currently used by the process.
Freeable PGA (MB)NumericAllocated PGA memory which can be freed.
PGA Stats
Total PGA used (MB)NumericIndicates how much PGA memory is currently consumed.
Total PGA allocated (MB)NumericCurrent amount of PGA memory allocated by the instance.
Maximum PGA allocated (MB)NumericMaximum amount of PGA memory consumed .
Total freeable PGA (MB)NumericNumber of bytes of PGA memory in all processes that could be freed back to the operating system.
PGA freed back to OS (MB)NumericNumber of bytes of PGA memory freed back to the operating system.
Cache hit percentageNumericPercentage of PGA memory component, cumulative since instance startup
Resource being used by processes (%)NumericPercentage resources currently being used by processes.
Resouce limit for processes
Resource being used by processesNumericResources (locks or processes) currently being used.
Free ResourceNumericPercentage of unused resources.

Process

ParametersTypeDescription
Session Details
Process IdNumericOracle process identifier.
PGA used (MB)NumericIndicates how much PGA memory is currently consumed.
PGA Stats Per Process (TOP 10)
Process IdNumericOracle process identifier.
Program NameStringThe program in progress.
PGA used(MB)NumericIndicates how much PGA memory is currently consumed.
PGA Allocated(MB)NumericCurrent amount of PGA memory allocated by the instance.
Max PGA Used(MB)NumericMaximum amount of PGA memory consumed .
Freeable PGA(MB)NumericNumber of bytes of PGA memory in all processes that could be freed back to the operating system.

ASM

Applications Manager allows you to enable/disable data collection of several metrics. Once enabled ,you can also customize the polling interval of these metrics. Data collection for ASM is not enabled by default and here is how you can enable it:

Enabling ASM Metrics

  • Go to the Settings tab.
  • Click Performance Polling under Discovery and Data Collection.
  • Under Performance Polling, click on the Optimize Data Collection tab.
  • Select Oracle from the Monitor Type drop-down menu.
  • Select ASM Details from the Metric Name drop-down menu.
  • Select how you wish to configure the metrics:
    • By Monitor Type - This will be the default polling status, for any new monitor added. All the monitors of this type, will have the default polling status, until any exclusive customization is done for the monitor. You can choose between three different polling settings: Never collect data, Collect data in every polling and Collect data at customized time interval. Changing the polling status of 'Monitor Type', will also change any configuration done for its 'Monitors'.
    • By Monitors - Use this option to change the polling status of any particular monitor(s).
  • Click Save.
ParameterTypeDescription
Disk Group Details
Disk Group NumberNumericCluster-wide number assigned to the disk group.
NameStringName of the disk group.
StateStringState of the disk group relative to the instance (Connected, Broken, Unknown, Dismounted, Mounted).
TypeStringRedundancy type for the disk group (EXTERN, NORMAL, HIGH).
Disk Total(GB)NumericTotal capacity of the disk group (in GB).
Disk Free(GB)NumericUnused capacity of the disk group (in GB).
Disk Used (GB)NumericUsed capacity of the disk group (in GB).
Disk Free Percentage(%)NumericThe percentage of the amount of free disk space.
Disk Used Percentage (%)NumericThe percentage of the amount of disk space used.

RPO

RPO statistics are not monitored by default. Applications Manager allows you to enable/disable data collection of RPO statistics. Once enabled, you can also customize the polling interval of these metrics. To monitor RPO statistics:

  • Go to the Settings tab.
  • Click Performance Polling under Discovery and Data Collection.
  • Under Performance Polling, click on the Optimize Data Collection tab.
  • Select Oracle from the Monitor Type drop-down menu.
  • Select Log Apply Gap details in Primary Server/Log Apply Lag details in Standby Server from the Metric Name drop-down menu.
  • Select how you wish to configure the Log Apply Gap details:
    • By Monitor Type - This will be the default polling status, for any new monitor added. All the monitors of this type, will have the default polling status, until any exclusive customization is done for the monitor. You can choose between three different polling settings: Never collect data, Collect data in every polling and Collect data at customized time interval. Changing the polling status of 'Monitor Type', will also change any configuration done for its 'Monitors'.
    • By Monitors - Use this option to change the polling status of any particular monitor(s).

Note: Log Apply Gap details polling occurs in the Primary Server once every 24 hours.

Log Apply Gap Details

For Primary and Physical Standby Databases:

ParameterTypeDescription
ThreadNumericIndicates the thread number.
Last Sequence ReceivedNumericShows the last log sequence that was received by the database.
Last Sequence AppliedNumericShows the last log sequence that was applied to the database.
Log apply gapNumericShows the difference between log sequence received and the log sequence applied.

For Logical Standby databases:

ParameterTypeDescription
TypeStringType of the log applied.
SCNNumericThe System Change Number (SCN) of the database.
TimeStringTimestamp of the log that was applied.
SequenceNumericSequence number of the log that was applied.

Log Apply Lag Details

ParameterTypeDescription
Log Apply Lag Details (only from standby)
Transport LagNumericTransport lag is a measure of the degree to which the transport of redo to the standby database lags behind the generation of redo on the primary database. (no units)
Log Apply LagNumericLog Apply lag is a measure of the degree to which the redo data on the standby database lags behind the primary database. (no units)
Apply Finish TimeNumericEstimated time before log apply services will finish applying the redo data available on the standby database. (in minutes)

Archive Log Destination Details

Archive Log Destination Details are not monitored by default. Applications Manager allows you to enable/disable data collection of archive log destination metrics. Once enabled ,you can also customize the polling interval of these metrics. To monitor metrics:

  • Go to the Settings tab.
  • Click Performance Polling under Discovery and Data Collection.
  • Under Performance Polling, click on the Optimize Data Collection tab.
  • Select Oracle from the Monitor Type drop-down menu.
  • Select Archive Log Destination Monitoring from the Metric Name drop-down menu.
  • Select how you wish to configure the queries:
    • By Monitor Type - This will be the default polling status, for any new monitor added. All the monitors of this type, will have the default polling status, until any exclusive customization is done for the monitor. You can choose between three different polling settings: Never collect data, Collect data in every polling and Collect data at customized time interval. Changing the polling status of 'Monitor Type', will also change any configuration done for its 'Monitors'.
    • By Monitors - Use this option to change the polling status of any particular monitor(s).
ParameterTypeDescription
Archive Log Destination Details (only from primary)
Dest IdNumericIdentifies the log archive destination parameter
NameStringArchived log file name.
StatusStringStatus of the archived log.
TypeStringType of archival destination database:
  • LOCAL - Local to primary database
  • PHYSICAL - Physical standby
  • CROSS-INSTANCE - An instance of the primary
  • LOGICAL - Logical standby
DestinationStringOriginal destination from which the archive log was generated.
Protection ModeStringIndicates whether the database is protected:
  • MAXIMUM PROTECTION
  • MAXIMUM AVAILABILITY
  • RESYNCHRONIZATION
  • MAXIMUM PERFORMANCE
  • UNPROTECTED
Transmit modeStringSpecifies network transmission mode:
  • SYNCHRONOUS
  • PARALLELSYNC
  • ASYNCHRONOUS
Recovery modeStringCurrent mode of media recovery at the archival destination database:
  • IDLE - Managed recovery is not active
  • MANUAL - Manual media recovery active
  • MANAGED - Managed recovery is active
  • MANAGED REAL TIME APPLY - Log apply services recover redo data from standby redo logs at the same time the logs are being written to, as opposed to recovering redo from archived redo logs when a log switch occurs
Archive Log Destination Stats (only from primary)
Dest IdNumericLog archive destination parameter identifier
Log sequenceNumericIdentifies the sequence number of the last archived redo log to be archived
Net timeoutNumericNumber of seconds the log writer process will wait for status from the network server of a network operation issued by the log writer process
Fail SequenceNumericSequence number of the archived redo log being archived when the last error occurred
Archived SequenceNumericIdentifies the log sequence number of the most recent archived redo log received at the destination
Applied SequenceNumericIdentifies the log sequence number of the most recent applied redo log received at the destination
Delay (Mins)NumericIdentifies the delay interval (in minutes) before the archived redo log is automatically applied to a standby database
ErrorStringDisplays the error text

Alert Logs

Alert Logs are not monitored by default. Applications Manager allows you to enable/disable data collection for Lock statistics. Once enabled, you can also customize the polling interval of these metrics. To monitor Alert Log Statistics:

  • Go to the Settings tab.
  • Click Performance Polling under Discovery and Data Collection.
  • Under Performance Polling, click on the Optimize Data Collection tab.
  • Select Oracle from the Monitor Type drop-down menu.
  • Select Oracle Alert Log from the Metric Name drop-down menu.
  • Select how you wish to configure the Alert Log Statistics:
    • By Monitor Type - This will be the default polling status, for any new monitor added. All the monitors of this type will have the default polling status, until any exclusive customization is performed. You can choose between three different polling settings: Never collect data, Collect data at every poll and Collect data at customized time interval. Changing the polling status of 'Monitor Type', will also change any configuration done for its 'Monitors'.
    • By Monitors - Use this option to change the polling status of a particular monitor(s).
  • Configure Oracle Alert Log Upper Limit: This option allows you to set an upper limit on the number of Oracle Alert Log entries fetched, helping to prevent performance issues. The default limit is 1000.

Oracle Error List table lists only recent errors. To view history of ORA errors, click View Alert Log history.

Monitored Parameters

ParameterTypeDescription
Oracle ORA Error Count
Critical / Severe / Important / NormalNumericThe number of critical errors, severe errors, important message and normal messages.
Oracle ORA Error List
Record IDNumericThe record number for the message (this value is same as the row number).
Message LevelStringLevel the message belongs to. Lower level values imply higher severity for errors. Possible values include:
  • 1: CRITICAL: critical errors
  • 2: SEVERE: severe errors
  • 8: IMPORTANT: important message
  • 16: NORMAL: normal message
Originating TimeStringThe date and time at which the message was generated.
Host AddressStringThe IP of other network address of the originating host for the mesaage.
Message TextStringThe fully formed and localized text of the message.

Redo Logs

Applications Manager allows you to enable/disable data collection of the Redo Logs metrics. Once enabled, you can also customize the polling interval of these metrics. To enable metrics monitoring:

  • Go to the Settings tab.
  • Click Performance Polling under Discovery and Data Collection.
  • Under Performance Polling, click on the Optimize Data Collection tab.
  • Select Oracle from the Monitor Type drop-down menu.
  • Select Redo Logs from the Metric Name drop-down menu.
  • Select how you wish to configure the Redo Logs:
    • By Monitor Type - This will be the default polling status, for any new monitor added. All the monitors of this type, will have the default polling status, until any exclusive customization is done for the monitor. You can choose between three different polling settings: Never collect data, Collect data in every polling and Collect data at customized time interval. Changing the polling status of 'Monitor Type', will also change any configuration done for its 'Monitors'.
    • By Monitors - Use this option to change the polling status of any particular monitor(s).
    ParameterTypeDescription
    REDO PERFORMANCE
    Buffer Allocation Retries RatioNumericThe ratio of redo buffer allocation retries/redo writes in Percentage. Ideal value is upto 1%.
    Space Request RatioNumericThe ratio of redo log space requests/redo entries in Percentage.Ideal value is upto 1%.
    Space Wait RatioNumericThe ratio of redo log space requests/redo writes in Percentage.Ideal value is upto 1%
    REDO LOG DETAILS
    RedoLog Buffer SizeNumericThe size of the buffers for the Redo Logs in Mb.
    Log switches in past 1 hourNumericThe average number of log switches in the last hour.
    Current Redo Log UsageNumericThe percentage of redo logs used/filled up.
    REDO LOG GROUPS INFORMATION
    GroupNumericThe redo log group identifier.
    ThreadNumericThe number of redo log threads. (The redo log file groups of an instance are collectively called a redo log thread.)
    Log Size  (MB)NumericThe size of each log in the redo log groups.
    Member CountNumericThe number of members in the log group.
    Archive StatusStringArchive status: YES or NO. (Oracle lets you save filled groups of redo log files to one or more offline destinations, known as the archived redo log.)
    Log StatusStringLog status:
    • UNUSED - Online redo log has never been written to. This is the state of a redo log that was just added, or just after a RESETLOGS, when it is not the current redo log.
    • CURRENT - Current redo log. This implies that the redo log is active. The redo log could be open or closed.
    • ACTIVE - Log is active but is not the current log. It is needed for crash recovery. It may be in use for block recovery. It may or may not be archived.
    • CLEARING - Log is being re-created as an empty log after an ALTER DATABASE CLEAR LOGFILE statement. After the log is cleared, the status changes to UNUSED.
    • CLEARING_CURRENT - Current log is being cleared of a closed thread. The log can stay in this status if there is some failure in the switch such as an I/O error writing the new log header.
    • INACTIVE - Log is no longer needed for instance recovery. It may be in use for media recovery. It may or may not be archived.
    REDO LOG MEMBERS INFORMATION
    Member NameStringThe redo log member name.
    GroupNumericThe redo log group identifier.
    Member StatusStringThe status of the log member:
    • INVALID - File is inaccessible
    • STALE - File's contents are incomplete
    • DELETED - File is no longer used
    • IN USE - File is in use
    Member Type  StringThe member status type:
    • ONLINE
    • STANDBY

Loved by customers all over the world

"Standout Tool With Extensive Monitoring Capabilities"

It allows us to track crucial metrics such as response times, resource utilization, error rates, and transaction performance. The real-time monitoring alerts promptly notify us of any issues or anomalies, enabling us to take immediate action.

Reviewer Role: Research and Development

carlos-rivero
"I like Applications Manager because it helps us to detect issues present in our servers and SQL databases."
Carlos Rivero

Tech Support Manager, Lexmark

Trusted by over 6000+ businesses globally