SessionId is missing when `OpenTelemetryRumBuilder.build()` is used.

[gopal-vunet]

SessionId is missing when OpenTelemetryRumBuilder.buil() is used instead of the new OpenTelemetryRumInitializer.initialize function.

It seems the SessionProvider is missing. But to set the session provider manually there is no SessionProvider implementation available. The existing implementationSessionManager is an internal class so it is not accessible.

[LikeTheSalad]

Hi @gopal-vunet

As session's "proper behavior" hasn't been officially defined yet, I think @bidetofevil has been working on it so maybe he can provide more details. Because of this, we only provide an implementation within the android-agent module (via OpenTelemetryRumInitializer.initialize), as this initializer function is our opinionated way of configuring OpenTelemetryRumBuilder.

If you want to configure your own OpenTelemetryRumBuilder, because our opinionated initializer configuration doesn't suit your needs, you're going to have to create your own SessionProvider implementation. Bear in mind that the SessionProvider interface is in a separate artifact, which you'll have to add to your project if you want to use it.

Aside from that, I just wanted to point out that, ideally users should get everything working as expected by using the initializer function, and only on very specific scenarios would they need to directly use OpenTelemetryRumBuilder instead. Since you're trying to use OpenTelemetryRumBuilder directly, it seems like the initializer function doesn't meet your needs. We're open to make the initializer function grow as needed, to accomodate to most use cases, so if you don't mind letting us know what's the use case you need to fulfill for which the initializer function isn't working? For example, some people have mentioned that the initializer function is not practical to use from Java sources, for example, is that your case?

[breedx-splk]

+1 to what @LikeTheSalad said. If you have a good reason for using the OpenTelemetryRumBuilder directly instead of using the agent initializer, please reply here and explain. It's really good feedback for us to consider as we move toward a first stable release. Thanks!

[gopal-vunet]

Hi @LikeTheSalad , @breedx-splk

I use OpenTelemetryRumBuilder because I want to use addTracerProviderCustomizer. I use this to add custom attributes to the spans, the code for this will be like

 class GlobalAttributesSpanProcessor : SpanProcessor{

        override fun onStart(parentContext: Context, span: ReadWriteSpan) {
            MyApplication.globalAttribute.forEach { (key, value) ->
                span.setAttribute(key, value)
            }
        }

        override fun isStartRequired(): Boolean {
            return true
        }

        override fun onEnd(span: ReadableSpan) {}

        override fun isEndRequired(): Boolean {
            return false
        }

    }

    fun init(){
        OpenTelemetryRum.builder(this, config)
            .setSessionProvider(sessionProvider)
            .addSpanExporterCustomizer {
                OtlpHttpSpanExporter.builder()
                    .setSslContext(sslContext, trustAllCerts)
                    .setEndpoint(spansIngestUrl)
                    .build()
            }.addTracerProviderCustomizer { sdkTracerProviderBuilder, _ ->
                sdkTracerProviderBuilder.addSpanProcessor(GlobalAttributesSpanProcessor())
            }
    }

[mboudraa]

I'm in the same scenario and I use the builder to add custom Span Processors

addTracerProviderCustomizer { tracerProvider, _ ->
            tracerProvider.apply {
                addResource(AppInfo.instance.createResource())
                addSpanProcessor(UserContextSpanProcessor(workspaceManager, appScope))
                addSpanProcessor(DatadogIntegrationSpanProcessor())
                addSpanProcessor(LoggingSpanProcessor())
            }
        }

[LikeTheSalad]

I use OpenTelemetryRumBuilder because I want to use addTracerProviderCustomizer. I use this to add custom attributes to the spans

Hi @gopal-vunet. For global attributes, the agent's initializer DSL api provides a way to add those via the globalAttributes method, which can receive a function/supplier that will be called on every new Span and Log creation to add dynamic attributes.

Would that config option enable your use case while still using the OpenTelemetryRumInitializer.initialize function? I'm asking because we want to make the OpenTelemetryRumInitializer.initialize function as flexible as possible, but also focused on what's needed only, which makes the maintenance efforts more manageable.

---

@mboudraa - regarding the 3 custom processors that you're adding for your use case, I'm curious if they only add attributes (like the use case mentioned above) or if they do more than that? Knowing this will help a lot to know what we can do to enhance the initializer/DSL function to easily address more use cases.

[gopal-vunet]

Hi @LikeTheSalad , the current globalAttributes option via DSL accepts value only during the initialization. It doesn't fetch those values whenever the processor is executing. Incase if I want to add userId in the globalAttributes, the userId variable will be null during initialization, but after login, the variable's value will be updated, but the processor's won't fetch the updated value.

[breedx-splk]

@gopal-vunet I think we addressed this in #1593 back in February. Can you please verify if that works for your use case?