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

Add custom tracking module #1168

Merged

Conversation

surbhiia
Copy link
Contributor

@surbhiia surbhiia commented Feb 7, 2025

This PR covers the following:

  • Add custom tracking module with two public APIs
  • Add tests for same to sample app
  • Logging error if opentelemetry instance is null when these custom tracking APIs are called.
  • Add the module to :agent module, for it to be available to customers using defaults directly.
  • Add RumConstants in :common:otel to hold certain re-usable constant
  • Update rum-common-otel-otel published library name to rum-common-otel

@surbhiia surbhiia requested a review from a team as a code owner February 7, 2025 00:55
Copy link

@SenNeonoveNoci SenNeonoveNoci left a 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.

@surbhiia
Copy link
Contributor Author

surbhiia commented Feb 7, 2025

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}")
Copy link
Contributor

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?

Copy link
Contributor Author

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

@surbhiia surbhiia merged commit a320a82 into signalfx:feature/next-gen Feb 10, 2025
3 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Feb 10, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants