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

feat(json-format): lowercase span name and service name as per swagger definition #166

Merged
merged 1 commit into from
Aug 10, 2020

Conversation

jcchavezs
Copy link
Contributor

@jcchavezs jcchavezs commented Aug 4, 2020

I just discovered the JSON V2 API expected the service names and the span names to be lower case. This PR address that.

image

image

https://zipkin.io/zipkin-api/\#/default/post_spans.

Ping @basvanbeek

@jcchavezs jcchavezs requested a review from basvanbeek August 4, 2020 12:50
@coveralls
Copy link

coveralls commented Aug 4, 2020

Coverage Status

Coverage decreased (-17.05%) to 43.516% when pulling 8a7ca06 on lowercase_span_name_and_service_name into ef1b344 on master.

@jcchavezs jcchavezs force-pushed the lowercase_span_name_and_service_name branch 7 times, most recently from 8a7ca06 to 284481c Compare August 10, 2020 15:00
@jcchavezs jcchavezs merged commit 6b3cdea into master Aug 10, 2020
@jcchavezs jcchavezs deleted the lowercase_span_name_and_service_name branch August 10, 2020 15:11
cuonglm added a commit to pomerium/pomerium that referenced this pull request Aug 17, 2020
Test needs to be changed to use lowercase name, as required by zipkin
JSON API v2 spec.

See: openzipkin/zipkin-go#166
cuonglm added a commit to pomerium/pomerium that referenced this pull request Aug 17, 2020
Test needs to be changed to use lowercase name, as required by zipkin
JSON API v2 spec.

See: openzipkin/zipkin-go#166
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