-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Make default InfluxDB client support custom HTTP endpoints #10294
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@Stale I'm still watching this and in need of this. AFAIK there is no workaround, so it's impossible to use the |
Is this still unavailable? This is a common use case for people deploying influxdb using containers, like with docker stack or kubernetes. Official Python client already have it: Even the third party Async Client has it: And the official CLI doesn't? Seems pretty trivial change to me. CLI has a https://docs.influxdata.com/influxdb/v1.7/tools/shell/#path If you need a setup you may use the Docker stack attached: Deploy stack with: docker stack deploy --compose-file=stack.yml influx Access InfluxDB with: curl -L -i http://127.0.0.1:8000/my/custom/path/ping?verbose=true Connect using Sync Python client with: from influxdb import InfluxDBClient
client = InfluxDBClient(host='127.0.0.1', port=8000, path='/my/custom/path/')
client.ping() |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
So every few months the stale bot tries to auto-close valid and accepted issues, and we have to keep spamming them in order to keep them open... |
I also have topic starter's problem!
It spends a lot of time for understanding, that it works!
|
Proposal:
Make it possible to connect to an InfluxDB instance running behind a reverse proxy with a custom subpath / endpoint with the default InfluxDB client
influx
.Current behavior:
I have InfluxDB, Grafana and nginx running as docker containers in a test VM at
192.168.122.26
.InfluxDB is exposed at
192.168.122.26/influxdb/
I can issue a ping command with
curl
but I can't log in usinginflux
:Desired behavior:
I'd like to be able to connect to a custom endpoint with
influx
. :)Use case:
I'm just getting started with InfluxDB but I'd like to be able to test the database with
influx
as the server is set up now. I might go back to just exposing the server directly via its default port and no endpoint instead if necessary.The text was updated successfully, but these errors were encountered: