How to verify InfluxDB is running as it should?

Followed this guide: Optimize Your Home Assistant Database - SmartHomeScene
But not sure if InfluxDB is running. When i query “show measurements on homeassistant” nothing comes up. Retention policy is 2 years.
YAML from the dedicated influxdb.yaml file:

host: a0d7b954-influxdb
port: 8086
database: homeassistant
username: !secret influxdb_user
password: !secret influxdb_pass
max_retries: 3
default_measurement: state

i have split config and have also included the include statement in the configuration.yaml file.

However, still i see no sign of data coming into influxDB. How can i verify this / What could be wrong?
Screenshot of InfluxDB, where I try to run a simple query to see the tables:


Nothing is showing. When I click “homeassistant.2Y_Retention”, nothing comes up in the ‘Measurements & Tags’ column. However, when I click the “_internal.monitor” I see tables/measurements.

Of course I have double checked that the login credentials are correct. I have also:

Checked the user has admin privileges
Checked the database has a retention of 730d (2 years)
Tried changing host to the local IP of my home assistant instance (192.168.1.18) or localhost, but no change.

Checked logs of influxdb. It’s filled with these response lines, like it’s receiving something, but again, I can’t make it show anything.

time="2025-03-30T16:10:48+02:00" level=info msg="Response: OK" component=server method=GET remote_addr="127.0.0.1:54314" response_time="32.18µs" status=200

time="2025-03-30T16:10:48+02:00" level=info msg="Response: No Content" component=server method=GET remote_addr="127.0.0.1:54322" response_time="427.149µs" status=204

time="2025-03-30T16:10:48+02:00" level=info msg="Response: OK" component=server method=GET remote_addr="127.0.0.1:54328" response_time=1.8375ms status=200

time="2025-03-30T16:10:48+02:00" level=info msg="Response: OK" component=server method=GET remote_addr="127.0.0.1:54338" response_time="48.301µs" status=200

time="2025-03-30T16:10:48+02:00" level=info msg="Response: OK" component=server method=POST remote_addr="127.0.0.1:54354" response_time="734.258µs" status=200

time="2025-03-30T16:10:48+02:00" level=info msg="Response: OK" component=server method=POST remote_addr="127.0.0.1:54364" response_time="866.145µs" status=200

time="2025-03-30T16:10:48+02:00" level=info msg="Response: No Content" component=server method=GET remote_addr="127.0.0.1:54372" response_time="267.332µs" status=204

time="2025-03-30T16:10:48+02:00" level=info msg="Response: OK" component=server method=GET remote_addr="127.0.0.1:54384" response_time="117.217µs" status=200

time="2025-03-30T16:10:48+02:00" level=info msg="Response: OK" component=server method=POST remote_addr="127.0.0.1:54388" response_time="651.976µs" status=200

time="2025-03-30T16:10:48+02:00" level=info msg="Response: OK" component=server method=POST remote_addr="127.0.0.1:54398" response_time="547.191µs" status=200

time="2025-03-30T16:10:49+02:00" level=info msg="Response: OK" component=server method=GET remote_addr="127.0.0.1:54400" response_time="733.423µs" status=200

time="2025-03-30T16:10:49+02:00" level=info msg="Response: OK" component=server method=GET remote_addr="127.0.0.1:54406" response_time="692.968µs" status=200

time="2025-03-30T16:10:49+02:00" level=info msg="Response: No Content" component=server method=GET remote_addr="127.0.0.1:54408" response_time="298.002µs" status=204

time="2025-03-30T16:10:49+02:00" level=info msg="Response: OK" component=server method=GET remote_addr="127.0.0.1:54410" response_time="79.716µs" status=200

time="2025-03-30T16:10:49+02:00" level=info msg="Response: OK" component=server method=POST remote_addr="127.0.0.1:54416" response_time="613.226µs" status=200

time="2025-03-30T16:10:49+02:00" level=info msg="Response: OK" component=server method=POST remote_addr="127.0.0.1:54422" response_time="580.884µs" status=200

time="2025-03-30T16:10:49+02:00" level=info msg="Response: OK" component=server method=GET remote_addr="127.0.0.1:54426" response_time="794.047µs" status=200

time="2025-03-30T16:10:49+02:00" level=info msg="Response: OK" component=server method=GET remote_addr="127.0.0.1:54438" response_time="671.82µs" status=200

time="2025-03-30T16:10:49+02:00" level=info msg="Response: No Content" component=server method=GET remote_addr="127.0.0.1:54454" response_time="298.14µs" status=204

time="2025-03-30T16:10:49+02:00" level=info msg="Response: OK" component=server method=GET remote_addr="127.0.0.1:54466" response_time="136.892µs" status=200

