Dashboard infomation not corrected after update from 4.10.0 to 4.12.4

[carloreggiani]

Current Behavior

Hi

We updated from 4.10.0 to 4.12.4, and now the numbers for vulnerabilities (critical, high, medium) and Policy Violations shown in the dashboard are incorrect.

We tried to re-import the SBOM, but nothing changed.

There is any activity to manage to refresh the counters?

Steps to Reproduce

1. update version (docker) from 4.10.0 to 4.12.4

Expected Behavior

Counters (total numbers) in the dashboard for Policy Violation and vulnerability criticality are correct after migration.

Dependency-Track Version

4.12.4

Dependency-Track Distribution

Container Image

Database Server

PostgreSQL

Database Server Version

No response

Browser

Microsoft Edge

Checklist

• I have read and understand the contributing guidelines
• I have checked the existing issues for whether this defect was already reported

[nscuro]

Can you elaborate on how "incorrect" manifests itself? Can you give an example as to how metrics are skewed?

Also, have you checked the logs for any errors? It could be that metrics updates are failing.

[carloreggiani]

Sure, for example: - Project with one component with a critical vulnerability (and 2 High) [image: immagine.png] - Total counters for vulnerability correctly showed [image: immagine.png] - Policy set to Fail in case of critical vuln [image: immagine.png] *- Counter Policy Violations don't show correctly the Policy Failed* [image: immagine.png] I asked to sysadmin to check the logs

…

On Wed, Feb 19, 2025 at 10:39 AM Niklas ***@***.***> wrote: Can you elaborate on how "incorrect" manifests itself? Can you give an example as to how metrics are skewed? Also, have you checked the logs for any errors? It could be that metrics updates are failing. — Reply to this email directly, view it on GitHub <#1170>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHXVHJ3KKALNVIJRCPX77L2QRGNFAVCNFSM6AAAAABXNTUBNKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRYGA3DONZZGI> . You are receiving this because you authored the thread.Message ID: ***@***.***> [image: nscuro]*nscuro* left a comment (DependencyTrack/frontend#1170) <#1170> Can you elaborate on how "incorrect" manifests itself? Can you give an example as to how metrics are skewed? Also, have you checked the logs for any errors? It could be that metrics updates are failing. — Reply to this email directly, view it on GitHub <#1170>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHXVHJ3KKALNVIJRCPX77L2QRGNFAVCNFSM6AAAAABXNTUBNKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRYGA3DONZZGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Carlo Reggiani about.me/reggianicarlo [image: Carlo Reggiani on about.me] <http://about.me/reggianicarlo>

[nscuro]

It seems like you answered via email, and the attached screenshots did not make it to GitHub.

[carloreggiani]

Sorry, I'm referring to the numbers in project detail: numbers in the colored circle for vulnerability counters and numbers (colored) for Policy Violations counters.

[msymons]

This seems to be the problem, tested in v4.12.4 and in v4.13.0-SNAPSHOT

As can be seen, there are 39 policy violations in total.... but no count displayed for the type (info/warn/fail):