Analytics Dashboard Overview

On the Analytics page, you might find a collection of charts, graphs, and statistics such as:

IaC Coverage Over Time

A line graph showing the trend of IaC coverage (percent of assets codified) week by week or month by month. This is a great KPI to measure the success of your IaC adoption initiatives. For example, you can see a line climbing from 50% to 80% over six months after onboarding Firefly, demonstrating progress.

Drift Incidents Over Time

A graph or counter of how many drift events have been detected and resolved in a given period. You may see a bar chart per month: e.g., 10 drift incidents in January, 6 in February, 2 in March, indicating improvement. Or perhaps an uptick might signal need for more training or stricter guardrails.

Policy Compliance Rate

Perhaps a percentage of resources that are fully compliant with all policies. If you have 100 policies, maybe not all apply to every resource. This metric could be represented as "X% of resources have 0 policy violations." The higher, the better. Alternatively, a breakdown like "Critical Violations: 0 this week (100% compliance on critical checks). High Violations: 5 (98% compliance)."

Onboarding/Adoption Metrics

Analytics might show how many cloud accounts are integrated vs how many exist (to ensure coverage), how many users are actively using Firefly (number of user logins or API calls by users, etc.), and how many pull requests or codify actions have been done via Firefly. This tells you if teams are actually engaging with the tool or not. For instance, "20 self-service changes executed via Firefly this quarter" indicates developer adoption.

Top Offenders/Top Savers

Analytics can highlight, say, Top 5 Policies Violated (which policies are most frequently tripped – useful to identify where documentation or training is needed), or Top 5 Projects by Unmanaged Assets (to see which teams need help codifying). Conversely, it might highlight Top 5 Teams by IaC Adoption (a little friendly competition metric).

Savings and Cost Metrics

If Firefly is used diligently for cost optimization, you could input data on cost savings from actions taken and have a running total. For example, each time an orphan volume is deleted, log an estimated monthly saving. Analytics can then show "Estimated Cloud Cost Saved: $7,200/year" from all cleanup actions. While Firefly might not automatically calculate all savings, the platform team can maintain this or integrate with cost tools to pull actual spend data and correlate it with Firefly's actions.

Export and Reporting

All charts usually have an export option (CSV, PDF). This is useful for reporting to management. You can, for example, export a PDF report of "Quarterly Cloud Governance Report" containing those IaC coverage and compliance graphs. Some GitBook formatting might not apply for actual output, but in GitBook documentation, you can note that such exports are available.