Summary

1. Overview of the Action Summary Page

The Action Summary Page provides insights into the execution of system rules, categorizing them based on success, failure, or administrative intervention needs.

Available Information:

1. Action Summary
   • Total Actions Attempted: Number of rule-based actions executed.
   • Pass (Successful Actions)
     • Reason: Actions completed without issues.
     • Example: Cache clearing completed successfully.
   • Fail (Unsuccessful Actions)
     • Reason: Execution failed due to user denial, system conflicts, or process restrictions.
     •  Example: Cache clearing failed because Chrome was running.
   • Need Admin Action (Requires Administrator Privileges)
     • Reason: Requires higher-level permissions for execution.
     • Example: Clearing system temp files or modifying group policies.
2. Detailed Table for Execution Analysis
   • Lists all rules with their execution status:
     • Total rule executions
     • Successful (Pass)
     • Failed (Fail)
     • Admin Action required
3. Trend Analysis
   • Daily Trend: Shows execution performance per day to track fluctuations.
   • Weekly Trend: Aggregated execution data to track weekly action volume.
   • Monthly Trend: Broad view of long-term execution trends over months.
4. Action Result Breakdown
   • Graphical representation of execution results for a specific date (e.g., Dec 4, 2024)
     • Pass
     • Fail
     • Need Admin Action

2. Viewing Detailed Information for a Rule’s Action History

The Action Analytics section allows users to explore a specific rule’s execution history for better monitoring and troubleshooting.

Steps to Access Detailed Action History:

1. Navigate to the Action Summary Page.
2. Click on a rule name or its Pass/Fail count in the execution table.
3. A detailed table opens, showing:

• Rule Name
• Username (who executed the action)
• Hostname (device where the action occurred)
• Action Result (Pass/Fail/Admin Action)
• Execution Time (start/end timestamps)

Using the Data for Insights:

• Sort & Filter the execution history based on date, result type, or rule name.
• Identify Trends to detect repeated failures or admin action requirements.
• Troubleshoot & Audit to improve proactive self-healing efficiency.

3. Why Do Some Self-Heal Rules Require User/Admin Action?

While Self-Heal rules automate IT maintenance, certain tasks cannot execute without manual intervention due to system security and operational requirements.

User Action Required (To Avoid Disruptions):

Examples:

• Clearing browser cache/cookies.
• Restarting applications.

Why?

• Users may be actively working on a browser or app, and interrupting their session could cause loss of work.

Admin Action Required (For Security & Permissions):

Examples:

• Updating group policies.
• Clearing system-wide temporary files.
• Modifying security settings.
  

  ---