I’ve released a new version of Orabbix.
actual improvements are:
1) Added retry on ZabbixSend items and values (max 10 times) , increased socket timeout to 30 sec.
2) Now exception are managed better and is less verbose i’ve revisited all loglevel to clean the software
Actually this daemon keep monitored 43 Oracle instances on mine production environment, with success.
see ya
more info available:
http://rootzone.wordpress.com/
downloadable here:
https://sourceforge.net/projects/orabbix/
Orabbix is becoming every day more stable 🙂
I’m using this on production servers on RedHat EL 5.3 , with zabbix server 1.6.6, if someone can try on zabbix server 1.8.1 i’ll be happy to receive a feedback.
On this release:
- Modified the version query now return :
– DB_NAME = <dbname> – INSTANCE_NAME = <instancename>
– SERVERNAME = <server.example.com> – SERVERADDRESS = <192.168.0.1>
CATALOG Oracle Database Catalog Views 10.2.0.4.0 VALID
CATJAVA Oracle Database Java Packages 10.2.0.4.0 VALID
CATPROC Oracle Database Packages and Types 10.2.0.4.0 VALID
EXF Oracle Expression Filter 10.2.0.4.0 VALID
JAVAVM JServer JAVA Virtual Machine 10.2.0.4.0 VALID
ORDIM Oracle interMedia 10.2.0.4.0 VALID
OWM Oracle Workspace Manager 10.2.0.4.3 VALID
RUL Oracle Rules Manager 10.2.0.4.0 VALID
XDB Oracle XML Database 10.2.0.4.0 VALID
XML Oracle XDK 10.2.0.4.0 VALID
as you can see i’ve added this information: DB_NAME INSTANCE_NAME SERVERNAME SERVERADDRESS. DB_NAME and INSTANCE_NAME can be different just in case of RAC or DATAGUARD configuration.
- Modified how retrieve the values from resultset now is supported an output with more column and more rows
- Database are removed dynamically this mean that you can add and remove database without restart the daemon.
- Founded a little bug on connection to database, there was a connection that was idle and never used now is fixed.
New release available at:
https://sourceforge.net/projects/orabbix/
[slideshow]
In this new release :
- fixed trouble with connection, now if a database is unavailable will be removed and on next loop the daemon try again to get connection and execute query etc..
- added dynamics configuration features, if you add a database this will be used on next loop.
- added a new parameter ZabbixDaemon.MaxThreadNumber on config.props
There is only a constraint with thid dynamics configuration the parameter ZabbixDaemon.MaxThreadNumber need be >= of the number of your databases.
this new release is available for donwload here:
Hi to everyone,
in this release there are some correction, i’ve removed some dead code, and in particular added this new item:
- a new query to inspect user locked as LOCKED(TIMED) and EXPIRED(GRACE)
so you can receive a mail if someon lock an user on database.
I consider this item foundamental to keep monitored users on production databases.
I’ve correct the bug that hang orabbix if you have wrong connection parameter.
An last but not the least i’ve added a new parameter on query.props <QUERY_NAME>.NoDataFound= where you can spacify a value that will be used when no data are founded so you can grep this value on trigger.
Download the new version here: