How to know if a zipkin receiver is enabled ?

[amrih-pg]

I was trying to following this : https://github.com/apache/skywalking/blob/06558fcf5ab6afc6eaf3b30aa0ca541545e2d3ea/docs/en/setup/zipkin/tracing.md

below are something that i have setup on my minikube:

export SKYWALKING_RELEASE_VERSION=4.4.0 
export SKYWALKING_RELEASE_NAME=skywalking
export SKYWALKING_RELEASE_NAMESPACE=default

helm install "${SKYWALKING_RELEASE_NAME}" \
  oci://registry-1.docker.io/apache/skywalking-helm \
  --version "${SKYWALKING_RELEASE_VERSION}" \
  -n "${SKYWALKING_RELEASE_NAMESPACE}" \
	--set ui.image.tag=9.2.0 \
  --set oap.image.tag=9.2.0 \
  --set oap.storageType=elasticsearch \
  --set elasticsearch.replicas=1 \
  --set oap.replicas=1 \
  --set env.SW_RECEIVER_ZIPKIN=default

the pods running:

Anything that i should look for ? e.g., oap logs

[amrih-pg]

You could see that i have a zipkin pod above. That's just a separate zipkin server for me to verify how to send to a zipkin endpoint e.g:

curl --location 'http://localhost:9411/api/v2/spans' \
--header 'Content-Type: application/json' \
--data '[
  {
    "traceId": "a03ee8fff1dcd9b9",
    "parentId": "f5f268651b2a2b34",
    "id": "15fc03927f0f68df",
    "kind": "CLIENT",
    "name": "post",
    "timestamp": 1571896375322000,
    "duration": 14000,
    "localEndpoint": {
      "serviceName": "mobile_api"
    },
    "remoteEndpoint": {
      "serviceName": "blt",
      "port": 31882
    },
    "tags": {
      "client_status_code": "200",
      "http.uri.client": "/visits",
      "request_budget": "9980",
      "tracer": "syslog2scribe.haproxy-synapse"
    }
  }
]'

I was trying to open port-forward of the OAP for 9411 port and hit the same endpoint. I couldn't get 202 Accepted status

[wu-sheng]

OAP logs would say zipkin receiver module is on with default provider.

[amrih-pg]

I will retry the installation.

I noticed that the "zipkin" port is not exposed:

Anything I missed here ?

[wu-sheng]

@wankai123

[wankai123]

The port is not exposed by default, you need to expose it by the Helm install --set.

https://github.com/apache/skywalking-kubernetes/blob/6df69f01882b4d58367687a661267d01e30e573c/chart/skywalking/values.yaml#L43

[amrih-pg]

Thanks @wankai123 .. will try this as well

[lxx95]

Hi all,

Trying to do something like @amrih-pg (as suggested here by @wu-sheng), exporting Zipkin traces starting from OTLP receiver.
Here my values.yaml to start the helm deployment:

oap:
  name: oap
  replicas: 1
  env:
    SW_OTEL_RECEIVER: default
    SW_RECEIVER_ZIPKIN: default
    SW_ZIPKIN_HTTP_COLLECTOR_ENABLED: true
    SW_OTEL_RECEIVER_ENABLED_HANDLERS: "oc, otlp"
  image:
    repository: skywalking.docker.scarf.sh/apache/skywalking-oap-server
    tag: 9.4.0  # Must be set explicitly
    pullPolicy: IfNotPresent
  storageType: "elasticsearch"
  ports:
    # add more ports here if you need, for example
    zipkin: 9411

ui:
  image:
    tag: 9.4.0

elasticsearch:
  imageTag: 7.5.1
  replicas: 1
  minimumMasterNodes: 1
  maxUnavailable: 0

fullnameOverride: "skywalking"

And my otel-collector:

receivers:
      otlp:
        protocols:
          grpc:
    exporters:
      zipkin:
        endpoint: "skywalking-oap.skywalking.svc.cluster.local:9411"
        tls:
          insecure: true
      logging:
processors:
      batch:
service:
      pipelines:
        traces:
          receivers: [otlp]
          processors: [batch]
          exporters: [zipkin, logging]

This error message has been shown for exporting phase (from otel-collector):
2023-05-04T14:56:27.171Z error exporterhelper/queued_retry.go:175 Exporting failed. No more retries left. Dropping data. {"kind": "exporter", "data_type": "traces", "name": "zipkin", "error": "max elapsed time expired failed to push trace data via Zipkin exporter: Post \"skywalking-oap.skywalking.svc.cluster.local:9411\": unsupported protocol scheme \"skywalking-oap.skywalking.svc.cluster.local\"", "dropped_items": 5}

The zipkin Skywalking OAP port was fine:
skywalking-oap ClusterIP 10.99.240.73 <none> 11800/TCP,12800/TCP,9411/TCP 27m

Thank you,
Luigi

[wu-sheng]

I think you need to ask OTEL community what does this mean?
We have tested Zipkin brave and Envoy Zipkin tracer, both work.

[wankai123]

I think the endpoint should be skywalking-oap.skywalking.svc.cluster.local:9411/api/v2/spans if your OAP URL is correct.
See: https://opentelemetry.io/docs/collector/configuration/#exporters

[lxx95]

Unfortunately I have tried also with that endpoint but the same error message has been shown. And yes, the OAP URL is correct, because I have evidences from native Skywalking agent to that endpoint on port 11800.

A new discussion on OTEL collector repo has been opened open-telemetry/opentelemetry-collector-contrib#21492. Hope that we can obtain other information about that error.