Action Host Summary

1. Introduction to Action Host Summary Analytics

The Action Host Summary Page provides insights into proactive rule actions attempted across multiple host systems. It categorizes actions as Pass, Fail, or Need Admin Action and displays execution trends over a selected date range. This helps administrators assess host performance, troubleshoot issues, and optimize automation strategies.

2. Key Information Available in the Action Host Summary Section

1. Action Summary Overview:

• Host Count: Displays the total number of unique hosts where actions were attempted within the specified date range.
• Total Actions Attempted: The overall count of rule executions across all hosts, providing insight into the system’s operational activity.
• Action (Pass): The number of successfully executed actions across all hosts, indicating effective rule execution.
• Action (Fail): The number of failed actions due to reasons such as permission denials, system conflicts, or execution errors.
• Need Admin Action: The count of actions that require administrative intervention to complete due to elevated privileges or manual execution.

2. Detailed Table Structure:

Each row in the table corresponds to a specific host and includes:

• Host Name: The system where actions were performed.
• Total Actions: The number of actions attempted on the host.
• Pass: The number of successfully executed actions.
• Fail: The number of actions that failed to execute properly.
• Need Admin Action: The count of actions requiring administrator intervention.

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

Navigating the Action History Analytics Page:

1. Click on a host name in the table to open its detailed action history.
2. The system presents a comprehensive view of all actions attempted on the selected host within the specified date range.
3. The detailed table includes:

• Action Attempted for Rules: The specific rule for which the action was executed.
• Username: The user associated with the action.
• Hostname: The specific system where the action occurred.
• Action Result: Indicates whether the action was successful (Pass) or failed (Fail), with failure reasons if applicable.
• Details: Additional context about the action execution.
• Run Time (in seconds): The duration taken to execute the action.
• Count: The number of times the rule was executed.
• Start Date and End Date: The precise timestamps for each execution.

4. Importance of Admin Action in Host-Level Execution

Some actions require user input or administrative intervention due to security restrictions or operational dependencies:

User Action Required:

• Certain tasks, like clearing cache or restarting applications, may need user approval to prevent disruptions.
• Example: If a browser is in use, the user must confirm before the cache is cleared.

Admin Action Required:

• Tasks such as modifying security settings or updating system configurations require elevated permissions.
• Example: System-wide policy updates need administrator access to execute successfully.