[Maintenance]: Time Token Tracker 3.0.0 — remove the HTTP Data Collector fallback once Microsoft announces its shutdown #192

Affected area: filters/time_token_tracker.py, docs/setup-azure-log-analytics.md, tests/e2e
Related: #188, #191 (Time Token Tracker 2.7.0: Logs Ingestion API with the Data Collector API as fallback)

Summary

Since 2.7.0 (#191), the Time Token Tracker sends records through the Azure Monitor Logs Ingestion API. It keeps the deprecated HTTP Data Collector API as a fallback, with modes auto, logs_ingestion, data_collector and both. The fallback logs a one-time deprecation warning.

Microsoft ended support for the Data Collector API on September 14, 2026. Ingestion still works for clients using TLS 1.2 or later, and no shutdown date has been announced as of 2026-10-09 (migration guide, Data Collector API). Removing the fallback now would break working setups without a technical need, and it would also remove the both mode used for side-by-side migration.

Plan

When Microsoft announces a date after which Data Collector ingestion stops, release Time Token Tracker 3.0.0 with the Logs Ingestion API only:

• remove the Data Collector sender (SharedKey signature, *.ods.opinsights.azure.com), the modes data_collector, both and auto, and the deprecation warning;
• remove the valves LOG_ANALYTICS_WORKSPACE_ID, LOG_ANALYTICS_SHARED_KEY and LOG_ANALYTICS_INGESTION_API. This is a major version, so add a migration note;
• for installations that still have only the old valves, log one clear message per process with the migration doc link and a permalink to the last 2.x version;
• port every API-independent e2e check of the la group to the Logs Ingestion path, and remove only the checks that are specific to the Data Collector API;
• update the docs in three places, with a BREAKING note in the changelog.

Trigger

Watch the two Microsoft pages above and the Azure Updates feed for an ingestion shutdown date.