Proactive Code Check analytics
Platform Owners use Proactive Code Check to track compliance against coding best practices and organizational standards. Owners can review detailed findings and audit the status of issues that were uncovered during the scan. Historical data is available up to six months.
About this task
- Identify recurring issues and trends in unresolved findings.
- View progress on resolving technical debt over time.
- Prioritize remediation efforts using a severity-based categorization of findings.
Before you begin
Role required: Impact_platform_owner, sn.mif_mif_read
Procedure
-
Navigate to .
The Proactive Code Check overview displays with data from the last 30 days.
-
Select View Dashboard to view additional information about the scans.
- Filter by instances or by time period.
- The Prevented findings charts display metrics related to findings that were resolved prior to moving an update set to a production completed status.
- The Unresolved findings section displays metrics related to findings that remained open after an update set was moved to a production completed status.
- Compare Trends in Resolved vs. Unresolved Findings.
-
Select View all findings to view all findings related to Proactive Code Check.
- View All Findings Across Instances.
- Filter and Group Findings by Severity, Type, or Check.
- Identify Checks Producing the Most Findings for Targeted Improvements.
- Analyze Findings Across Time Periods to Track Trends and Recurring Issues.
Table 1. Findings count and state across time periods Findings category State Count of Findings (Findings Resolved) Muted and Created on Today Count of Findings Unresolved Recurring or New and Updated on Today Count of Findings Resolved Resolved and Updated on Today Count of Findings New New and Updated on Today Count of Findings Muted Muted and Updated on Today