Thanks, in the end the “bucket name not found” was caused by a problem in my output config, please see here: Error parsing tagpass in telegraf.conf. So it’s possible it would not have been able to display the bucket name anyway, but for others trying to access a non-existent bucket it would be useful to see the name and fix their influxdb2 setup.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Second set of eyes on my MQTT Telegraf config file please | 3 | 438 | October 14, 2021 | |
| Problems publishing to InfluxDB | 1 | 478 | April 16, 2020 | |
| Telegraf writes but nothing in Data Explorer !? [Solved] | 2 | 1120 | August 8, 2022 | |
| Not able to get Telegraf to write mqtt messages to influxDB | 1 | 327 | October 30, 2023 | |
| [outputs.influxdb_v2] When writing to https://url: failed to write metric to bucket (401 Unauthorized): unauthorized: unauthorized access | 4 | 641 | January 22, 2025 |
