-
Notifications
You must be signed in to change notification settings - Fork 38
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
Generate configuration event at startup #277
Comments
Apart from avoiding a circular dependency, do you think there are other reasons where transforming the config object into a map could be beneficial? I'm asking because I think we could work around the circular dependency issue, so we might be able to avoid doing this work altogether. |
I think this issue is no longer needed. |
Yeah, certainly as written now the "configuration" isn't a singular thing that we can absorb and digest....and instead it is spread around with each individual instrumentation. The original goal of this was to provide additional details about how the agent (and otel) are configured. Imagine looking at a session in a RUM tool and being able to ask easily:
This stuff is metadata, but super useful if/when you start questioning how the agent is behaving. Very very useful in troubleshooting. I guess I'll close for now until there's a more specific ask. |
Relates to #168.
As part of #276, the configuration was decoupled from the initialization events. This TODO says that we should figure out how to pass the config as a map: https://github.com/open-telemetry/opentelemetry-android/pull/276/files#diff-6f33477d17cf7e6844b9afbc97741d317291d28b233fb28f810359611325274fR376
It's really helpful to have an event at startup that provides the o11y practitioner with details about the RUM/agent configuration.
The text was updated successfully, but these errors were encountered: