Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Add skills - ngx-ui-watchtower setup and integration

Offen
  • Stimmt etwas nicht?
#42 0 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

@fateeand arbeitet bereits daran.

Seit 08.10.2026.

  • #43 von @fateeand — offen

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

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
Vorherrschende Sprache
Python
Sterne
1
Forks
0
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus AbsaOSS/agentic-toolkit

Alle Issues in AbsaOSS/agentic-toolkit

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.