Skip to content

Home

Jump to bottom
SmartMarmot edited this page Nov 10, 2016 · 2 revisions

About DBforBix

Architecture

DBforBIX is a daemon designed to work in combination with Zabbix Enterprise Monitor to provide multi-tiered monitoring, performance and availability reporting and measurement for the many kind of different databases, along with server performance metrics.

It provides an effective mechanism to acquire data from numerous databases installation, 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.

DBforBIX can run as a Windows Service and is able to work on many different environments. Where is available a JRE 1.6 you can run DbforBIX. History

You can read about the history and evolution of the DBforBIX plug-in in these threads below:

Original Orabbix here: http://www.zabbix.com/forum/showthread.php?t=13666
Latest Orabbix here: http://www.zabbix.com/forum/showthread.php?t=16391

Original DBforBIX here: https://www.zabbix.com/forum/showthread.php?t=21730&highlight=dbforbix

The origins of DBforBIX can be traced though Orabbix, PostBIX, MySQLBIX and DB2Bix, and as such inherits all its predecessors benefits.

Author

DBforBIX was developed and written by:
Andrea Dalle Vacche : http://www.smartmarmot.com

Supported Databases

DBforBIX can acquire and retrieve every kind performance parameter and vital statistic that is supported or available through standard queries.

DBforBIX support the following databases:

  • Oracle
  • MySQL Server
  • PostgreSQL
  • MS SQL Server
  • DB2
  • Sybase Anywhere
  • HP Allbase

All information gathered from the monitored databases is retrieved by query, using the Java JDBC layer. This ensures compatibility and diversity with future database versions and types.

Monitoring Capabilities

Below are some examples of what DBforBIX is capable of monitoring.

on Oracle Database The following are just some of parameters that DBforBIX is capable of monitoring on Oracle:

Availability

  • DB Version (for every vendor)

  • 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) on MySQL server The following are just some of parameters that DBforBIX is capable of monitoring on MySQL. The list was truncated due to the sheer volume of list items:

  • Dbversion

  • table/thread cache

  • Com created/dropped/changed/committed

  • Innodb statistics

  • Key read/write/requests

  • Qcache statistics

on PostgreSQL server The following are just some of parameters that DBforBIX is capable of monitoring on PostgreSQL:

  • Availability
  • Buffers (Backend, checkpoint, clean, allocated)
  • Checkpoint (requested, timed)
  • Connections
  • Tuples (deleted, updated, fetched, returned, inserted)
  • Xact (rollback, commit)
  • Locks (every kind of exclusive locks and every kind of general locks)

on MS SQL server The following are just some of parameters that DBforBIX is capable of monitoring on Microsoft SQL Server:

  • Cachehit
  • I/O Pending
  • waittime
  • dbsize/logsize
  • log usedsize
  • Page reades/writes

On DB2 Coming soon to a DBforBIX distribution near you!

On Sybase Anywhere Coming soon to a DBforBIX distribution near you!

On HP ALLBASE Coming soon to a DBforBIX distribution near you!

Clone this wiki locally