Rules Analytics

1. Introduction to Rules Execution Analytics

The Rules Page provides a detailed analysis of proactive rule executions within the system. It enables administrators to track the number of rules executed, their status, and any necessary actions required. This section is essential for ensuring automated processes run efficiently and with minimal user intervention.

2. Key Information Available in the Rules Execution Section

Summary of Rule Execution:

• Total Rules: Displays the total number of proactive rules configured and executed within a given period.
• No Action Required: Rules that executed automatically and completed their process without user intervention.
• Action Required: Rules that require user interaction or administrative approval before execution.
• Not Applicable: Rules that did not meet execution conditions and were skipped.

Detailed Table Structure:

• Rule Name: The name or title of the rule being executed.
• Username: Identifies the user under whom the rule was executed.
• Hostname: Specifies the machine where the rule was executed.
• Status: The execution outcome, categorized as “No Action Required,” “Action Required,” or “Not Applicable.”
• Action: Specifies the action performed or required (e.g., “No Action”).
• Details: Additional context about the rule execution, such as special conditions or dependencies.
• Run Time (in seconds): The time taken for rule execution.

3. Exploring Rule Execution, Users, and Host Systems

1. Rule Insights:

• Clicking on a rule (e.g., “Restart Essential Services”) opens the Proactive Analytics section.
• Execution counts are categorized under No Action Required, Action Required, and Not Applicable.
• A status graph provides a visual distribution of execution statuses.
• A detailed table lists execution history with details like username, hostname, status, and run time.

2. User Activity Tracking:

• Selecting a user provides machine-specific details in Agent Analytics, including hostname, IP address, last activity, and version.
• The Proactive Analytics section lists all rules associated with the user, along with their statuses and execution logs.
• The Proactive Actions section summarizes action results and tracks timelines.
• The Remote Solution Firing Analytics feature monitors remotely triggered deployments.

3. Host Performance Monitoring:

• Clicking on a host displays execution history within Agent Analytics, showing hostname, IP address, and last recorded activity.
• The Proactive Analytics section lists all rules executed on the host, including their status, run time, and date.
• The Proactive Actions section captures action outcomes and timelines.
• The Action Event Analytics section logs remotely executed actions on the host.

4. Why Might a Proactive Solution Require User or Admin Action?

User Action Required:

• Some proactive solutions need user approval to prevent disruptions.
• Example: Restarting an application might require confirmation if the user is actively using it.

Admin Action Required:

• Some solutions involve changes that require administrative privileges.
• Example: Updating group policies or modifying system configurations requires admin-level access.