Infraova
Docs/Prioritization

Monitoring

Prioritization

Not every problem deserves the same attention — how Infraova ranks issues by severity, health scores, and portfolio impact.

Why prioritization matters

An agency managing fifty client domains may have dozens of issues open at any time. Without prioritization, every issue looks equally urgent — which means nothing feels urgent. Prioritization is how Infraova turns a list of detected problems into a ranked queue that tells you where to focus first, what can wait, and what is threatening client operations right now.

Severity levels

Infraova assigns every issue one of two severity levels. Critical issues are problems that are actively affecting or imminently threatening deliverability, domain function, or client operations. A missing DMARC policy on a domain with p=reject, an expired SSL certificate, or a blacklist appearance are critical issues. Warning issues are problems that represent misconfiguration or risk but are not causing immediate impact — an SPF record approaching the DNS lookup limit, a certificate with 25 days remaining, a DMARC policy still at p=none.

Health scores

Every domain in Infraova has a health score — a single number that reflects the current state of the domain's infrastructure. The score is derived from the open issues on the domain, weighted by severity. A domain with no issues scores at 100. Each open critical issue reduces the score significantly. Warning issues reduce it less. Health scores update in real time as issues are detected, resolved, or dismissed.

Portfolio health

Health scores roll up from domain to client and from client to portfolio. The portfolio health view shows the overall state of all domains you manage — sorted by health score so the most degraded clients and domains surface at the top. Portfolio health gives you the agency-level view: across everything you manage, where are the problems and how bad are they.

Impact assessment

Severity and health score tell you how bad a problem is. Impact assessment tells you who it affects. A critical issue on a domain sending 10,000 emails per day has more immediate business impact than the same issue on a domain sending 100 emails per month. Infraova surfaces sending volume and activity context alongside issues so you can make informed decisions about which critical issues to approve first.

Recommended attention

The Infraova dashboard surfaces issues in recommended attention order — critical issues first, sorted by client impact, with the domains in the worst health state at the top. This is the default view for operators who need to know where to focus without having to filter or sort manually.