Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Add skills - ngx-ui-watchtower setup and integration

Abierto
  • ¿Algo no está bien?
#42 0 comentarios 0 reacciones 1 asignado Ver en GitHub

@fateeand ya está trabajando en esto.

Desde el 8/10/2026.

  • #43 de @fateeand — abierto

Evaluación

Este issue todavía no se ha evaluado.

Descripción

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
Lenguaje dominante
Python
Estrellas
1
Forks
0
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de AbsaOSS/agentic-toolkit

Todos los issues de AbsaOSS/agentic-toolkit

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.