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

jaeger-agent: --log-level flag not recognized #803

Closed
cboggs opened this issue May 4, 2018 · 1 comment · Fixed by #828
Closed

jaeger-agent: --log-level flag not recognized #803

cboggs opened this issue May 4, 2018 · 1 comment · Fixed by #828

Comments

@cboggs
Copy link

cboggs commented May 4, 2018

The 1.4.1 release of jaeger agent doesn't appear to include the --log-level flag as indicated here and here.

Attempt results:

> docker run -it jaegertracing/jaeger-agent:1.4.1 /go/bin/agent-linux --log-level=warn
Error: unknown flag: --log-level
Usage:
  jaeger-agent [flags]
  jaeger-agent [command]

Available Commands:
  help        Help about any command
  version     Print the version

Flags:
      --collector.host-port string                            comma-separated string representing host:ports of a static list of collectors to connect to directly (e.g. when not using service discovery)
      --config-file string                                    Configuration file in JSON, TOML, YAML, HCL, or Java properties formats (default none). See spf13/viper for precedence.
      --discovery.min-peers int                               if using service discovery, the min number of connections to maintain to the backend (default 3)
  -h, --help                                                  help for jaeger-agent
      --http-server.host-port string                          host:port of the http server (e.g. for /sampling point and /baggage endpoint) (default ":5778")
      --metrics-backend string                                Defines which metrics backend to use for metrics reporting: expvar, prometheus, none (default "prometheus")
      --metrics-http-route string                             Defines the route of HTTP endpoint for metrics backends that support scraping (default "/metrics")
      --processor.jaeger-binary.server-host-port string       host:port for the UDP server (default ":6832")
      --processor.jaeger-binary.server-max-packet-size int    max packet size for the UDP server (default 65000)
      --processor.jaeger-binary.server-queue-size int         length of the queue for the UDP server (default 1000)
      --processor.jaeger-binary.workers int                   how many workers the processor should run (default 10)
      --processor.jaeger-compact.server-host-port string      host:port for the UDP server (default ":6831")
      --processor.jaeger-compact.server-max-packet-size int   max packet size for the UDP server (default 65000)
      --processor.jaeger-compact.server-queue-size int        length of the queue for the UDP server (default 1000)
      --processor.jaeger-compact.workers int                  how many workers the processor should run (default 10)
      --processor.zipkin-compact.server-host-port string      host:port for the UDP server (default ":5775")
      --processor.zipkin-compact.server-max-packet-size int   max packet size for the UDP server (default 65000)
      --processor.zipkin-compact.server-queue-size int        length of the queue for the UDP server (default 1000)
      --processor.zipkin-compact.workers int                  how many workers the processor should run (default 10)

Use "jaeger-agent [command] --help" for more information about a command.

unknown flag: --log-level
@carlislk
Copy link

Any updates on this issue? Possibly supported as an env variable?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants