Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correctly store the commonTags in for later use in Lightstep span sink #388

Closed
wants to merge 1 commit into from

Conversation

sdboyer-stripe
Copy link
Contributor

Summary

A set of commonTags were provided to the Lightstep span sink, but they
were not permanently recorded into the struct; as such, no common tags
were ever applied to outgoing spans.

Motivation

Seems like a pretty clear bug?

Test plan

Simple addition to a relevant test.

Rollout/monitoring/revert plan

A set of commonTags were provided to the Lightstep span sink, but they
were not permanently recorded into the struct; as such, no common tags
were ever applied to outgoing spans.
@stripe-ci
Copy link

Gerald Rule: Copy Observability on Veneur and Unilog pull requests

cc @stripe/observability
cc @stripe/observability-stripe

@sdboyer-stripe sdboyer-stripe changed the title Correctly store the commonTags for later use Correctly store the commonTags in for later use in Lightstep span sink Feb 16, 2018
@cory-stripe
Copy link
Contributor

Eep! Can you audit the Kafka sink as well? I had a note it might have this problem…

@sdboyer-stripe
Copy link
Contributor Author

Hmm, right now, the kafka sink doesn't appear to support even the concept of common tags - they're missing entirely. Do they need to be added?

@sdboyer-stripe
Copy link
Contributor Author

Closing this now, it's not actually how we want commonTags to behave.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants