zalando / zalando/skipper

OpenTracing, proxy span not visible

Open
#1,237 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

needs-investigation
Dominant language
Go
Stars
3.3k
Forks
407
Avg merge
1d 8h
Merged PRs (30d)
46

Description

Describe the bug
In some cases, the proxy opentracing span is missing, while the filter processing spans are not.

no-proxy-span

the above screenshot should contain a proxy span. Checked on multiple traces.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the missing proxy span using the traces described in the issue and compare them with traces where filter-processing spans appear. Read the OpenTracing instrumentation around proxy and filter processing, then add or update a focused test demonstrating the expected proxy span and verify it appears in the trace.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend, observability
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.