Skip to main content

Informix DB

Connector dependencies​

The following monitoring connectors will be installed when you install the Informix DB connector through the Configuration > Monitoring Connector Manager menu:

Pack assets​

Templates​

The Monitoring Connector Informix DB brings a host template:

  • App-DB-Informix-custom

The connector brings the following service templates (sorted by the host template they are attached to):

Service AliasService TemplateService Description
Archivelevel0-GlobalApp-DB-Informix-Archivelevel0-Global-customCheck archive level0 backup last execution
CheckpointsApp-DB-Informix-Checkpoints-customCheck Informix Checkpoints
Chunk-Down-GlobalApp-DB-Informix-Chunk-Down-Global-customCheck chunk state
ConnectionApp-DB-Informix-Connection-customCheck connection to the Informix server
Global-CacheApp-DB-Informix-Global-Cache-customCheck read/write caches
LockoverflowApp-DB-Informix-Lockoverflow-customCheck the number of times Informix attempted to exceed the maximum number of locks
LongtxsApp-DB-Informix-Longtxs-customCheck number of current long transactions
SessionsApp-DB-Informix-Sessions-customCheck current sessions

The services listed above are created automatically when the App-DB-Informix-custom host template is used.

Collected metrics & status​

Here is the list of services for this connector, detailing all metrics and statuses linked to each service.

NameUnit
seconds.#archive-level0-names

Prerequisites​

You need to download the "Informix Client Software Development Kit" on the IBM website.

Install the SDK with the following procedure:

  1. Copy the archive on the poller.
  2. Create an informix user:
useradd informix chmod 775 /home/informix
  1. Install Sun JRE (as explained in the IBM procedure).
  2. Install the SDK (selectTypical Installation):
./installclientsdk -javahome /usr/java/jreXXXX/ ....
  1. Specify a directory or press Enter to accept the default directory. Directory Name: [/root/informix/sdkclient/] /home/informix/sdkclient

Perl DBD Informix​

  1. To compile Informix DBD, you need access to an Informix Database. Run:
cd /usr/local/src
wget http://search.cpan.org/CPAN/authors/id/J/JO/JOHNL/DBD-Informix-2013.0521.tar.gz
tar xzf DBD-Informix-2013.0521.tar.gz
cd DBD-Informix-2013.0521
export INFORMIXDIR=/home/informix/sdkclient
export LD_LIBRARY_PATH=$ORACLE_HOME/lib
export PATH=${PATH}:/home/informix/sdkclient/bin
export LD_LIBRARY_PATH=/home/informix/sdkclient/lib/esql/:/home/informix/sdkclient/lib/
export DBD_INFORMIX_USERNAME=root
export DBD_INFORMIX_PASSWORD=xxxx # export DBD_INFORMIX_DATABASE=xxxx

Set a value for Informix Instance in the /home/informix/sdkclient/etc/sqlhosts file:

INSTANCE onsoctcp IP PORT
  1. Compile the library:
$ perl Makefile.PL 
$ make
$ make install
  1. Create the file /etc/ld.so.conf.d/informix.conf
  2. Link to the Informix Library:
$ touch /etc/ld.so.conf.d/informix.conf 
vi /etc/ld.so.conf.d/informix.conf

You just have to enter in the file:

/home/informix/sdkclient/lib/esql/ /home/informix/sdkclient/lib/

Then:

/sbin/ldconfig

About the user account​

The safest way to retrieve information from the Oracle server is to create a dedicated user for Centreon. This user account must have the read permission on sysmaster database.

Installing the monitoring connector​

Pack​

  1. If the platform uses an online license, you can skip the package installation instruction below as it is not required to have the connector displayed within the Configuration > Monitoring Connector Manager menu. If the platform uses an offline license, install the package on the central server with the command corresponding to the operating system's package manager:
dnf install centreon-pack-applications-databases-informix
  1. Whatever the license type (online or offline), install the Informix DB connector through the Configuration > Monitoring Connector Manager menu.

Plugin​

Since Centreon 22.04, you can benefit from the 'Automatic plugin installation' feature. When this feature is enabled, you can skip the installation part below.

You still have to manually install the plugin on the poller(s) when:

  • Automatic plugin installation is turned off
  • You want to run a discovery job from a poller that doesn't monitor any resource of this kind yet

More information in the Installing the plugin section.

Use the commands below according to your operating system's package manager:

dnf install centreon-plugin-Applications-Databases-Informix

Using the monitoring connector​

Using a host template provided by the connector​

  1. Log into Centreon and add a new host through Configuration > Hosts.
  2. Fill in the Name, Alias & IP Address/DNS fields according to your resource's settings.
  3. Apply the App-DB-Informix-custom template to the host. A list of macros appears. Macros allow you to define how the connector will connect to the resource, and to customize the connector's behavior.
  4. Fill in the macros you want. Some macros are mandatory.
