From the forum (https://community.coffeylabs.org/t/232, post 27): the dashboard said "12 reports with warnings" while the DMARC reports page showed fewer problems, which looked like the two disagreed.
The attention item (src/features/dashboard/attention.ts) adds DMARC and TLS warnings into one count across every domain, over the dashboard's saved period; the DMARC page is per domain. The split is only in the detail line.
Proposal: separate items, "N DMARC reports with failures" and "N TLS reports with failures", each linking to its own page. Related: inbuxa/inbuxa-server#402 (a TLS report can count more than once).
From the forum (https://community.coffeylabs.org/t/232, post 27): the dashboard said "12 reports with warnings" while the DMARC reports page showed fewer problems, which looked like the two disagreed.
The attention item (`src/features/dashboard/attention.ts`) adds DMARC and TLS warnings into one count across every domain, over the dashboard's saved period; the DMARC page is per domain. The split is only in the detail line.
Proposal: separate items, "N DMARC reports with failures" and "N TLS reports with failures", each linking to its own page. Related: inbuxa/inbuxa-server#402 (a TLS report can count more than once).
The dashboard now shows DMARC and TLS report warnings as two separate items, each linking to its own reports page, and each says its count covers all your domains over the dashboard's period. That's why it can be higher than what the DMARC reports page shows for one domain. A TLS report being counted more than once is a separate server issue, inbuxa-server#402.
It ships in the next console release candidate.
Fixed in #242, thanks to the report in https://community.coffeylabs.org/t/232 (post 27).
The dashboard now shows DMARC and TLS report warnings as two separate items, each linking to its own reports page, and each says its count covers all your domains over the dashboard's period. That's why it can be higher than what the DMARC reports page shows for one domain. A TLS report being counted more than once is a separate server issue, inbuxa-server#402.
It ships in the next console release candidate.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
From the forum (https://community.coffeylabs.org/t/232, post 27): the dashboard said "12 reports with warnings" while the DMARC reports page showed fewer problems, which looked like the two disagreed.
The attention item (
src/features/dashboard/attention.ts) adds DMARC and TLS warnings into one count across every domain, over the dashboard's saved period; the DMARC page is per domain. The split is only in the detail line.Proposal: separate items, "N DMARC reports with failures" and "N TLS reports with failures", each linking to its own page. Related: inbuxa/inbuxa-server#402 (a TLS report can count more than once).
Fixed in #242, thanks to the report in https://community.coffeylabs.org/t/232 (post 27).
The dashboard now shows DMARC and TLS report warnings as two separate items, each linking to its own reports page, and each says its count covers all your domains over the dashboard's period. That's why it can be higher than what the DMARC reports page shows for one domain. A TLS report being counted more than once is a separate server issue, inbuxa-server#402.
It ships in the next console release candidate.