angular-telemetry

Standard IDs

ID	Severity	What it checks
TEL-001	P1	No Application Insights JS SDK (or equivalent) wired into the app
TEL-002	P2	User-interaction events tracked with ad-hoc/inconsistent naming instead of a shared convention
TEL-003	P1	No correlation between a frontend action and the backend request's trace ID
TEL-004	P0	PII captured in telemetry event properties

---

Check A — No Application Insights JS SDK wired (TEL-001)

Detection

Check app.config.ts/main.ts for @microsoft/applicationinsights-web (or an equivalent RUM/analytics SDK) initialization. Without it, frontend errors, page-load performance, and user-interaction patterns are invisible — dotnet-observability covers the backend, but a slow or broken frontend experience produces no telemetry at all on its own.

BAD — no frontend telemetry SDK at all

export const appConfig: ApplicationConfig = {
  providers: [provideHttpClient(), provideRouter(routes)],
  // No telemetry SDK — a JS error or a slow page load is invisible unless a user reports it.
};

GOOD — Application Insights initialized, wired to the global ErrorHandler

const appInsights = new ApplicationInsights({
  config: { connectionString: environment.appInsightsConnectionString, enableAutoRouteTracking: true },
});
appInsights.loadAppInsights();

@Injectable()
export class TelemetryService {
  trackEvent(name: string, properties?: Record<string, string>) {
    appInsights.trackEvent({ name }, properties);
  }
  trackException(error: unknown) {
    appInsights.trackException({ exception: error as Error });
  }
}

GlobalErrorHandler (from angular-error-handling AEH-001) calls telemetry.trackException(error) so uncaught exceptions are captured automatically.

---

Check B — Ad-hoc event naming instead of a shared convention (TEL-002)

Detection

Grep trackEvent(...) call sites for inconsistent naming ("Order Approved", "order_approve_click", "OrderApprove" all appearing across the codebase) instead of one documented convention (e.g., Feature.Action — Orders.Approved, Orders.ExportClicked). Inconsistent naming makes it impossible to build a reliable dashboard/funnel query across events from different features.