Not switched on
Useful1 Signal3
Severity thresholds can now be set per feature area from server config, and none are set.
A severityBySite config key can hold per-area thresholds with one area wired up, resolving to null without a server value.
What's wrong with this entry?
Anonymous. No account, no email.
What
Severity thresholds can now be resolved per feature area, reading a severityBySite key from remote config that holds either the literal "on" or an object of thresholds, falling back to that area's own defaults. One area is wired up, keyed handoff. With no value from the server the result is a null threshold marked as coming from the default, so severity stays off unless remote config carries the key.
Details
- Two additional local conditions must also pass before the remote value is consulted.
- In the same function the older bundle-based severity source is compiled out: the variable its
iftests is assigned literalnullimmediately above, so that branch can never run. The per-model threshold map is the only remaining non-per-area route.
Evidence
severityBySite
Strings lifted out of the shipped bundle, so the claim above can be checked against them.