feat: support fullUrl in EndpointConfiguration to bypass default signal path appending#1723
Conversation
|
|
7dff583 to
5adb472
Compare
|
/easycla |
08e18f9 to
3f88171
Compare
|
Hi @breedx-splk, quick update, the line endings and detekt issues are The only remaining blocker is a conflict in android-agent/api/android-agent.api. Could you resolve it by running: ./gradlew :android-agent:apiDump and pushing to my branch? That should be the very last thing needed I'm really sorry for all the trouble and deeply appreciate your patience. |
e96f4e2 to
08c1644
Compare
breedx-splk
left a comment
There was a problem hiding this comment.
This seems like a reasonable approach to me...thanks for the contribution @Cloud-Architect-Emma!
There are two gradlew files that should not be part of this PR, as well as the .gitattributes, so lets get this removed and then move it forward. Thanks again for your patience!
|
Oh there are some compilation failures too in the |
eef4aa9 to
b930b22
Compare
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1723 +/- ##
==========================================
- Coverage 62.41% 62.06% -0.35%
==========================================
Files 160 159 -1
Lines 3480 3451 -29
Branches 353 351 -2
==========================================
- Hits 2172 2142 -30
- Misses 1209 1210 +1
Partials 99 99 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Hi @breedx-splk, all checks are now passing! I've addressed all your feedback:
Ready for your approval whenever you get a chance. Thank you so much for your patience throughout this whole process! |
|
@breedx-splk, PR passed all checks. Can you please review at your convenience? Thnaks |
…al path appending
b930b22 to
4500ff1
Compare
breedx-splk
left a comment
There was a problem hiding this comment.
Thanks for the contribution @Cloud-Architect-Emma! This is looking good to me now, and it's going to be useful for users to be able to customize the specific url for a given signal.
There's one result from this which is potentially odd looking, but I can't think of a better way of doing it that remains backwards compatible.
configuration = {
httpExport {
baseUrl = "http://10.0.2.2:4318"
logs {
url = "http://something.else.com"
fullUrl = "https://something.other.net/v1/whatever"
}
}
...
}I think that would be the worst case....and the solution IMO is pretty simple -- users shouldn't do that. :) Documentation is probably enough. 👍🏻
I would like the other @open-telemetry/android-maintainers to chime in as well before we merge. Thanks again for seeing this through.
fractalwrench
left a comment
There was a problem hiding this comment.
LGTM and thanks for the contribution. I agree that documentation should be sufficient to mitigate the comment @breedx-splk made.
Fixes #1712
Summary
When using
HttpExportConfiguration, the signal-specific paths (/v1/logs,/v1/traces,/v1/metrics) are always appended to the base URL. This makesit impossible to use a custom endpoint path like
/v2/logs.This PR adds a
fullUrlproperty toEndpointConfigurationthat, when set,bypasses the automatic path appending and uses the provided URL as-is.
Usage
httpExport { baseUrl = "https://example.com" logs { fullUrl = "https://example.com/v2/logs" // used as-is, no path appended } // traces still uses: https://example.com/v1/traces // metrics still uses: https://example.com/v1/metrics }Changes
fullUrl: String?property toEndpointConfigurationHttpExportConfigurationto usefullUrlwhen set, falling backto existing
url+ path behaviourHttpEndpointConnectivity.forTraces/forLogs/forMetricsto accepta
fullUrlflagNotes
This supersedes PR #1715 which had CLA identity issues.