Usage guide: Investigations starter pack

This page outlines various ways to use the pack, including use case examples.

Administrators can refer to the Configuration guide: Investigations starter pack to set up and customize the installed content.

The Getting started investigations library pack enables EUC teams to leverage pre-built investigations or out-of-the-box solutions to:

• Quickly gain insights on common and recurring issues.

• Accelerate NQL proficiency within your organization by exploring the underlying queries.

Library pack use: quick investigation execution

Jump to Use cases on this page to see relevant scenario applications.

Find in the Configuration guide: Investigations starter pack a purpose/description for each pre-defined library investigation. These investigations are ready to use once installed.

You can quickly customize and reuse these library investigations as-is or as templates by, for example, adding additional fields or columns to incorporate more information into the investigation results table.

Refer to the Investigations documentation to learn more about managing, editing, running, and sharing investigations.

Use case example: Investigating system errors versus devices

Use System crashes by error label predefined investigation to investigate System crashes.

Without relying on Nexthink Assist to query System crashes from scratch, you can simply edit the installed System crashes by error label library investigation and add the Device model and Hardware → Manufacturer field columns to correlate specific errors with particular models or manufacturers.

Both the NQL editor and Visual editor support investigations installed from the library.

The image below displays the device model and manufacturer associated with System crashes.