Difference between revisions of "Orabbix"
(→What can it monitor?) |
|||
| Line 11: | Line 11: | ||
===What can it monitor?=== | ===What can it monitor?=== | ||
Below are some examples of what Orabbix is capable of monitoring: | Below are some examples of what Orabbix is capable of monitoring: | ||
| − | + | - DB Version (i.e. Validity of package) | |
| − | + | - Archiving (Archive log production with trend analysis) | |
| − | + | - Event Waits (Files I/O, single block read, multi-block read, direct path read, SQLNet Messages, Control file I/O, Log Write) | |
| − | + | - Hit Ratio (Hit Ratio on Triggers, Tables/Procedures, SQL Area, Body) | |
| − | + | - Logical I/O (Server performance on Logical I/O of: Current Read, Consistent Read, Block Change) | |
| − | + | - Physical I/O (Redo Writes, Datafile Writes, Datafile Reads) | |
| − | + | - PGA | |
| − | + | - SGA (In particular; Fixed Buffer, Java Pool, Large Pool, Log Buffer, Shared Poolm Buffer Cache) | |
| − | + | - Shared Pool (Pool Dictionary Cache, Pool Free Memory, Library Chache, SQL Area, MISC.) | |
| − | + | - Pin Hit Ratio (Oracle library cache pin are caused by contention with the library cache, the area used to store SQL executables for re-use) | |
| − | + | - Sessions / Processes | |
| − | + | - Sessions (Active Sessions, Inactive Sessions, System Sessions) | |
| − | + | - DBSize/DBFileSize (DBSize size of database really used space and of Filesize) | |
Revision as of 16:08, 25 October 2011
Contents
Download & Installation Instructions
About Orabbix
Product Description
Orabbix is a plugin designed to work with Zabbix Enterprise Monitor to provide multi-tiered monitoring, performance and availability reporting and measurement for Oracle Databases, along with server performance metrics.
It provides an effective mechanism to acquire data from numerous Oracle instances, and in turn provides this information for monitoring and performance metrics to your Zabbix server. You can then utilize the reporting capabilities of Zabbix for all data collected, and provide analysis such as graphs and service level agreement metrics for stakeholders.
The current distribution contains a set of pre-defined templates which incorporate alerting and graphing capabilities from initial deployment. However these can be fine tuned to suit your needs and data/monitoring requirements.
What can it monitor?
Below are some examples of what Orabbix is capable of monitoring: - DB Version (i.e. Validity of package) - Archiving (Archive log production with trend analysis) - Event Waits (Files I/O, single block read, multi-block read, direct path read, SQLNet Messages, Control file I/O, Log Write) - Hit Ratio (Hit Ratio on Triggers, Tables/Procedures, SQL Area, Body) - Logical I/O (Server performance on Logical I/O of: Current Read, Consistent Read, Block Change) - Physical I/O (Redo Writes, Datafile Writes, Datafile Reads) - PGA - SGA (In particular; Fixed Buffer, Java Pool, Large Pool, Log Buffer, Shared Poolm Buffer Cache) - Shared Pool (Pool Dictionary Cache, Pool Free Memory, Library Chache, SQL Area, MISC.) - Pin Hit Ratio (Oracle library cache pin are caused by contention with the library cache, the area used to store SQL executables for re-use) - Sessions / Processes - Sessions (Active Sessions, Inactive Sessions, System Sessions) - DBSize/DBFileSize (DBSize size of database really used space and of Filesize)
