Production low traffic
What a runtime-low-traffic finding of fallow health means, why it matters and how to fix it.
What it reports
Function was invoked below the low-traffic threshold.
Runtime coverage explains how fallow finds it.
Why it matters
Production almost never runs the function, but the team still maintains and tests it. Each change to it carries risk for a path that few requests need.
Example
legacyLogin ran 3 times in a capture of 2 million calls, below the --low-traffic-threshold fraction.
Fix
Find the remaining callers, move them to the current path, then remove the function. Keep it when the rare callers matter.
Facts
| Fact | Value |
|---|---|
| Issue type | runtime-low-traffic |
| Rule id in SARIF output | fallow/runtime-low-traffic |
| Command | fallow health |
Fixable with fallow fix | No |
Note. Requires --runtime-coverage input (V8 directory, V8 JSON, or Istanbul map).