Zabbix Documentation 4.4

3.04.04.4 (current)| In development:5.0 (devel)| Unsupported:1.82.02.22.43.23.44.2Guidelines

User Tools

Site Tools


manual:config:items:itemtypes:odbc_checks

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
manual:config:items:itemtypes:odbc_checks [2019/09/24 07:32]
martins-v logical reordering
manual:config:items:itemtypes:odbc_checks [2019/10/01 08:44] (current)
martins-v linking to an example of db.odbc.get
Line 105: Line 105:
  
 |//​Type// ​  ​|Select //Database monitor// here.   | |//​Type// ​  ​|Select //Database monitor// here.   |
-|//​Key// ​  ​|Enter one of the two supported item keys:\\ **db.odbc.select**[unique_description,​data_source_name] - this item is designed to return one value, i.e. the first column of the first row of the SQL query result. If a query returns more than one column, only the first column is read. If a query returns more than one line, only the first line is read.\\ **db.odbc.get**[unique_description,​data_source_name] - this item is capable of returning multiple rows/​columns in JSON format. Thus it may be used as a master item that collects all data in one system call, while JSONPath preprocessing may be used in dependent items to extract individual values.\\ This item is supported since Zabbix 4.4.\\ The unique description will serve to identify the item in triggers etc.\\ The data source name (DSN) must be set as specified in odbc.ini. ​ |+|//​Key// ​  ​|Enter one of the two supported item keys:\\ **db.odbc.select**[unique_description,​data_source_name] - this item is designed to return one value, i.e. the first column of the first row of the SQL query result. If a query returns more than one column, only the first column is read. If a query returns more than one line, only the first line is read.\\ **db.odbc.get**[unique_description,​data_source_name] - this item is capable of returning multiple rows/​columns in JSON format. Thus it may be used as a master item that collects all data in one system call, while JSONPath preprocessing may be used in dependent items to extract individual values. ​For more information,​ see an [[:​manual/​discovery/​low_level_discovery/​sql_queries#​using_dbodbcget|example]] of the returned format, used in low-level discovery. ​This item is supported since Zabbix 4.4.\\ The unique description will serve to identify the item in triggers etc.\\ The data source name (DSN) must be set as specified in odbc.ini. ​ |
 |//User name// ​  ​|Enter the database user name (optional if user is specified in odbc.ini) | |//User name// ​  ​|Enter the database user name (optional if user is specified in odbc.ini) |
 |//​Password// ​  ​|Enter the database user password (optional if password is specified in odbc.ini) | |//​Password// ​  ​|Enter the database user password (optional if password is specified in odbc.ini) |