Action Summary

1. Introduction to Action Summary Analytics

The Action Summary Page provides an overview of actions attempted for system rules, categorizing them as Pass, Fail, or Need Admin Action. It includes a detailed table of rule execution outcomes along with graphical trends (daily, weekly, and monthly) to track performance and identify recurring issues.

2. Key Information Available in the Action Summary Section

1. Action Summary Overview:

Total Actions Attempted for Rules: Displays the total count of executed actions and their distribution across the following categories:

• Pass (Successfully Executed Actions): Actions completed without issues, confirming that the system is functioning as intended. No further intervention is required.
• Fail (Actions That Failed to Execute): Actions that couldn’t be completed due to issues like user denial or system conflicts (e.g., Chrome running during cache clearing).
• Need Admin Action (Actions Requiring Administrative Intervention): Actions needing higher-level permissions or manual input, such as clearing system temp files or modifying security settings.

Detailed Execution Table: Lists all rules with details including:

• Total number of rules executed.
• Count of successful executions (Pass).
• Count of failed executions (Fail).

2. Trend Analysis:

• Daily Trend: A graphical representation of daily actions performed, highlighting fluctuations in activity.
• Weekly Trend: Aggregated data showing the weekly volume of attempted actions.
• Monthly Trend: A broader view of action trends over several months, providing long-term performance insights.

3. Action Result Breakdown:

Displays a visual representation of action execution for a specific date (e.g., Dec 4, 2024), categorized as:

• Pass
• Fail
• Need Admin Action

3. How to View Detailed Information About a Specific Rule’s Action History?

Navigating the Action Analytics Section:

1. Click on a specific rule or its Pass/Fail count in the table.
2. A detailed view of the rule’s action history will open, including:

• Rule Name
• Username
• Hostname
• Action Result
• Execution Time
• Start/End Dates

1. The data can be sorted and filtered for troubleshooting, performance evaluation, and compliance monitoring.
2. This feature offers granular visibility into individual rule execution patterns, helping administrators identify issues and improve system efficiency.

4. Why Might Self-Heal Rules Require User or Admin Action?

User Action Required:

• Some tasks, such as clearing browser cache or cookies, may require user permission to avoid disruptions.
• Example: If a user is actively working on a browser, they may need to confirm the action before execution.

Admin Action Required:

• Other tasks, such as updating system policies or clearing temp files, require administrative privileges.
• Example: System-wide settings modifications or access to restricted areas often need an admin account to execute.