Orabbix 1.2.2 has been released!!
On this release:
- Added the following parameter on main configuration file:
- DefaultUser = <USERNAME>
- DefaultPassword = <PASSWORD>
- <DB_NAME>.ExtraQueryListFile = <relative path to extra query file>
- on query’s properties file I’ve added the following parameter:
- <QUERY_NAME>.WhenNotAlive = <VALUE>
You can download it here
Complete changelog here::
1.2.2
Added the following parameters in the main configuration file:
- DefaultUser = <USERNAME>
- DefaultPassword = <PASSWORD>
- <DB_NAME>.ExtraQueryListFile =
on query’s properties file I’ve added the following parameter:
- <QUERY_NAME>.WhenNotAlive = <VALUE>
with these parameters you can define a default username and password for all databases.
- DefaultUser = <USERNAME>
- DefaultPassword = <PASSWORD>
this default parameter can be overridden using the following pair:
- <DB_NAME>.User and <DB_NAME>.User
It is possible to override only Username or Password.
the following parameter
- <DB_NAME>.ExtraQueryListFile =
adds another custom query to a default query file.
if there are duplicate the ExtraQueryListFile it will override them.
the following parameter
- <QUERY_NAME>.WhenNotAlive = <VALUE>
is used to specify a value or a string to send if a database is not working,
doing so you are going to “clean” the graphs generated in Zabbix with a “set” value.
This fixes the issue introduced by “Zabbix Trapper”:
– if Zabbix don’t receive data the graphs don’t change anymore.
Tags: database, linkedin, monitoring, orabbix, oracle, zabbix