Skip to content
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

Cannot configure multiple graphite listeners via env variables? #7726

Closed
kklocek opened this issue Dec 15, 2016 · 3 comments
Closed

Cannot configure multiple graphite listeners via env variables? #7726

kklocek opened this issue Dec 15, 2016 · 3 comments

Comments

@kklocek
Copy link

kklocek commented Dec 15, 2016

Bug report

System info: InfluxDB, version v1.0.2, branch master, commit ff30704. Mac OS X Sierra . Tested locally, also tested on dockerized version of 1.1

Steps to reproduce:

  1. I need to configure two graphite listeners, one on UDP (port 2004) and other on TCP (port 2003)
  2. I set some env variables (not all because lots of them are defaults):
INFLUXDB_GRAPHITE_1_ENABLED=true
INFLUXDB_GRAPHITE_1_PROTOCOL=udp
INFLUXDB_GRAPHITE_1_BIND_ADDRESS=:2004
INFLUXDB_GRAPHITE_1_DATABASE=test
INFLUXDB_GRAPHITE_0_PROTOCOL=tcp
INFLUXDB_GRAPHITE_ENABLED=true
  1. I run influxd and in logs I can see
...
[httpd] 2016/12/15 11:34:36 Listening on HTTP: [::]:8086
[retention] 2016/12/15 11:34:36 Starting retention policy enforcement service with check interval of 30m0s
[monitor] 2016/12/15 11:34:36 Storing statistics in database '_internal' retention policy 'monitor', at interval 10s
[graphite] 2016/12/15 11:34:36 Starting graphite service, batch size 5000, batch timeout 1s
[monitor] 2016/12/15 11:34:36 'graphite:tcp::2003' registered for diagnostics monitoring
[graphite] 2016/12/15 11:34:36 Listening on TCP: [::]:2003
  1. If I do it via config file it works

Expected behavior: run two graphite listeners on two ports, which I can set via env variables

Actual behavior: if I set configuration via env variable only one graphite listeners is started (from configuration INFLUXDB_GRAPHITE_0)

Additional info: vars, stats, diagnostics

I looked through the docs but I think there is an error there also - on config I see:

Note: To set or override settings in a config section that allows multiple configurations (any section with [[double_brackets]] in the header supports multiple configurations), the desired configuration must be specified by ordinal number. For example, for the first set of [[graphite]] environment variables, prefix the configuration setting name in the environment variable with the relevant position number (in this case: 0):

...
INFLUXDB_GRAPHITE_0_PROTOCOL
...

For the Nth Graphite configuration in the configuration file, the relevant environment variables would be of the form INFLUXDB_GRAPHITE_(N-1)_BATCH_PENDING. For each section of the configuration file the numbering restarts at zero.

but in a graphite section i see:

protocol = “tcp”

Set to tcp or udp.

Environment variable: INFLUXDB_GRAPHITE_PROTOCOL
@jwilder
Copy link
Contributor

jwilder commented Dec 15, 2016

This might be fixed when #7323 is merged.

@stale
Copy link

stale bot commented Jul 24, 2019

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 stale bot added the wontfix label Jul 24, 2019
@stale
Copy link

stale bot commented Jul 31, 2019

This issue has been automatically closed because it has not had recent activity. Please reopen if this issue is still important to you. Thank you for your contributions.

@stale stale bot closed this as completed Jul 31, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants