You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@absaoss-cps/ngx-ui-watchtower is a telemetry library for Angular apps: scenarios (did a user journey succeed, and how long did it take), BI events, and logs, with an AWS CloudWatch RUM sink.
Integrating it well takes more than installing it — the destination must be wired per app role, names must be declared as a typed vocabulary, journeys must settle with the right status, and an app that already sends RUM events must keep wire parity. It would be beneficial to introduce an agentic skill that guides an agent through integrating the library into any Angular application.
Proposed Scope
Detect the app's shape: Angular version, bootstrap style (standalone / NgModule), SSR, package manager, test runner, existing RUM code, and its role (standalone app, micro-frontend shell, or fragment)
Install the package and wire providers with exactly one destination for that role (RUM sink + credentials provider, broadcast host for shells, forwarding sink for fragments, or an explicit no-op)
Wire logging only when the app has a log backend
Create the typed name vocabulary (telemetry.schema.ts)
Migrate an existing hand-written RUM integration without changing what reaches CloudWatch
Propose scenarios and BI events from the app's code, wait for the user's confirmation, then implement them (always including route navigation)
Fix specs that need telemetry providers, add tests for each instrumented outcome, and validate (build, tests, type-check, live debug output)
Out of Scope
CloudWatch dashboards, RUM extended metrics and alarms
Activity