-
-
Notifications
You must be signed in to change notification settings - Fork 182
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG/DOCUMENTATION] TROUBLESHOOTING_INFLUXDB doc #741
Comments
Good catch, those env variables should be prefixed with |
Hmmm, unfortunately SCRUTINY_INFLUXDB_HOSTNAME doesnt seem to work either - its still trying to connect to db at localhost. I can see a different behaviour if i use SCRUTINY_WEB_INFLUXDB_HOST, but it still doesnt work - for some reason if i put the influxdb server IP address in SCRUTINY_WEB_INFLUXDB_HOST, then its trying to connect to database at my DNS server IP (different one) and port |
Ok i think i have it:
So it should be SCRUTINY_WEB_INFLUXDB_HOST, but unlike the documentation just IP number without the schema and port? [edit] does it look correct for you? im not sure if Scrutiny has done that automatic setup though - it didnt want to connect until i create the org and bucket. |
ah, sorry we must have nested the influx configuration under the web key in the config. Yes, |
Describe the bug
Hi. Im trying to set up the docker version (web/collector) of Scrutiny with an existing InfluxDB instance running on a different host. It seems that the env variables mentioned in the documentation (https://github.com/AnalogJ/scrutiny/blob/master/docs/TROUBLESHOOTING_INFLUXDB.md) are not correct. Particularly after setting up INFLUXDB_HOSTNAME to external host, Scrutiny is still looking for InfluxDB on localhost.
Expected behavior
After setting up the variables INFLUXDB_ADMIN_TOKEN, INFLUXDB_ORG_ID, INFLUXDB_HOSTNAME, Scrutiny should connect to the database and set it up using admin token.
Screenshots
![image](https://private-user-images.githubusercontent.com/313674/403335393-02b0e1d9-8310-427c-ad45-83a560278ce2.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzg5MTEwOTEsIm5iZiI6MTczODkxMDc5MSwicGF0aCI6Ii8zMTM2NzQvNDAzMzM1MzkzLTAyYjBlMWQ5LTgzMTAtNDI3Yy1hZDQ1LTgzYTU2MDI3OGNlMi5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjA3JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIwN1QwNjQ2MzFaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT01MmNlZmQ0YThhYzgxZjFmNzk4YmE4ZWY2YjJkYmM1OWQ1YWNkNTkyZDE3OWQ0NjE4MDg4Y2NmMDZjZDQ5NjJmJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.KYT0F_qTcRGRSqqsDBe4yAzgqeogryNhHjEvl33vQG8)
Log Files
The log files will be available on your host in the
config
directory. Please attach them to this issue.Please also provide the output of
docker info
The text was updated successfully, but these errors were encountered: