-
Notifications
You must be signed in to change notification settings - Fork 5.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
influxdb - URLS' URI is ignored when sending HTTP request #2750
Comments
We had an issue about this recently: #2568. Can you tell me a little about why you need this, are you using a reverse proxy in front of influxdb as well? |
Thanks for the reply. Yes, it is almost the same scenario (reverse proxy between telegraf and influxdb). Enforcing security access implies in using a reverse proxy in some environments. Several workarounds exist, but they all have drawbacks:
I don't understand why appending URI cannot be supported as you mentioned in #2568. |
Is there a reason you cannot serve with the normal paths? If it is on the same box as influxdb you could bind influxdb only to the loopback interface and have your reverse proxy on the external interface. |
I'm trying to deploy telegraf within a 2 different SL (security levels) datacenter with several servers. As |
Sorry about all the questions, but the first step of adding a new feature is to justify the code change and increase in complexity. The reason you are not supposed to use |
Vote for this. Have the same issue with telegraf. |
Sorry if it sounded a little harsh. I understand that "just adding one feature" is not as simple as it sounds. |
I'm having the same issue. I might fix it if I find time. @danielnelson, does your concern about increased code complexity still hold? I'm not interested in contributing if rejection is guaranteed ;) The following NGINX hack might help for the times being. It relies on
|
@marcv81 We can add this, there is the PR referenced above but it has a bug. |
Will be in 1.5, thanks @dimrozakis |
Bug report
Relevant telegraf.conf:
System info:
Telegraf v1.2.1 (git: release-1.2 3b6ffb3)
Centos 7
Steps to reproduce:
urls
as shown in thetelegraf.conf
Expected behavior:
Telegraf would send http query requests to
https://localhost/influxdb/query
and http write requests tohttps://localhost/influxdb/write
Actual behavior:
Telegraf sends http query requests to
https://localhost/query
. Write requests should follow the same rule.Additional info:
This issue can potentially be a Feature Request as the documentation does not mention
URI
handling.The text was updated successfully, but these errors were encountered: