Closed xsolinsx closed 1 year ago
Hey @xsolinsx
have you looked at the Bring your own InfluxDB
section of the troubleshooting guide?
that should provide you with all the buckets & tasks necessary to get Scrutiny working
Yes, I have followed the instructions and created the appropriate tasks/buckets with the curl commands
can you add the DEBUG=true
environmental variable to the scrutiny container?
still obtain nothing else but
2022/10/02 16:10:31 Loading configuration file: /opt/scrutiny/config/scrutiny.yaml 2022/10/02 16:10:37 Loading configuration file: /opt/scrutiny/config/scrutiny.yaml 2022/10/02 16:10:51 Loading configuration file: /opt/scrutiny/config/scrutiny.yaml
My influxdb part on scrutiny.yaml
, and you can try to manually start collector to check will the API connect influxdb correctly
influxdb:
host: db
port: 8086
token: 'scrutinytoken'
org: 'scrutinyorg'
bucket: 'scrutiny'
Oh god I feel so stupid, I just reviewed my scrutiny.yaml file and there is an additional indentation level for the token, org and bucket fields I'm sorry I didn't notice, now it's working 🤦🏻♂️
weird, I wouldn't have expected a silent failure like that though. I'm glad you figured this out, but I'll try to add some extra logging in the future.
Describe the bug As I already have an influxdb instance I am using the separate setup, I have edited the docker compose hub/spoke setup to accomodate for my needs. Scrutiny does not load the configuration. No error is given.
Expected behavior Scrutiny does load the configuration and starts correctly (as the collector with the same setup is doing).
Screenshots
Log Files Docker logs:
docker compose file section of scrutiny
No log file is present in the conf volume
docker info output
scrutiny.yaml