COURSE
AppNeta: Support Triage Playbook
Learn the steps to triage and investigate issues with AppNeta in order to resolve issues or gather preliminary information to hand off an investigation to next-level support and product engineers.
Start This Course
August 13, 2026
45 minutes
Badge
AppNeta Support Playbook
What You Will Learn
Learn the steps to triage and investigate issues with AppNeta in order to resolve issues or gather preliminary information to hand off an investigation to next-level support and product engineers.
The course was last updated to align with AppNeta version 19.14.0.
To learn about changes and enhancements released since the last course update, refer to the AppNeta documentation: Release Information.
Roles
-
AppNeta administrators
-
Technical support specialists
-
Broadcom partners
Prerequisites
Before taking this course, you should have a strong understanding of Unix/Linux operating systems, including command-line usage, system administration, and troubleshooting.
This course assumes some familiarity with concepts covered in the following courses:
-
AppNeta: Getting Started
-
AppNeta: Introducing the Intelligent Alarms Experience
-
AppNeta: Create Monitoring Policies for Active Monitoring
Exercises
This course contains practice scenarios.
Completion Criteria
To complete this course, you must pass the final test with a score of 80% or higher.
What You Will Earn
Upon completion, you will receive:
- A certificate validating the course completion
- The AppNeta Support Playbook badge
Course Objectives
After taking this course, you should be able to:
- Diagnose reports of an inaccessible AppNeta web user interface.
- Triage reports of AppNeta user interface slowness.
- Troubleshoot failed AppNeta application login.
- Diagnose Monitoring Point connectivity to AppNeta.
- Diagnose Monitoring Point connectivity to a path target.
- Diagnose a Monitoring Point upgrade failure.
- Diagnose a hardware Monitoring Point boot failure.
- Diagnose gaps in path metrics.
- Diagnose a misconfigured alarm connector.
- Troubleshoot a failed browser workflow.
- Troubleshoot Monitoring Point local SSH access.


