-
Notifications
You must be signed in to change notification settings - Fork 30
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
Add custom tracking module #1168
Add custom tracking module #1168
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The only thing I was considering is whether we should have the integration/instrumentation pair, but for this specific functionality, I think it's okay to have the instrumentation directly.
Yeah, I considered this as well. As there wasn't any configuration to be supplied to this module at this point, so thought we'll wait on that for now until it's clearly known that we need it. |
@@ -15,7 +15,7 @@ apply<ConfigAndroidLibrary>() | |||
apply<ConfigPublish>() | |||
|
|||
ext { | |||
set(artifactIdProperty, "$artifactPrefix${commonPrefix}otel-${project.name}") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe I missed the context here but how come we're removing the 'otel' part of this name?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As mentioned in the what PR covers bullet points - The published library name was earlier - rum-common-otel-otel which was changed to rum-common-otel
This PR covers the following:
:agent
module, for it to be available to customers using defaults directly.:common:otel
to hold certain re-usable constantrum-common-otel-otel
published library name torum-common-otel