Here is an easy to use query to reveal the tables which are not taking advantage of the special features of TimescaleDB, specifically retention policies, automatic moving, and high performance chunking.
In Creating a retention policy in TimescaleDB after the fact and realizing it's not even a hypertable we discussed the fact that the Telegraf TimescaleDB Postgres output plugin does not properly create hypertables automatically. I wrote the following query to reveal them easily:
At this point you can use the truncation method to quickly make them into hypertables, e.g.: