Uploaded image for project: 'Distributed Tracing'
  1. Distributed Tracing
  2. TRACING-5670

[RHOSDT 3.7] Network policies mis-match to OTC configuration of receivers

XMLWordPrintable

    • Tracing Sprint # 278

      With a configured OTEL collector or

      jaeger:
  protocols:
    thrift_compact:
      endpoint: 0.0.0.0:6831
otlp:
  protocols:
    grpc:
      endpoint: 0.0.0.0:4317
    http:
      endpoint: 0.0.0.0:4318

      we end up with a Network policy looking like

      oc get networkpolicies user-collector-networkpolicy -o yaml | yq -ry '.spec.ingress[]|.ports'
- port: 8888
  protocol: TCP
- port: 4317
  protocol: TCP
- port: 4318
  protocol: TCP
- port: 6831
  protocol: TCP
- port: 8889
  protocol: TCP

      Port 8888 get's explained with

      $ oc get opentelemetrycollector user -o yaml | yq -ry .spec.config.service.telemetry
metrics:
  readers:
    - pull:
        exporter:
          prometheus:
            host: 0.0.0.0
            port: 8888

      but port 8889 is not referenced in the configuration neither is there any listening service for it in the pod

      $ oc exec -ti user-collector-65596f576b-4bvg7 -- cat /proc/net/tcp | netstat_p | grep 8889 | wc -l 
0

              ploffay@redhat.com Pavol Loffay
              rhn-support-milang Michaela Lang
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: