Demo example not working

[jhengy]

Describe the bug
demo example not working, i.e. otel-collector 's prometheus exporter does not export metrics emitted by metrics-load-generator service as expected.

Steps to reproduce

• execute the following
  • cd examples/demo
  • docker-compose up -d
  • curl localhost:8889/metrics

What did you expect to see?
suppose to see metrics logs

What did you see instead?
No metrics logs are seen

What version did you use?
Version: otel/opentelemetry-collector-dev:latest

What config did you use?
Config: (e.g. the yaml config file)

Environment
OS: Ubuntu 18.04

Additional context
I executed the same procedure by setting OTELCOL_IMG=otel/opentelemetry-collector-dev:ffd2a1eb98980702fd642d8a9e4c270934e82e67 which points to the previous docker image, it works as expected, i.e. I get the following from doing curl localhost:8889/metrics:

# HELP promexample_opdemo_latency The various latencies of the methods
# TYPE promexample_opdemo_latency histogram
promexample_opdemo_latency_bucket{client="cli",label1="value1",method="repl",le="10"} 22
promexample_opdemo_latency_bucket{client="cli",label1="value1",method="repl",le="50"} 122
promexample_opdemo_latency_bucket{client="cli",label1="value1",method="repl",le="100"} 207
promexample_opdemo_latency_bucket{client="cli",label1="value1",method="repl",le="200"} 217
promexample_opdemo_latency_bucket{client="cli",label1="value1",method="repl",le="400"} 235
promexample_opdemo_latency_bucket{client="cli",label1="value1",method="repl",le="800"} 254
promexample_opdemo_latency_bucket{client="cli",label1="value1",method="repl",le="1000"} 266
promexample_opdemo_latency_bucket{client="cli",label1="value1",method="repl",le="1400"} 269
promexample_opdemo_latency_bucket{client="cli",label1="value1",method="repl",le="2000"} 271
promexample_opdemo_latency_bucket{client="cli",label1="value1",method="repl",le="5000"} 284
promexample_opdemo_latency_bucket{client="cli",label1="value1",method="repl",le="10000"} 296
promexample_opdemo_latency_bucket{client="cli",label1="value1",method="repl",le="15000"} 304
promexample_opdemo_latency_bucket{client="cli",label1="value1",method="repl",le="+Inf"} 309
promexample_opdemo_latency_sum{client="cli",label1="value1",method="repl"} 353812.62993700005
promexample_opdemo_latency_count{client="cli",label1="value1",method="repl"} 309
# HELP promexample_opdemo_line_counts The counts of the lines in
# TYPE promexample_opdemo_line_counts counter
promexample_opdemo_line_counts{client="cli",label1="value1",method="repl"} 857
# HELP promexample_opdemo_line_lengths The lengths of the various lines in
# TYPE promexample_opdemo_line_lengths histogram
promexample_opdemo_line_lengths_bucket{client="cli",label1="value1",method="repl",le="10"} 13
promexample_opdemo_line_lengths_bucket{client="cli",label1="value1",method="repl",le="20"} 20
promexample_opdemo_line_lengths_bucket{client="cli",label1="value1",method="repl",le="50"} 41
promexample_opdemo_line_lengths_bucket{client="cli",label1="value1",method="repl",le="100"} 92
promexample_opdemo_line_lengths_bucket{client="cli",label1="value1",method="repl",le="150"} 133
promexample_opdemo_line_lengths_bucket{client="cli",label1="value1",method="repl",le="200"} 170
promexample_opdemo_line_lengths_bucket{client="cli",label1="value1",method="repl",le="500"} 427
promexample_opdemo_line_lengths_bucket{client="cli",label1="value1",method="repl",le="800"} 674
promexample_opdemo_line_lengths_bucket{client="cli",label1="value1",method="repl",le="+Inf"} 857
promexample_opdemo_line_lengths_sum{client="cli",label1="value1",method="repl"} 427823.99999999977
promexample_opdemo_line_lengths_count{client="cli",label1="value1",method="repl"} 857
# HELP promexample_opdemo_process_counts The various counts
# TYPE promexample_opdemo_process_counts counter
promexample_opdemo_process_counts{client="cli",label1="value1",method="repl"} 309

[bogdandrutu]

@ccaraman this seems to be related to the TLS changes:

{"level":"warn","ts":1591279984.4496367,"caller":"queuedprocessor/queued_processor.go:190","msg":"Sender failed","component_kind":"processor","component_type":"queued_retry","component_name":"queued_retry","error":"rpc error: code = Unavailable desc = connection error: desc = "transport: authentication handshake failed: tls: first record does not look like a TLS handshake""}

[bogdandrutu]

@ccaraman the problem seems to be with "Insecure" because now the default value for this is "false" which means the default config for clients is to use TLS with no config

[bogdandrutu]

Also the log comes from the https://github.com/open-telemetry/opentelemetry-collector/blob/master/examples/demo/otel-collector-config.yaml which base on my best guess is caused by the Jaeger grpc exporter (possibly by the Zipkin exporter, but I don't think so).

[ccaraman]

I will work on this today. Apologies about the error.