Releases: bugsnag/bugsnag-android-performance
Releases · bugsnag/bugsnag-android-performance
v2.0.0
Changes
- Internal modularisation: moved the internal implementations of
bugsnag-android-performance
to the bugsnag-android-performance-impl
module, and much of the API into the bugsnag-android-performance-api
module. No changes are required to your dependencies and no code-changes are required.
#406
- New
bugsnag-plugin-android-performance-named-spans
plugin to track open spans by name, allowing you to easily retrieve them using BugsnagPerformance.getSpanControls(NamedSpanQuery("spanName"))
#411
Bug fixes
- Stopped attempting to send CPU metrics when none could be collected for a span
#404
v1.16.0
Changes
- Added
Plugin
as a way to extend the functionality of the BugsnagPerformance library
#387
- Introduced
AppStartSpanControl
and SpanType.AppStart
to allow custom categorisation of app starts
#394
v1.15.0
Changes
- Set default endpoints based on API key
#390
- Introduced
OnSpanStartCallback
as a way to listen-for and modify all spans before they are used
#383
v1.14.0
Changes
- Introduced
RemoteSpanContext
to allow cross-layer parenting of spans, along with easy encoding of traceparent
headers
#378
Bug fixes
- Corrected the naming of the aggregate CPU metrics attributes
#380
v1.13.0
Changes
- Optionally capture and report CPU and Memory use on selected spans (opt-in using
PerformanceConfiguration.enabledMetrics
)
#366
v1.12.0
Changes
- Added LoadingIndicator composable as a way to easily extend ViewLoad end times to interactivity
#336
- Added LoadingIndicatorView as a way for xml layouts to easily extend ViewLoad end times to interactivity
#352
v1.11.0
Changes
- Added mechanism for delivering external spans with natively-captured metrics (for initial use with React Native rendering metrics)
#327
v1.10.1
Bug fixes
- Move remaining I/O to the worker thread in
BugsnagPerformance.start
- avoiding StrictMode violations
#310
v1.10.0
Bug fixes
- Untagged socket violation when StrictMode is enabled #297
#306
- Fixed issue where background apps didn't consistently flush the current batch of spans
#305
Enhancements
- Formally introduced the
bugsnag-android-performance-compose
module and MeasuredComposable to report the performance of Composables
#299
v1.9.1
Bug fixes
- Fixed Warm AppStarts being over reported due to app-backgrounding not being fully reported internally
#299
- Custom spans are reported with a "bugsnag.span.category" to match behaviour in our other SDKs
#300