Skip to content
This repository has been archived by the owner on Jun 19, 2022. It is now read-only.

GCP Broker Follows Eventing Conventions for Spans and Attributes. #1063

Closed
ian-mi opened this issue May 13, 2020 · 0 comments · Fixed by #1064
Closed

GCP Broker Follows Eventing Conventions for Spans and Attributes. #1063

ian-mi opened this issue May 13, 2020 · 0 comments · Fixed by #1064
Assignees
@ian-mi
Labels
area/broker kind/feature-request New feature or request priority/1 Blocks current release defined by release/* label or blocks current milestone release/1 storypoint/3
Milestone
v0.15.0-M3

Comments

@ian-mi
Copy link
Contributor

ian-mi commented May 13, 2020

Problem
knative/eventing#2983 defines tracing conventions for brokers that the GCP broker should implement.

Persona:
Event Consumer

Exit Criteria
Manual verification that conforming spans are emitted.

Time Estimate (optional):
3
@ian-mi ian-mi added the kind/feature-request New feature or request label May 13, 2020
@ian-mi ian-mi added this to the v0.15.0-M3 milestone May 13, 2020
@ian-mi ian-mi self-assigned this May 13, 2020
@ian-mi ian-mi added priority/1 Blocks current release defined by release/* label or blocks current milestone release/1 storypoint/3 labels May 13, 2020
@ian-mi ian-mi mentioned this issue May 13, 2020
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@ian-mi ian-mi

Labels
area/broker kind/feature-request New feature or request priority/1 Blocks current release defined by release/* label or blocks current milestone release/1 storypoint/3
Projects
None yet
Milestone
v0.15.0-M3
Development

Successfully merging a pull request may close this issue.

Broker tracing conventions ian-mi/knative-gcp
2 participants
@grantr @ian-mi