You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I propose to add support for InfluxDB URLs that contain paths. As of today, the configuration is an URL, which kind of suggests that paths are supported – when in reality they are not. Here is an example:
Feature Request
Proposal:
I propose to add support for InfluxDB URLs that contain paths. As of today, the configuration is an URL, which kind of suggests that paths are supported – when in reality they are not. Here is an example:
Current behavior:
For the example above, telegraf will only extract the host name and port, and issue a request to e.g.
http://influxdb.example.com/query?…
Desired behavior:
telegraf should make use of the URI as well and issue a request to e.g.
http://influxdb.example.com/api/query?…
Use case: [Why is this important (helps with prioritizing requests)]
This feature will be very helpful for setups where InfluxDB resides behind a reverse proxy, such as nginx.
The text was updated successfully, but these errors were encountered: