Incident Search
Overview
The Incidents page lets you search and filter incidents
A collection of one or more related triggers. Relationships that cause triggers to be combined into incidents include application, location, operating system, or a trigger by itself. so you can find a specific set (for example, by description text, status, priority, incident type, or time range). That capability makes it easier to triage, track ongoing work, or pull incidents for reporting. You open an incident from the list to see its full details on the Incident Details page. For day-to-day incident handling, see Managing Incidents.
Incident search uses the common faceted search controls. The filter bar can include a type menu and a time range. Select Incidents from the type menu to search incidents.
Incident filters
The available facets reflect the incident data in your environment. Typical categories include:
-
Ongoing State: Whether the incident is still ongoing or has ended.
-
Status: New, Investigating, or Closed.
-
Priority: Critical, High, Moderate, or Low.
-
Incident Type: For example, Device Down Issue, Interface Performance Issue, Application Location Performance Issue, Multi-Device Down Issue.
-
Entity-based facets: Device name, Interface name, Application name, Impacted Application, Impacted Location, Impacted User. These narrow results to incidents that involve the selected entities.
When no search criteria are present, the page initially filters for ongoing incidents with New or Investigating status and Critical or High priority. Change or clear these facets to broaden the results.
Use the time range to restrict results by when incidents were created. To find incidents by entity or metric from elsewhere in the product, you can also use global search. Results include incidents where that object appears as an indicator.
Things deployed in the customer environment that are needed to run the business, such as applications, devices, interfaces, and locations.), use the Audit Log page under IQ Ops Management.