Zabbix Documentation 4.2

3.04.05.0 (current)| In development:5.2 (devel)| Unsupported:1.82.02.22.43.23.44.24.4Guidelines

User Tools

Site Tools


manual:appendix:install:timescaledb

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
manual:appendix:install:timescaledb [2020/03/06 07:08]
martins-v non-default schema situation with Timescale DB
manual:appendix:install:timescaledb [2020/03/06 13:12]
martins-v more precise wording
Line 10: Line 10:
 === Configuration === === Configuration ===
  
-We assume that TimescaleDB extension has been already installed ​in the database (see [[https://​docs.timescale.com/​latest/​getting-started/​installation|installation instructions]]).+We assume that TimescaleDB extension has been already installed ​on the database ​server ​(see [[https://​docs.timescale.com/​latest/​getting-started/​installation|installation instructions]]).
  
 TimescaleDB extension must also be enabled for the specific DB by executing: TimescaleDB extension must also be enabled for the specific DB by executing:
Line 18: Line 18:
 Running this command requires database administrator privileges. ​ Running this command requires database administrator privileges. ​
  
-<​note>​By default TimescaleDB stores all of its functions in '​public'​ schema. Zabbix cannot access TSDB's functions (such as ''​drop_chunks()''​) if DBSchema is set to some non-default value in the server config. ​If you use a database schema other than '​public'​ you need to add a SCHEMA clause to the command above. E.g.:\\ ''​echo %%"​%%CREATE EXTENSION IF NOT EXISTS timescaledb SCHEMA yourschema CASCADE;​%%"​%% | sudo -u postgres psql zabbix''</​note>​+<​note>​If you use a database schema other than '​public'​ you need to add a SCHEMA clause to the command above. E.g.:\\ ''​echo %%"​%%CREATE EXTENSION IF NOT EXISTS timescaledb SCHEMA yourschema CASCADE;​%%"​%% | sudo -u postgres psql zabbix''</​note>​
  
 Then run the ''​timescaledb.sql''​ script located in database/​postgresql: ​ Then run the ''​timescaledb.sql''​ script located in database/​postgresql: ​