Closed alpex8 closed 1 month ago
Hi,
The uint support is only used if the metric value that is read in is of the uint64 type. See here:
I'm not sure where the value of tag_id comes from, but the values from the CPU plugin are not uint64, so there is no need to return a uint64.
Ah I see, thanks for the explanation.
I might have gotten a bit confused. In the configuration I attached the tags are saved in a separate table and the relation to that tag-table is given via the values in the tag_id
column. However I have seen negative values in that tag_id
column.
So because I enabled the property for using the uint types, I thought there is a bug in the table setup and the written values have suffered from an overflow.
Also with the given config (pretty much from the examples given in the plugin README.d) there isn´t any foreign key constraint between field and tag table, but I´m not sure whether this might be intentional for better performance.
So if you are still confident the actual behavior is as expected than feel free to close this issue. :)
Thanks for following up.
the tags are saved in a separate table and the relation to that tag-table is given via the values in the tag_id column
Ah thanks for clarifying. Yeah I would only expect the uint8 support to be on actual data you are writing from Telegraf.
So if you are still confident the actual behavior is as expected than feel free to close this issue. :)
will do.
Relevant telegraf.conf
Logs from Telegraf
System info
Telegraf 1.30.3, Docker version 26.1.3
Docker
No response
Steps to reproduce
Containerfile
db_seed.sh
docker-compose.yml
telegraf.conf
docker-compose build
docker-compose up -d timescale
# avoid errors in telegraf logs during DB startup timedocker-compose up -d
docker exec -it timescale bash
psql -U postgres -d timeseries
\d cpu
Expected behavior
tag_id
column has typeuint8
.Actual behavior
tag_id
column has typebigint
.Additional info
Verify that extension uint is installed properly.