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

Make zipkin tag value length configurable #1151

Merged
merged 2 commits into from
Sep 24, 2020

Conversation

owais
Copy link
Contributor

@owais owais commented Sep 23, 2020

Description

Zipkin exporter truncates tag values to a maximum length of 128
characters. This commit makes this value configurable while keeping
128 as the default value.

The change required to move some functions to the zipkin exporter class. This has a nice side-effect of the zipkin exporter becoming a bit more customizable by sub-classing it. It can especially be very useful for vendor distributions.

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

  • Added unit test

Checklist:

  • Followed the style guidelines of this project
  • Changelogs have been updated
  • Unit tests have been added
  • Documentation has been updated

@owais owais requested a review from a team September 23, 2020 23:40
@owais owais changed the title Make zipkin tag value length configurable WIP: Make zipkin tag value length configurable Sep 24, 2020
@owais owais force-pushed the configurable-zipkin-tag-size branch 4 times, most recently from 663ac6e to c72d409 Compare September 24, 2020 00:36
@owais owais changed the title WIP: Make zipkin tag value length configurable Make zipkin tag value length configurable Sep 24, 2020
@owais owais force-pushed the configurable-zipkin-tag-size branch from c72d409 to 58f3134 Compare September 24, 2020 01:40
Copy link
Contributor

@codeboten codeboten left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor change requested, otherwise it looks good.

@@ -2,6 +2,8 @@

## Unreleased

- Zipkin exporter now accepts a ``max_tag_value_length`` attribute to customize the maximum allowed size a tag value can have.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Link the PR?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added

Zipkin exporter truncates tag values to a maximum length of 128
characters. This commit makes this value configurable while keeping
128 as the default value.
@owais owais force-pushed the configurable-zipkin-tag-size branch from ffc4660 to 480a061 Compare September 24, 2020 13:50
Copy link
Contributor

@codeboten codeboten left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@codeboten codeboten merged commit c1ec444 into open-telemetry:master Sep 24, 2020
owais added a commit to owais/opentelemetry-python that referenced this pull request Sep 25, 2020
Zipkin exporter truncates tag values to a maximum length of 128
characters. This commit makes this value configurable while keeping
128 as the default value.
@owais owais deleted the configurable-zipkin-tag-size branch September 25, 2020 02:57
srikanthccv pushed a commit to srikanthccv/opentelemetry-python that referenced this pull request Nov 1, 2020
* chore: add missing span sampling test

* chore: add additional sampling test

Co-authored-by: Daniel Dyla <dyladan@users.noreply.github.com>
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