icinga2 writing

icinga2 is an open-source, host and network monitoring software initially developed from the Nagios network monitoring application. Currently, icinga2 is distributed under the GNU GPL v2 license.

You can write the data collected by icinga2 to TDengine by simply modifying the icinga2 configuration to point to the taosAdapter server and the corresponding port, taking advantage of TDengine’s efficient storage and query performance and clustering capabilities for time-series data.

Prerequisites

To write icinga2 data to TDengine requires the following preparations.

  • The TDengine cluster is deployed and working properly
  • taosAdapter is installed and running properly. Please refer to the taosAdapter manual for details.
  • icinga2 has been installed. Please refer to the official documentation for icinga2 installation

Configuration steps

Configuring taosAdapter

To configure taosAdapter to receive icinga2 data.

  • Enable the configuration item in the taosAdapter configuration file (default location /etc/taos/taosadapter.toml)
  1. ...
  2. [opentsdb_telnet]
  3. enable = true
  4. maxTCPConnections = 250
  5. tcpKeepAlive = false
  6. dbs = ["opentsdb_telnet", "collectd", "icinga2", "tcollector"]
  7. ports = [6046, 6047, 6048, 6049]
  8. user = "root"
  9. password = "taosdata"
  10. ...

The default database name written by the taosAdapter is icinga2. You can also modify the taosAdapter configuration file dbs entry to specify a different name. user and password are the values configured by the actual TDengine. You need to restart the taosAdapter after modification.

  • You can also enable taosAdapter to receive icinga2 data by using the taosAdapter command-line parameters or setting environment variables.

Configure icinga3

  • Enable opentsdb-writer for icinga2 (refer to the link https://icinga.com/docs/icinga-2/latest/doc/14-features/#opentsdb-writer)
  • Modify the configuration file /etc/icinga2/features-enabled/opentsdb.conf by filling in <taosAdapter’s host> as the domain name or IP address of the server running taosAdapter and <port for icinga2> as the corresponding port on which taosAdapter supports receiving icinga2 data (default is 6048)
  1. object OpenTsdbWriter "opentsdb" {
  2.   host = "<taosAdapter's host>"
  3.   port = <port for icinga2>
  4. }

Example file:

  1. object OpenTsdbWriter "opentsdb" {
  2.   host = "127.0.0.1"
  3.   port = 6048
  4. }

Verification method

Restart taosAdapter:

  1. sudo systemctl restart taosadapter

Restart icinga2:

  1. sudo systemctl restart icinga2

After waiting about 10 seconds, use the TDengine CLI to query TDengine to verify that the appropriate database has been created and data are written.

  1. taos> show databases;
  2.               name              |
  3. =================================
  4.  information_schema             |
  5.  performance_schema             |
  6.  icinga2                        |
  7. Query OK, 3 row(s) in set (0.001867s)
  9. taos> use icinga2;
  10. Database changed.
  12. taos> show stables;
  13.               name              |
  14. =================================
  15.  icinga.service.users.state_... |
  16.  icinga.service.users.acknow... |
  17.  icinga.service.procs.downti... |
  18.  icinga.service.users.users     |
  19.  icinga.service.procs.procs_min |
  20.  icinga.service.users.users_min |
  21.  icinga.check.max_check_atte... |
  22.  icinga.service.procs.state_... |
  23.  icinga.service.procs.procs_... |
  24.  icinga.service.users.users_... |
  25.  icinga.check.latency           |
  26.  icinga.service.procs.procs_... |
  27.  icinga.service.users.downti... |
  28.  icinga.service.users.users_... |
  29.  icinga.service.users.reachable |
  30.  icinga.service.procs.procs     |
  31.  icinga.service.procs.acknow... |
  32.  icinga.service.procs.state     |
  33.  icinga.service.procs.reachable |
  34.  icinga.check.current_attempt   |
  35.  icinga.check.execution_time    |
  36.  icinga.service.users.state     |
  37. Query OK, 22 row(s) in set (0.002317s)
icinga2 - 图1note
  • TDengine will automatically create unique IDs for sub-table names by the rule.