Analytics

Introduction to Device Analytics and Self-Heal

The Device Analytics & Self-Heal System provides IT teams with advanced tools for tracking device performance, automating issue resolution, and maintaining system compliance. This module covers Self-Heal automation, execution monitoring, compliance tracking, and analytics reporting to optimize IT infrastructure.

1: Overview of Self-Heal and Its Importance

What is Self-Heal & Why is it Important?

Self-Heal is an automated troubleshooting mechanism that detects and resolves IT issues without user intervention.
Reduces manual troubleshooting efforts, ensuring proactive IT maintenance.
Enhances device health and stability by fixing common problems before they escalate.

2: Summary Page Insights

Understanding Host, User, and Rule Counts

Differentiating Between Rules Count & Total Rules Count

• Rules Count = Number of unique Self-Heal rules created.
• Total Rules Count = Total number of executions of all rules.

Example: If a rule applies to 10 devices, the Rules Count = 1, but Total Rules Count = 10 (one execution per device).

3: Host Analytics and Execution Monitoring

Tracking Host Execution Outcomes

• Shows whether Self-Heal solutions ran successfully or encountered issues.
• Displays execution trends across multiple devices.

Navigating the Host Summary Page

• Lists each host with associated users and rule execution statuses.
• Categorizes successful executions, failures, and admin-required actions.

Key Execution Statuses:
No Action Required: The system executed the rule without user interaction.
Action Required: User intervention was needed (e.g., closing an app before cache clearing).
Need Admin Action: Requires administrator approval (e.g., modifying system files).

4: Compliance and Non-Compliance Management

Understanding Device Compliance Metrics

• Compliance ensures all devices meet IT security and performance standards.
• Tracks compliant vs. non-compliant devices based on predefined rules.

Viewing Compliance and Non-Compliance Details

• Compliant Devices: Systems meeting all defined rules (e.g., updated OS, enabled firewall).
• Non-Compliant Devices: Systems failing one or more compliance rules (e.g., outdated antivirus).

Example: A device without BitLocker encryption is marked as Non-Compliant.

How to Fix Non-Compliance?

• Use Self-Heal Proactive Solutions to enforce compliance (e.g., enable firewall automatically).

5: Search and Filtering in Analytics

Searching for Users and Hosts in Analytics

• Find specific devices or users by entering hostnames/usernames.
• Use filters to view analytics per user, system, or rule execution.

Checking Usage Data for Specific Users and Hosts

• Displays last activity timestamps, installed versions, and performance logs.
• Helps IT teams validate system configurations and detect anomalies.

6: Proactive Rules Execution and Insights

Understanding Rule Execution Categories

Example: A Self-Heal rule clears temporary files but requires admin rights—this falls under Need Admin Action.

How to Track Execution Status?

• Navigate to Rule Execution Logs in the Admin Console.
• Analyze success/failure rates for each rule.

7: Action Analytics and Execution Trends

Analyzing Action Summary Data

• Tracks successful vs. failed executions across multiple devices.
• Helps IT teams identify trends and optimize rule execution.

Understanding Action Success, Failures, and Admin Requirements

8: Action Host Summary and Tracking

Understanding Host-Based Execution Trends

• View execution attempts per device and analyze trends over time.
• Drill down into specific host execution logs to find root causes of failures.

How to Track Admin-Required Actions?

• Navigate to Host Execution Summary to find rules needing admin approval.
• Take necessary manual actions to fix issues.

9: Agent Version and System Configurations

Monitoring Agent Version Data Across Hosts

• Ensures all devices run the latest Self-Heal agent version.
• Tracks outdated agents that need updates.

Updating the Self-Heal Agent:
Navigate to “Update Self-Heal Agent” in the Admin Console.
Upload the latest techselfsupport.zip update file.
Monitor deployment success via the Admin Dashboard.

10: Generating and Analyzing Reports

Navigating the Analytics Report Page

• Generate reports for Admin Actions, Rule Executions, Agent Versions, and more.
• Track IT performance trends over time.

Filtering Reports Based on Date Ranges

Define custom timeframes to analyze execution history.

Helps IT teams audit system health & compliance over weeks/months.

Understanding Report Types: