How-to guide
Advice re-reporting
Elevarq holds each finding back from being re-reported for a per-severity suppression window that matches your organization's issue-handling cadence — while a worsening metric or a material change to the database resurfaces the advice immediately. Set the windows per severity, or leave them at the defaults.
Elevarq does not re-file the same advice on every analysis run. Once a finding has been raised, it is held back from being re-reported for a per-severity suppression window that matches your organization's issue-handling cadence — so a two-week patch cycle is not buried under the same recommendation fifteen times. The finding stays visible on the Findings page throughout; the window governs only whether each new run re-raises it as fresh advice.
Default windows
The windows are per severity and mirror the analyzer defaults:
| Severity | Default window | Meaning |
|---|---|---|
| Critical | none | Always re-reported on every run; never silenced |
| High | 7 days | Not re-raised for 7 days after it was last reported |
| Medium | 28 days | Not re-raised for 28 days |
| Low | 56 days | Not re-raised for 56 days |
Critical advice is never suppressed — it is re-reported on every run, whatever the other windows are set to.
A real change always resurfaces advice
A window silences only the unchanged. Advice is re-raised immediately, before its window elapses, when either:
- the evidence worsens — the underlying metric degrades further, or
- there is a material change to the database — schema, configuration, workload, or statistics — that alters the finding.
So a window never hides a situation that is actively getting worse; it only quiets steady-state repetition of advice you have already seen.
Change the re-reporting windows
An administrator sets the windows on Settings → Advice
re-reporting (/settings, admin-only; every change is recorded in the
audit log). Each severity takes a whole number of days from 1 to 365;
leave a field empty to fall back to the default above. There is
deliberately no critical field — critical always reports.
Standalone analyzer
When you run the analyzer on its own — without Workbench managing the setting — the same windows are set through environment variables on the analyzer:
ELEVARQ_SUPPRESSION_INTERVAL_CRITICALELEVARQ_SUPPRESSION_INTERVAL_HIGHELEVARQ_SUPPRESSION_INTERVAL_MEDIUMELEVARQ_SUPPRESSION_INTERVAL_LOW
Each value accepts a duration — 7d, 4w, or 336h are all valid.
Unset or empty keeps that severity's default; an unparsable value is
ignored (the default stands, and suppression is never disabled by a bad
value). Unlike the Workbench setting, the critical window can be
adjusted here, for operators who knowingly accept the reduced safety
posture.
Related
- Findings and reports — reviewing and triaging the advice these windows govern.
- Administration — where an administrator changes the windows.