MacroDescriptionDefault valueMandatory
INFORMIXUSERNAMEDatabase Username
INFORMIXPASSWORDDatabase password
INFORMIXPORTDatabase Server Port33333
INFORMIXINSTANCENAMEDatabase Instance Name
  1. Deploy the configuration. The host appears in the list of hosts, and on the Resources Status page. The command that is sent by the connector is displayed in the details panel of the host: it shows the values of the macros.

Using a service template provided by the connector​

  1. If you have used a host template and checked Create Services linked to the Template too, the services linked to the template have been created automatically, using the corresponding service templates. Otherwise, create manually the services you want and apply a service template to them.
  2. Fill in the macros you want (e.g. to change the thresholds for the alerts). Some macros are mandatory (see the table below).
MacroDescriptionDefault valueMandatory
DBSPACENAMESet the dbspace (empty means 'check all dbspaces')
WARNINGWarning threshold in seconds since last execution
CRITICALCritical threshold in seconds since last execution
EXTRAOPTIONSAny extra option you may want to add to the command (a --verbose flag for example). All options are listed here.
  1. Deploy the configuration. The service appears in the list of services, and on the Resources Status page. The command that is sent by the connector is displayed in the details panel of the service: it shows the values of the macros.

How to check in the CLI that the configuration is OK and what are the main options for?​

Once the plugin is installed, log into your Centreon poller's CLI using the centreon-engine user account (su - centreon-engine). Test that the connector is able to monitor a resource using a command like this one (replace the sample values by yours):

/usr/lib/centreon/plugins/centreon_informix.pl \
	--plugin=database::informix::sql::plugin \
	--host=10.0.0.1 \
	--username='' \
	--password='' \
	--port='33333' \
	--mode='sql' \
	--sql-statement="" \
	--warning='' \
	--critical=''

The expected command output is shown below:

OK:  execution time: 67851 second(s) | 'value'=11007;;;; 'sqlrequest.execution.time.seconds'=67851s;;;0;

Troubleshooting​

Please find the troubleshooting documentation for Centreon Plugins typical issues.

Available modes​

In most cases, a mode corresponds to a service template. The mode appears in the execution command for the connector. In the Centreon interface, you don't need to specify a mode explicitly: its use is implied when you apply a service template. However, you will need to specify the correct mode for the template if you want to test the execution command for the connector in your terminal.

All available modes can be displayed by adding the --list-mode parameter to the command:

/usr/lib/centreon/plugins/centreon_informix.pl \
	--plugin=database::informix::sql::plugin \
	--list-mode

The plugin brings the following modes:

ModeLinked service template
archivelevel0 [code]App-DB-Informix-Archivelevel0-Generic-Name-custom
App-DB-Informix-Archivelevel0-Global-custom
checkpoints [code]App-DB-Informix-Checkpoints-custom
chunkstates [code]App-DB-Informix-Chunk-Down-Global-custom
collection [code]Not used in this Monitoring Connector
connection-time [code]App-DB-Informix-Connection-custom
dbspace-usage [code]App-DB-Informix-Dbspace-Usage-Generic-Name-custom
App-DB-Informix-Dbspace-Usage-Global-custom
global-cache [code]App-DB-Informix-Global-Cache-custom
list-databases [code]Not used in this Monitoring Connector
list-dbspaces [code]Not used in this Monitoring Connector
lockoverflow [code]App-DB-Informix-Lockoverflow-custom
logfile-usage [code]App-DB-Informix-Logfiles-Usage-custom
longtxs [code]App-DB-Informix-Longtxs-custom
name [code]Not used in this Monitoring Connector
sessions [code]App-DB-Informix-Sessions-custom
sql [code]App-DB-Informix-Sql-Statement-custom
table-locks [code]App-DB-Informix-Table-Locks-Generic-Name-custom
App-DB-Informix-Table-Locks-Global-custom

Available options​

Generic options​

All generic options are listed here:

