Skip to content

Classify EmployeeHub as internal telemetry - #222

Closed
amilandi wants to merge 2 commits into
mainfrom
amilandin/adk-tenant-name-cache
Closed

amilandi wants to merge 2 commits into
mainfrom
amilandin/adk-tenant-name-cache

Conversation

@amilandi

@amilandi amilandi commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Summary

  • classify the EmployeeHub dogfood tenant (935884d7-bdee-469b-a461-fcc530a3ac83) as internal telemetry
  • preserve the environment-variable allowlist for additional internal tenants
  • add regression coverage for EmployeeHub classification

Dashboard rollout

The dev and prod FlightCheck (External) and ADK Platform (External) tiles now also exclude this tenant ID explicitly, so retained historical EmployeeHub events are removed immediately rather than waiting for newly classified events.

No synthetic events were emitted to prod.

Testing

  • python -m pytest tests/test_adk_telemetry.py tests/flightcheck/test_telemetry.py -q

Avery Milandin added 2 commits August 4, 2026 14:38
Treat the EmployeeHub dogfood tenant as internal for future ADK and FlightCheck events, with regression coverage.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 70ddf006-7f8d-48e7-9afa-3fbae73b3864
@amilandi

Copy link
Copy Markdown
Contributor Author

Abandoning — no longer pursuing this hygiene change under the current iteration's telemetry plan.

@amilandi amilandi closed this Sep 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant