-
Problem report
-
Resolution: Duplicate
-
Major
-
None
-
6.4.4, 7.0.0alpha2
-
Zabbix 6.4
Steps to reproduce:
- configure connector to a third party system
- receive value like 9.462244549013257e-05 from the monitored host
- send using connector
Result:
{
"host": {
"host": "<hostname>",
"name": "<hostname>"
},
"groups": [
"Our groups"
],
"item_tags": [
{
"tag": "Application",
"value": "Zabbix proxy"
}
],
"itemid": 314111,
"name": "Zabbix vmware cache, % used",
"clock": 1688736191,
"ns": 1279869,
"value":9.4622445490132566E-,
"type": 0
}
Expected:
Correct value sent through connector.
Notes:
{code:sql}zabbix=> \d+ history
Table "zabbix.history"
Column | Type | Collation | Nullable | Default | Storage | Compression | Stats target | Description
--------+------------------+-----------+----------+-----------------------+---------+-------------+--------------+-------------
itemid | bigint | | not null | | plain | | |
clock | integer | | not null | 0 | plain | | |
value | double precision | | not null | '0'::double precision | plain | | |
ns | integer | | not null | 0 | plain | | |
Indexes:
"history_pkey" PRIMARY KEY, btree (itemid, clock, ns)
"history_clock_idx" btree (clock DESC)
Triggers:
ts_insert_blocker BEFORE INSERT ON history FOR EACH ROW EXECUTE FUNCTION _timescaledb_internal.insert_blocker()
Child tables: _timescaledb_internal._hyper_1_1644_chunk,
_timescaledb_internal._hyper_1_1654_chunk,
...