OptionDescription
--modeDefine the mode in which you want the plugin to be executed (see --list-mode).
--dyn-modeSpecify a mode with the module's path (advanced).
--list-modeList all available modes.
--mode-versionCheck minimal version of mode. If not, unknown error.
--versionReturn the version of the plugin.
--sqlmodeThis plugin offers several ways to query the database (default: dbi). See --list-sqlmode.
--list-sqlmodeList all available sql modes.
--multipleEnable connecting to multiple databases (required by some specific modes such as replication).
--pass-managerDefine the password manager you want to use. Supported managers are: environment, file, keepass, hashicorpvault and teampass.
--verboseDisplay extended status information (long output).
--debugDisplay debug messages.
--filter-perfdataFilter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data.
--filter-perfdata-advFilter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %{variable} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value.
--explode-perfdata-maxCreate a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '_max' suffix). Example: it will split 'used_prct'=26.93%;0:80;0:90;0;100 into 'used_prct'=26.93%;0:80;0:90;0;100 'used_prct_max'=100%;;;;
--change-perfdata --extend-perfdataChange or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target[,[newuom],[min],[max]] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic_in,,percent()' =back
--change-perfdataChange or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target[,[newuom],[min],[max]] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic_in,,percent()' =back
--extend-perfdataChange or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target[,[newuom],[min],[max]] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic_in,,percent()' =back
--extend-perfdata-groupAdd new aggregated metrics (min, max, average or sum) for groups of metrics defined by a regex match on the metrics' names. Syntax: --extend-perfdata-group=regex,namesofnewmetrics,calculation[,[newuom],[min],[max]] regex: regular expression namesofnewmetrics: how the new metrics' names are composed (can use $1, $2... for groups defined by () in regex). calculation: how the values of the new metrics should be calculated newuom (optional): unit of measure for the new metrics min (optional): lowest value the metrics can reach max (optional): highest value the metrics can reach Common examples: =over 4 Sum wrong packets from all interfaces (with interface need --units-errors=absolute): --extend-perfdata-group=',packets_wrong,sum(packets_(discard|error)_(in|out))' Sum traffic by interface: --extend-perfdata-group='traffic_in_(.*),traffic_$1,sum(traffic_(in|out)_$1)' =back
--change-short-output --change-long-outputModify the short/long output that is returned by the plugin. Syntax: --change-short-output=patternreplacementmodifier Most commonly used modifiers are i (case insensitive) and g (replace all occurrences). Example: adding --change-short-output='OKUpgi' will replace all occurrences of 'OK', 'ok', 'Ok' or 'oK' with 'Up'
--change-short-outputModify the short/long output that is returned by the plugin. Syntax: --change-short-output=patternreplacementmodifier Most commonly used modifiers are i (case insensitive) and g (replace all occurrences). Example: adding --change-short-output='OKUpgi' will replace all occurrences of 'OK', 'ok', 'Ok' or 'oK' with 'Up'
--change-long-outputModify the short/long output that is returned by the plugin. Syntax: --change-short-output=patternreplacementmodifier Most commonly used modifiers are i (case insensitive) and g (replace all occurrences). Example: adding --change-short-output='OKUpgi' will replace all occurrences of 'OK', 'ok', 'Ok' or 'oK' with 'Up'
--change-exitReplace an exit code with one of your choice. Example: adding --change-exit=unknown=critical will result in a CRITICAL state instead of an UNKNOWN state.
--range-perfdataRewrite the ranges displayed in the perfdata. Accepted values: 0: nothing is changed. 1: if the lower value of the range is equal to 0, it is removed. 2: remove the thresholds from the perfdata.
--filter-uomMask the units when they don't match the given regular expression.
--opt-exitReplace the exit code in case of an execution error (i.e. wrong option provided, SSH connection refused, timeout, etc). Default: unknown.
--output-ignore-perfdataRemove all the metrics from the service. The service will still have a status and an output.
--output-ignore-labelRemove the status label ("OK:", "WARNING:", "UNKNOWN:", CRITICAL:") from the beginning of the output. Example: 'OK: Ram Total:...' will become 'Ram Total:...'
--output-xmlReturn the output in XML format (to send to an XML API).
--output-jsonReturn the output in JSON format (to send to a JSON API).
--output-openmetricsReturn the output in OpenMetrics format (to send to a tool expecting this format).
--output-fileWrite output in file (can be combined with json, xml and openmetrics options). E.g.: --output-file=/tmp/output.txt will write the output in /tmp/output.txt.
--disco-formatApplies only to modes beginning with 'list-'. Returns the list of available macros to configure a service discovery rule (formatted in XML).
--disco-showApplies only to modes beginning with 'list-'. Returns the list of discovered objects (formatted in XML) for service discovery.
--float-precisionDefine the float precision for thresholds (default: 8).
--source-encodingDefine the character encoding of the response sent by the monitored resource Default: 'UTF-8'. =head1 DESCRIPTION B<output>. =cut
--hostHostname to query.
--portDatabase Server Port.
--instanceDatabase Instance Name.

Modes options​

All available options for each service template are listed below:

OptionDescription
--warningWarning threshold in seconds since last execution.
--criticalCritical threshold in seconds since last execution.
--nameSet the dbspace (empty means 'check all dbspaces').
--regexpAllows to use regexp to filter dbspaces (with option --name).

All available options for a given mode can be displayed by adding the --help parameter to the command:

/usr/lib/centreon/plugins/centreon_informix.pl \
	--plugin=database::informix::sql::plugin \
	--host=10.0.0.1 \
	--help