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

Fix OTLP/HTTP receiver's path to be /v1/traces #1979

Conversation

tigrannajaryan
Copy link
Member

OTLP/HTTP receiver was incorrectly expecting traces on /v1/trace.
OTLP spec require the path to be /v1/traces. This change adds /v1/traces
as a supported alias in the receiver to match what spec requires.

We will keep both paths supported for a while and then will eventually
retire /v1/trace.

Note that the OTLP/HTTP exporter already correctly uses /v1/traces path.

Fixes: #1968

@tigrannajaryan tigrannajaryan changed the title Fix OTLP/HTTP receiver's path for to be /v1/traces Fix OTLP/HTTP receiver's path to be /v1/traces Oct 19, 2020
@tigrannajaryan tigrannajaryan force-pushed the feature/tigran/otlp_rcv_http_traces_path branch from 2b91d5e to f582410 Compare October 19, 2020 15:28
@codecov
Copy link

codecov bot commented Oct 19, 2020

Codecov Report

Merging #1979 into master will increase coverage by 0.00%.
The diff coverage is 50.00%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #1979   +/-   ##
=======================================
  Coverage   91.43%   91.43%           
=======================================
  Files         280      280           
  Lines       16523    16526    +3     
=======================================
+ Hits        15108    15111    +3     
  Misses        979      979           
  Partials      436      436           
Impacted Files Coverage Δ
config/confighttp/confighttp.go 100.00% <ø> (ø)
receiver/otlpreceiver/otlp.go 92.30% <50.00%> (-2.36%) ⬇️
translator/internaldata/resource_to_oc.go 91.78% <0.00%> (+2.73%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 46aada6...33d0003. Read the comment docs.

OTLP/HTTP receiver was incorrectly expecting traces on /v1/trace.
OTLP spec require the path to be /v1/traces. This change adds /v1/traces
as a supported alias in the receiver to match what spec requires.

We will keep both paths supported for a while and then will eventually
retire /v1/trace.

Note that the OTLP/HTTP exporter already correctly uses /v1/traces path.

Fixes: open-telemetry#1968
@tigrannajaryan tigrannajaryan force-pushed the feature/tigran/otlp_rcv_http_traces_path branch from f582410 to 33d0003 Compare October 19, 2020 16:17
@bogdandrutu bogdandrutu merged commit 8286fe0 into open-telemetry:master Oct 19, 2020
@tigrannajaryan tigrannajaryan deleted the feature/tigran/otlp_rcv_http_traces_path branch October 19, 2020 17:37
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.

otlp receiver expects traces on “/v1/trace” but spec says “/v1/traces”.
2 participants