Skip to main content

Automate Insights

The Insights dashboard provides analytics on your Automate activity — savings over time, execution success rates, and resource coverage. Use it to understand the impact of your automation and identify opportunities for improvement.

View Insights

[SCREENSHOT: automate-insights.png -- Automate insights dashboard showing savings chart, success rate, and resource coverage]


Key metrics

Savings over time

A chart showing total savings broken down by period. Savings are calculated from completed Executions where resources were successfully stopped or scaled down.

GranularityAvailable ranges
DailyLast 7 days, last 30 days
WeeklyLast 4 weeks, last 12 weeks
MonthlyLast 3 months, last 6 months, last 12 months

Execution success rate

The percentage of Executions that completed without errors, shown as a trend line alongside total Execution count. A high success rate indicates healthy Targets and IAM configurations.

StatusMeaning
SucceededAll resources in the Target transitioned to the desired state
Partially failedSome resources transitioned; others encountered errors
FailedNo resources transitioned — typically an IAM or connectivity issue
tip

If your success rate drops below 90%, review the Execution Lifecycle page for troubleshooting guidance, and check that your IAM policies are up to date in IAM Role Permissions.

Resource coverage

Shows how many of your AWS resources are included in at least one Target, compared to the total discovered resources across your Connections. High coverage means more of your environment is being managed by frugally.app.


Filters and controls

FilterOptions
Date rangePreset ranges or custom date picker
ConnectionFilter by one or more AWS Connections
ServiceFilter by AWS service type
TargetFilter by specific Targets

Using Insights to improve savings

  1. Low resource coverage? Run the Onboarding Wizard to discover resources not yet included in Targets
  2. Low success rate? Check for IAM permission errors or resources that have been terminated in AWS
  3. Savings plateau? Review your Schedules — extending stop durations (e.g. including weekends) or adding more Targets can increase savings
  4. Projected vs actual gap? See the Projected vs Actual Savings chart for a detailed comparison