time="2025-03-30T16:10:50+02:00" level=info msg="Response: OK" component=server method=POST remote_addr="127.0.0.1:54468" response_time="685.297µs" status=200

time="2025-03-30T16:10:50+02:00" level=info msg="Response: OK" component=server method=POST remote_addr="127.0.0.1:54478" response_time="513.246µs" status=200

ts=2025-03-31T03:37:10.303+02:00 lvl=error msg="error while sending usage report" service=reporting err="Post \"https://usage.influxdata.com/api/v1/usage/kapacitor\": dial tcp 0.0.0.0:443: connect: connection refused"

The last line I’m not sure about. It also seems like it is starting up with no errors:

-----------------------------------------------------------

Add-on: InfluxDB

Scalable datastore for metrics, events, and real-time analytics

-----------------------------------------------------------

Add-on version: 5.0.2

You are running the latest version of this add-on.

System: Home Assistant OS 15.0  (amd64 / qemux86-64)

Home Assistant Core: 2025.3.4

Home Assistant Supervisor: 2025.03.3

-----------------------------------------------------------

Please, share the above information when looking for help

or support in, e.g., GitHub, forums or the Discord chat.

-----------------------------------------------------------

s6-rc: info: service base-addon-banner successfully started

s6-rc: info: service fix-attrs: starting

s6-rc: info: service base-addon-timezone: starting

s6-rc: info: service base-addon-log-level: starting

s6-rc: info: service fix-attrs successfully started

[15:36:59] INFO: Configuring timezone (Europe/Copenhagen)...

s6-rc: info: service base-addon-log-level successfully started

s6-rc: info: service base-addon-timezone successfully started

s6-rc: info: service legacy-cont-init: starting

cont-init: info: running /etc/cont-init.d/create-users.sh

cont-init: info: /etc/cont-init.d/create-users.sh exited 0

cont-init: info: running /etc/cont-init.d/influxdb.sh

cont-init: info: /etc/cont-init.d/influxdb.sh exited 0

cont-init: info: running /etc/cont-init.d/kapacitor.sh

cont-init: info: /etc/cont-init.d/kapacitor.sh exited 0

cont-init: info: running /etc/cont-init.d/nginx.sh

cont-init: info: /etc/cont-init.d/nginx.sh exited 0

s6-rc: info: service legacy-cont-init successfully started

s6-rc: info: service legacy-services: starting

services-up: info: copying legacy longrun chronograf (no readiness notification)

services-up: info: copying legacy longrun influxdb (no readiness notification)

services-up: info: copying legacy longrun kapacitor (no readiness notification)

services-up: info: copying legacy longrun nginx (no readiness notification)

[15:36:59] INFO: Kapacitor is waiting until InfluxDB is available...

[15:36:59] INFO: Chronograf is waiting until InfluxDB is available...

[15:36:59] INFO: Starting the InfluxDB...

s6-rc: info: service legacy-services successfully started

[15:37:10] INFO: Starting the Kapacitor

[15:37:10] INFO: Starting Chronograf...

2025/03/30 15:37:10 Using configuration at: /etc/kapacitor/kapacitor.conf

'##:::'##::::'###::::'########:::::'###:::::'######::'####:'########::'#######::'########::

##::'##::::'## ##::: ##.... ##:::'## ##:::'##... ##:. ##::... ##..::'##.... ##: ##.... ##:

##:'##::::'##:. ##:: ##:::: ##::'##:. ##:: ##:::..::: ##::::: ##:::: ##:::: ##: ##:::: ##:

#####::::'##:::. ##: ########::'##:::. ##: ##:::::::: ##::::: ##:::: ##:::: ##: ########::

##. ##::: #########: ##.....::: #########: ##:::::::: ##::::: ##:::: ##:::: ##: ##.. ##:::

##:. ##:: ##.... ##: ##:::::::: ##.... ##: ##::: ##:: ##::::: ##:::: ##:::: ##: ##::. ##::

##::. ##: ##:::: ##: ##:::::::: ##:::: ##:. ######::'####:::: ##::::. #######:: ##:::. ##:

..::::..::..:::::..::..:::::::::..:::::..:::......:::....:::::..::::::.......:::..:::::..::

ts=2025-03-30T15:37:10.279+02:00 lvl=error msg="error while sending usage report on startup" service=reporting err="Post \"https://usage.influxdata.com/api/v1/usage/kapacitor\": dial tcp 0.0.0.0:443: connect: connection refused"

time="2025-03-30T15:37:13+02:00" level=info msg="Serving chronograf at http://127.0.0.1:8889" component=server

time="2025-03-30T15:37:13+02:00" level=info msg="Reporting usage stats" component=usage freq=24h reporting_addr="https://usage.influxdata.com" stats="os,arch,version,cluster_id,uptime"

[15:37:13] INFO: Starting NGINX...