Knowledge Base

Accessing the monitoring data of IPCheck Server Monitor

Esta pagina no esta disponible en Español. Rogamos su comprension.

This article explains storage of sensor data and monitoring data of IPCheck Server Monitor

Important: Please only use this information for READ ONLY access to the data. There are also other tables and database fields necessary for IPCheck to work correctly which are not shown here. It is not recommended to write data into IPCheck's database tables. To programmatically import server/sensor data into the database use the "Export Group/Import Group" feature.

Database System

The Open Source SQL Server Firebird, which was developed based on the Open Source version of Borland's Interbase SQL Server, is used to store the data. To access the data in the SQL server you must use some software that can access an Interbase/Firebird SQL database (e.g. via the ODBC driver or one of the other connectors available at the Firebird website).

Database System Hierarchy

IPCheck Server Monitor stores the hierarchy of Users=>Groups=>Servers=>Sensors in four tables (=tables IPCUSER, IPCGROUP, IPCSERVER and IPCSENSOR) in the Firebird SQL database (filename ipcheck.fdb).

All monitoring results (and also all other activities) are by default stored in a proprietary fileformat ('Monitoring Database' subfolder, one folder per day, one file per sensor, filename is based on the group/server/sensor id). The monitoring results can optionally be exported to a CSV file or the table "IPCLOG " in the SQL database for external processing. This setting can be found in the Control Panel.

In the database chart (see attachment below) the relations between the five tables are shown graphically.            

Selected Data Fields

Here is a list of table columns with their meanings that are not self explanatory.

Field "NODEACTIVE"

  • 0: Object Active
  • 1: Object Paused
  • 2: Object marked for deletion (will be removed by next database maintenance)

Field "KIND" (Table "IPCSENSOR")

  • 1: PING
  • 2: HTTP
  • 3: HTTP Advanced
  • 4: HTTP Content
  • 5: HTTP Global (discontinued)
  • 6: Script
  • 7: TCP Script
  • 8: SMTP
  • 9: POP3
  • 10: FTP
  • 11: PORT
  • 12: DNS
  • 13: HTTP Transaction
  • 14: Custom
  • 15: SNMP Traffic
  • 16: SNMP Advanced
  • 17: FILE
  • 18: DiskSpace
  • 19: SERVICE
  • 20: MSSQL
  • 21: OracleSQL
  • 22: MySQL

Field "ERRORTYPE" (Table "IPCLOG")

  • 0: No Error
  • 1: No Connection to probe
  • 2: Exception occured in probe
  • 3: Socket Error (TCP)
  • 4: Protocol Error (e.g. HTTP/SMTP)
  • 5: Content Error (e.g. content checks)

Field "STATUS" (Table "IPCLOG")

  • 0: OK
  • 1: SLOW
  • 2: FAILED
  • 3: Unused
  • 4: Value Changed (e.g. HTTP content check)
  • 5: No connection to probe
  • 6: Value undefined (e.g. for 1st scan of SNMP delta )

Other fields of table "IPCLOG"

  • LOGTYPE: Always zero
  • RESULTSTRING: status string as shown in the web interface
  • ERRORSTRING: raw status string as given by the sensor
  • FIRSTSCAN: value of 1 means that this is the first scan result, earlier status is not known (e.g. after a reboot or if sensor was paused)

By Category