@@ -229,10 +229,16 @@ providers: [
229229 broadcast plumbing stay internal so they can change freely. Redaction is
230230 the exception: a custom sink needs ` uwtRedactMetadata ` ,
231231 ` uwtNormalizeError ` , ` uwtScrubString ` and ` uwtRedactConfigFor ` .
232+ - ** The RUM sink is the core's too.** Its logic — the lazy ` aws-rum-web `
233+ import, startup retries, credential refresh, the pre-init buffer, the
234+ settings check — lives in ` @absaoss-cps/ui-watchtower/rum ` . This package's
235+ ` /rum ` keeps ` UWT_RUM_CREDENTIALS_PROVIDER ` , ` provideUwtTelemetryRumSink() `
236+ and ` UwtRumTelemetrySink ` , an injectable subclass of the core's.
232237- ** The secondary entry keeps private copies of a few utilities.** ng-packagr
233238 fixes each entry point's ` rootDir ` to its own ` src ` , so
234239 ` @absaoss-cps/ngx-ui-watchtower/rum ` can't import the main entry's
235- internals by relative path and carries small copies of what it needs.
240+ internals by relative path and carries small copies of what it needs: its
241+ Angular helpers and the reporter.
236242- ** Test doubles live in the specs that use them** , declared inline, never in
237243 a shared file and never exported. The one browser gap needing a stub is
238244 ` BroadcastChannel ` , which jsdom doesn't implement.
@@ -1608,12 +1614,15 @@ convention, for an application that wants the pre-fallback behavior back.
16081614## 11. Error handling and performance
16091615
16101616- ** Telemetry never breaks the application.** Every public entry point is
1611- wrapped and never rethrows. The core prints nothing by itself: it hands a
1612- suppressed error, or data it had to drop, to the ` UwtReporter ` it is
1613- given. This package gives it one that writes to the console, prefixed
1617+ wrapped and never rethrows. The core hands a suppressed error ( ` 'error' ` ),
1618+ or data it had to drop ( ` 'warn' ` ) , to the ` UwtReporter ` it is given. This
1619+ package gives it one that writes to the console, prefixed
16141620 ` [ngx-ui-watchtower] ` , in development mode only, so bugs surface in
1615- development and production stays silent. Even a broken ` console.error `
1616- cannot turn a suppressed failure into a throw.
1621+ development and production stays silent. What cannot work as configured
1622+ (` 'config' ` ) — a second broadcast host, a host in a forwarding realm, RUM
1623+ settings of the wrong type — is printed in production too, as it always
1624+ was; without a reporter, the core prints it itself. Even a broken
1625+ ` console.error ` cannot turn a suppressed failure into a throw.
16171626- ** Fail-open.** A broker outage, expired credentials or an SDK throw all
16181627 leave the application behaving exactly as with healthy telemetry. A failed
16191628 broker request at startup is retried with backoff for five minutes. A
0 commit comments