Change 33581
recommend_limits.py: add ADX data source with configurable date range; externalize ADX settings to recommend_limits.cfg; remove MaxLockTime 90s cap
- fetch_records_from_adx() pulls per-command metrics from Azure Data
Explorer (PerforceEventType9/PerforceEventType2) as an alternative to a
local log file, filtered by --p4-port and/or --environment, with
--adx-start/--adx-end defaulting to the last N days. Automatically
bisects the time range and retries when ADX reports a result set too
large for one query.
- All ADX cluster/database/tuning values now come from an INI config
file (recommend_limits.cfg, p4-ignored - never checked in) instead of
being hardcoded in the script, since this is a public depot.
recommend_limits.cfg.example documents the format with placeholder
values.
- MaxLockTime is now computed the same percentile-driven way as
MaxResults/MaxScanRows/MaxMemory, instead of being capped at a fixed
90000ms.
- fetch_records_from_adx() pulls per-command metrics from Azure Data
Explorer (PerforceEventType9/PerforceEventType2) as an alternative to a
local log file, filtered by --p4-port and/or --environment, with
--adx-start/--adx-end defaulting to the last N days. Automatically
bisects the time range and retries when ADX reports a result set too
large for one query.
- All ADX cluster/database/tuning values now come from an INI config
file (recommend_limits.cfg, p4-ignored - never checked in) instead of
being hardcoded in the script, since this is a public depot.
recommend_limits.cfg.example documents the format with placeholder
values.
- MaxLockTime is now computed the same percentile-driven way as
MaxResults/MaxScanRows/MaxMemory, instead of being capped at a fixed
90000ms.