> For the complete documentation index, see [llms.txt](https://docs.certinext.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.certinext.io/documentation/monitoring-alerts-and-reporting/dashboards-and-kpis.md). # Dashboards and KPIs Dashboards and KPIs in CERTInext provide a real-time, visual representation of certificate health, risk posture, and operational effectiveness across the organization. They allow administrators, security teams, and management to quickly understand the current state of certificates and identify areas requiring attention. Dashboards consolidate data from certificate inventory, discovery scans, expiry monitoring, policy evaluation, and CT log monitoring, presenting it in an actionable and easy-to-interpret format. #### What Dashboards Show in CERTInext CERTInext dashboards display key metrics that reflect the overall certificate posture, including: * **Total Certificates Under Management**\ Count of all certificates issued, discovered, or monitored across environments. * **Expiry Status Indicators**\ Certificates that are expiring soon, already expired, or renewed recently. * **Policy Compliance Metrics**\ Number of certificates that are compliant versus those violating defined policies. * **Discovery Coverage**\ Visibility into certificates discovered via Bots and external sources such as CT logs. * **CA Distribution**\ Breakdown of certificates by issuing Certificate Authority (public or private). These metrics are continuously updated as certificates move through their lifecycle. #### Key Performance Indicators (KPIs) KPIs in CERTInext are designed to measure risk, readiness, and operational efficiency. Common KPIs include: * Percentage of certificates expiring within defined thresholds * Count of high-severity policy violations * Reduction in expired certificates over time * Discovery success rate across environments * Renewal completion rates before expiry KPIs help teams track trends rather than isolated events, enabling data-driven decision-making. #### Identifying Issues Using Dashboards Dashboards act as an early warning system by highlighting abnormal patterns or spikes, such as: * Sudden increase in expiring certificates * Growth in non-compliant or vulnerable certificates * Gaps in discovery coverage * Increased dependency on specific CAs Users can drill down from high-level KPIs to certificate-level details, allowing quick identification of affected certificates, owners, and deployment locations. #### Acting on Dashboard Insights Dashboards are tightly integrated with certificate inventory and lifecycle actions. From dashboard views, users can: * Navigate directly to affected certificates * Initiate renewal or replacement workflows * Review policy violation details * Correlate dashboard data with alerts and notifications This integration ensures that dashboards are not passive reports but active operational tools. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.certinext.io/documentation/monitoring-alerts-and-reporting/dashboards-and-kpis.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.