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 endpoint paths and signal-specific behavior (#200) #214

Merged
merged 8 commits into from
May 26, 2023

Conversation

tobert
Copy link
Collaborator

@tobert tobert commented May 25, 2023

This PR reworks endpoint handling to closer match the OTel spec and solve problems noticed in #200.

Amy Tobey added 8 commits May 23, 2023 13:36
Modified checkProcess to return a bool if the process met the expected
conditions. If it failed unexpectedly, checkAll will bail out of running
further checks on the data, so output is a lot less spammy.

Added "*" support to the check on diagnostics data strings.
Adds 2 tests to the regression suite to validate endpoints on general
get /v1/traces appended, and that signal endpoints do not.
Moved URL parsing to its own func, moving some code from the http/grpc
option paths to it, as well as starting to consider the "source" of
general (e.g. --endpoint, OTEL_EXPORTER_OTLP_ENDPOINT) or a signal
(e.g. --signal-endpoint or OTEL_EXPORTER_OTLP_TRACES_ENDPOINT). They are
treated differently now to match the spec.

Added tests for parseEndpoint.
e.g. "localhost", "127.0.0.1" are always going to go to gRPC, and when
no port is provided, should default to 4317.

Might need to check the spec. It probably doesn't allow for bare
hostname but otel-cli will because it should be easy to type.
@tobert tobert merged commit 2060787 into main May 26, 2023
@tobert tobert deleted the fix-endpoint-pathing branch May 26, 2023 16:31
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.

1 participant