Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Add skills - ngx-ui-watchtower setup and integration

Aperta
  • Qualcosa non va?
#42 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@fateeand ci sta già lavorando.

Dal 8/10/2026.

  • #43 di @fateeand — aperta

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

Summary

@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.

Adopting it is two different jobs, so this proposes two skills:

  • ui-watchtower-setup — the infrastructure, done once per app.
  • ui-watchtower-integration — measuring the app's own journeys and interactions, repeated as the app grows, driven by what the team wants to learn.

Proposed Scope

ui-watchtower-setup
  • 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 exactly one destination for that role (RUM sink + credentials provider, broadcast host for shells, forwarding sink for fragments, or an explicit no-op); a log provider 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
  • Prove the pipeline with route-navigation tracking (route templates, not ids) and a test
  • Fix specs that need telemetry providers; validate (build, tests, type-check, live debug output); hand over to the integration skill
ui-watchtower-integration
  • Check that setup is done; otherwise point to ui-watchtower-setup
  • Ask the user first what the telemetry should answer: questions to answer, key journeys and what success means, interactions to count, known pain points, what must not be tracked, scope
  • Scan the code for candidates within that scope
  • Present a merged proposal marking each item as requested by the user or suggested, plus requests that had to change (e.g. no raw search text, no ids in names) with the alternative
  • Implement only what the user confirms, with the right settle status for each outcome, and test every outcome

Out of Scope

  • CloudWatch dashboards, RUM extended metrics and alarms
  • A backend correlation-header interceptor
  • The diagnostics popup (not yet released)
  • Non-Angular applications
Lingua principale
Python
Stelle
1
Fork
0
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di AbsaOSS/agentic-toolkit

Tutte le issue di AbsaOSS/agentic-toolkit

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.