Closed remz1337 closed 6 months ago
Food for thought, maybe have the collector write directly to influxdb, without going through the webapp
Hey @remz1337 were you following the INFLUXDB troubleshooting instructions? https://github.com/AnalogJ/scrutiny/blob/master/docs/TROUBLESHOOTING_INFLUXDB.md
Specifically the section titled Bring your own InfluxDB
oh, I did not see that. Thanks for pointing it out! It would be nice to have that link in the manual installation section of the README. Awesome library, thanks for your work :)
Describe the bug I have a Proxmox server with a few LXC, including influxdb that already has a few buckets (including proxmox stats). Thus, I want to reuse that influxdb server by adding a bucket for scrutiny and generate an API token with minimal access to improve security and avoid messing with my other data. My influxdb has a single organization with a few buckets. I created a
scrutiny
bucket and generated an API token with read/write access only to that bucket (+ Read toAll org
and read/write toAll tasks
).Scrutiny throws the following error:
panic: unauthorized: write:orgs/7dfc21b40d851f55/buckets is unauthorized
I fixed it by generating a new API token with read/write on
All buckets
.Expected behavior Maybe I'm missing something, I don't understand why Scrutiny would need write on my other buckets. Expected behaviour: write access only on bucket defined in config.
Screenshots If applicable, add screenshots to help explain your problem.
Log Files