tc-diagnostics-portal
Support-facing diagnostics portal: an Angular 20 SPA plus a .NET 10 API boundary that gives support staff one place to investigate EventStore events, exceptions, provider transaction (PTR) logs and booking errors across environments.
Health score
0 to 100 across seven weighted factors; nothing is hidden. Green is 75 and above, amber 50 to 74, red below 50. How scoring works.
Facts
| Languages | csharp, typescript |
| Frameworks | ASP.NET Core 10, Angular 20 |
| Runtimes | .NET 10, nodejs |
| Tests / CI | good / CI in place |
| Last commit | 2026-05-27 |
| Owner | Owner unknown (mapping to be curated) |
| Domain | Platform services (system generated; curate in repo-owners.json to override) |
| Product area | Shared platform |
| Hosted | On-prem Deployed to our own machines
|
| Releases | 2 release pipeline(s): \tools\tc-diagnostics-portal; \tools\tc-diagnostics-portal-api |
| Integration | rest, jwt |
| Source | Open in Azure DevOps |
Risk flags
No risk flags recorded.
Each flag links to its glossary definition.
Dependencies in context
Entanglement
loose No binding mechanisms apply: this system needs no untangling work.
Depends on / used by
Migration playbooks
Generated from this repo's assessment data: what is feasible, what blocks it, and the steps in order. Ratings: green means actionable now, amber means sequence other work first, red means blocked, grey means not applicable.
ZDD adoption
No excuseNothing technical is holding this repo on the three-week release. It either already deploys without downtime (AWS) or is a modern, well-tested service the automated stealth path can carry today. Modern runtime, good tests, no hosted legacy transport: the automated stealth path can carry it today.
- 31 system(s) depend on this repo; during a rolling deploy they will talk to old and new versions at once, so responses must stay compatible
- Adopt the four-stage discipline from the ZDD engineering standard: pre-deployment compatibility, deployment, feature activation behind a flag, post-release cleanup.
- Make every change dual-version safe: backwards-compatible APIs (new major version for breaking wire changes), expand and contract for any schema change, and consumers tolerant of unknown fields.
- Externalise any remaining session state so users can move between nodes mid-session without disruption.
- Wrap behaviour changes in feature flags so code deploys dark and release becomes a business decision, not a deployment event.
- Route deployments through the Workflow Engine's automated drain, deploy, health-check, return cycle (the path proven by the first automated production run in mid-2026).
- Verify with area-scoped regression rather than the whole-platform cycle, and watch error rates after rollout with automated rollback on alert.
SQL Server exit
Not applicableNo SQL Server dependency is recorded for this repo. Nothing to migrate.
Containerisation
Ready to containeriseModern runtime, no hosted legacy transport: this service can follow the estate's proven container path (Dockerfile, shared pipeline template, ECS via Terraform).
- Add a Dockerfile and make the app read all configuration from environment variables and the secrets manager, never from machine-local files.
- Log to stdout and expose a health check endpoint so ECS can supervise it.
- Adopt the shared ci.yml pipeline template with the container parameters (awsRegion, containerAfterBuild, ecsTerraformRepo), which is exactly how the estate's existing AWS services deploy.
- Define the service in the Terraform repo, deploy to a non-production environment, then shift traffic and disarm the deployment-group release pipeline.
Recommended actions
No specific actions for this repo. It either needs only normal maintenance, or its work is covered by an estate-level action. See the full programme.
Assessment notes
tc-diagnostics-portal
Purpose
Consolidates operational investigation workflows behind one UI and one API. The SPA never calls diagnostic systems directly: the API validates Entra tokens and per-user assignment, resolves the downstream target through ConnectionBroker (EventStore, Exceptions, ProviderTransactionLogging, Provider, Quote, DynamicMargin), propagates correlation headers and returns normalised contracts. Shared api/search endpoints cover people, teams, destinations, places, providers and quote-to-folder lookups.
Tech stack
API: C# on .NET 10 (single DiagnosticsPortal.Api project) with JWT bearer validation against Microsoft Entra, TC.ConnectionBroker (Api + Wcf), TC.Cognito.Auth.Client and TC.UserAccount.ServiceClient. UI: Angular 20 with MSAL (@azure/msal-angular), Bootstrap 5, Karma/Jasmine specs. Both ship as Docker images (docker-compose for local dev) and are hosted on the dockerdev/docker.travelcounsellors.com platform per the allowed-origins list.
Deployment
Included as prod_application with 2 releases. Path-filtered YAML pipelines azure-pipelines-backend.yml and azure-pipelines-frontend.yml on the shared templates repo; included.json lists four build pipelines (diagnostics-portal and older support-portal backend/frontend pairs) and release pipelines \tools\tc-diagnostics-portal and \tools\tc-diagnostics-portal-api. Environment-aware config for QA, liveproviderqa, staging, training and live.
Dependencies
Internal: TC.ConnectionBroker.* (tc-connectionbroker) for downstream target resolution, the Exceptions diagnostic API (tc-exceptions) as a queried downstream, TC.UserAccount.ServiceClient (backoffice-useraccount-service) for people lookups; TC.Cognito.Auth.Client maps to no included repo. Other brokered targets (EventStore, PTR, Provider, Quote, DynamicMargin) reach further estate services by config. External: Microsoft Entra ID for SSO.
Data stores
None of its own — it is a read-only aggregation layer over other systems' diagnostic data.
Integration points
REST throughout (SPA to API, API to brokered downstream APIs) with Entra JWT authentication end to end.
Code health
Well tested for its size: API integration/unit tests (authorization handler, executors, contract tests via a test factory) and Angular Karma specs. Unusually good documentation — a solution wiki plus per-module query contracts and ops runbooks. Active (last commit 2026-05-27). The npm lint script is stubbed out (echo lint skipped).
Modernisation risks
Low — .NET 10, Angular 20, Docker-packaged, documented and tested; this is a model repo for the estate. Residual notes: the older tc-support-portal-* build pipelines suggest a predecessor app whose pipelines may need retiring, and access control depends entirely on correct Entra assignment configuration since the portal can reach sensitive diagnostic data across environments.