search

henrikrexed / openfeature

1 stars 0 forks source link

oteld-collector health_check service does not exist #10

Open agardnerIT opened 1 year ago

agardnerIT commented 1 year ago 
$ kubectl logs oteld-collector-zdjj6
2023/01/31 04:11:53 proto: duplicate proto type registered: jaeger.api_v2.PostSpansRequest
2023/01/31 04:11:53 proto: duplicate proto type registered: jaeger.api_v2.PostSpansResponse
Error: failed to get config: invalid configuration: service references extension "health_check" which does not exist
2023-01-31 04:11:53.978942 I | collector server run finished with error: failed to get config: invalid configuration: service references extension "health_check" which does not exist

Perhaps this needs to be added?

...
processors:
...
extensions:
  health_check: {}
    endpoint: 0.0.0.0:8889
  logging:

service:
  extensions: [health_check]
agardnerIT commented 1 year ago

This resulted in:

$ kubectl logs oteld-collector-89pkk
2023/01/31 06:26:05 proto: duplicate proto type registered: jaeger.api_v2.PostSpansRequest
2023/01/31 06:26:05 proto: duplicate proto type registered: jaeger.api_v2.PostSpansResponse
Error: failed to get config: cannot resolve the configuration: cannot retrieve the configuration: yaml: line 14: did not find expected key
2023-01-31 06:26:05.899372 I | collector server run finished with error: failed to get config: cannot resolve the configuration: cannot retrieve the configuration: yaml: line 14: did not find expected key

Setting to extensions: [] got the pods running.