Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Add skills - ngx-ui-watchtower setup and integration

Ouverte
  • Quelque chose ne va pas ?
#42 0 commentaires 0 réactions 1 personne assignée Voir sur GitHub

@fateeand y travaille déjà.

Depuis le 8/10/2026.

  • #43 par @fateeand — ouverte

Évaluation

Cette issue n'a pas encore été évaluée.

Description

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
Langage dominant
Python
Étoiles
1
Forks
0
Aucune PR mergée en 30 j

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de AbsaOSS/agentic-toolkit

Toutes les issues de AbsaOSS/agentic-toolkit

Issues similaires

Plus d'issues Python

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.