E2E Tracing for Importer/Broker/Trigger model

[akashrv]

Problem
This is a placeholder feature and observability subgroup should drive detailed requirement and scope it down to 0.9, 0.9+
Minimal expectations from 0.9: End user should be able to trace an event all the way through the eventing pipeline from source to sink - Importer, Broker, Trigger.

• Identify gaps in current tracing and complete the scenario
• Document how an end user should enable and leverage tracing, under How To section in Knative.dev --> Eventing
• E2E tests Add E2E test for tracing #1318
• Leverage work done by serving
• fix [BUG] Broker pods die if tracing configmap is malformed on start #1417
• Do we want to define minimal tracing requirements for importers and channels data plane?

Persona:
Which persona is this feature for?
Event consumer, Event producer, and System integrator.

Exit Criteria
A measurable (binary) test that would indicate that the problem has been resolved.

Time Estimate (optional):
<subgroup to define this and scope it down to 0.9 and 0.9+>

Additional context (optional)
Please work with @lindydonna and @rgregg to validate the end user expectations from tracing.

[akashrv]

/milestone v0.9.0

[akashrv]

@adamharwayne @grantr

[daisy-ycguo]

/assign
I would like to take this issue.

[Harwayne]

Here is the work items I think I see for this: see #1755.

[Harwayne]

/close

Closing in favor of the general tracking issue #1755 and individual issues in the Observability project.

[knative-prow-robot]

@Harwayne: Closing this issue.

In response to this:

/close

Closing in favor of the general tracking issue #1755 and individual issues in the Observability project.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.