Remstats Home


  About remstats
  Release Notes
  FAQ
  Conventions
  Prerequisites
  Installation
  Configuration
  Configuration Tools
  Servers
  Collectors
      cisco-access-server-collector
      dbi-collector
      dns-collector
      error-collector
      log-collector
      nt-status-collector
      ntop-collector
      ping-collector
      port-collector
      program-collector
      remoteping-collector
      snmp-collector
      snmp-route-collector
      unix-status-collector
  Updater
  Monitors
  pagemakers
  run-remstats2
  CGIs
  troubleshooting
  do-traceroutes
  Miscellany
  Thank-you
  Index


Live Data

Remstats was written by Thomas Erskine at the CRC in Canada and now looking for work.

[Top] [Prev] [Next]

dbi-collector - data from remote databases

Usage:

dbi-collector version 1.8 from remstats 1.0.13a
usage: ../dbi-collector [options]
where options are:
    -d nnn  enable debugging output at level 'nnn'
    -f fff  use 'fff' for config-dir [/home/groups/r/re/remstats/etc/config]
    -F      force collection even if it's not time
   	-G GGG  only try hosts from group 'GGG', a comma-separated list
    -h      show this help
    -H HHH  only try hosts from 'HHH', a comma-separated list
    -K KKK  only try hosts with key(s) 'KKK', a comma-separated list
    -u      ignore uphosts file

Description:

The dbi-collector uses perl's DBI interface to access remote databases to collect data. If you have a DBD driver for your database, and can write an SQL select statement to select the data you're interested in, the dbi-collector can import the data into rrdtool and remstats.

The dbi-collector adds three new directives to RRD definitions which use it:

The connect directive tells how to connect to the appropriate server and database; the select tells how to select the data.

For an RRD collected by the dbi-collector, the data directive will require the column number in the select that will provide its data. This will be appended to the data directive like:

	data xxx=yyy GAUGE:600:0:U COL=12

There are also pseudo-columns called STATUS and RESPONSE to enable the rrd definition to reference the connection-status and response-time.

There are also some possible additions to the rrd directive in the host file. The rrd directive can look like:

	rrd	rrdname CONNECT="cc" SELECT="ss" USER="uu" PASSWORD="pp" DATABASE="dd"

All of the extras on the end are optional, and are provided in order to be able to use a single connect file with multiple databases, users, ...

If the multirowid is specified, then the variable returned is named RRDNAME:DATANAME:ROWNAME. Otherwise, it is named RRDNAME:DATANAME.

Notes

The dbi-collector, when querying an Oracle database, needs to know where Oracle was installed, specifically, it needs the environment to contain ORACLE_HOME pointing at where Oracle was installed. This can be simply done using the new environment config-file.


[Top] [Remstats] [SourceWorks] [RRDtool] [SourceForge]
Last updated Fri May 30 13:50:52 PDT 2003 by <terskine@users.sourceforge.net>.