Weird measurements in InfluxDB bucket

,
1

Hey guys,

I am new to InfluxDB and Telegraf so I am a bit overwhelmed by everything.
I have a window sensor that is using zigbee to communicate.
Furthermore I have an Zigbee2MQTT Docker container that pushes the messages pushed by the sensor into a topic (homeassistant/rooms/bedroom/window).
I use an MQTT which is also running in a docker container.
Communcation between thos two is okay as I can subscribe to homeassistant/rooms/# and see the message once I close the window contact.

Now I want to use Telegraf to get the messages into InfluxDB. The sensor sends more data than I need so I want to parse it.
Telegraf is configured to listen to homeassistant/rooms/#
Everything seems to work fine as the measurement is correctly parsed and added to my homeassistant bucket with the correct measurement name.

However as I tried to get my hands on the data explorer of my DB (which is also running in a container) I saw many, many measurements. I tried to get a list of them but I did not get it to work with influx cli (I did not even get to get a list of my buckets as I always got an empty list but thats another problem.

Here is a example list of measurements I have in my bucket:

  • bedroom (which is the measurement I want to have, with field isWindowClosed)
  • boltdb_reads_total
  • boltdb_writes_total
  • go_gc_duration_seconds
  • go_info
  • go_memstats_frees_total
  • a lot more go_memstats
  • http_api_requests_total (and many more http related measurements)
  • influxdb_info
  • influxdb_remotes_total (many more influx related measurements)
  • qc_all_active (and many more qc related measurements)
  • service_bucket_new_call_total (many more service related measurements)
  • storage_user_new_duration (many more storage related measurements)
  • task_scheduler_execute_delta (and some more task related)

I tried to get behind all these but I do not even know where to start.
Is this a Telegraf problem or did I misconfigure something else?

I hope someone could explain to me what is going on.

Thanks in advance,

Tim

2

Stupid error: Did not get that the measurments of influx are automatically written into the first created bucket if I choose get started on initialization

3

I too want to know the reason of this. Then what should be the best (smooth) option to create a new bucket so that it does not create unnecessary measurements at the beginning.
Please replay asap
@scott @tiko

4

I’m suffering from the same issue. The biggest problem is that because of that my bucket is already 39GB of size, after a year of pushing just 10 messages every hour.

@tiko can you share your way of fixing this?

5

Hmmm, I created a new bucket and copied only the measurements I’m interested in:

import "influxdata/influxdb/schema"

from(bucket: "speedtest-tracker")
  |> range(start: 1970-01-01T00:00:00Z)
  |> filter(fn: (r) => r._measurement == "speedtest")
  |> to(bucket: "speedtest-clean")

Then I deleted the speedtest-tracker, created a new one with the same name, and imported the data back the same way.

At this point I have no idea where do those internal influxdb measurements are being saved. Should I care? :thinking: