To add an Incidents List dashlet to a custom dashboard
To view details of an incident
To configure, filter or export the table in the dashlet
Introduction:
The Incidents List dashlet shows you a list of the incidents on a managed object, together with key details on those incidents.
The Incidents List dashlet is applicable to any data source (e.g. Views, devices, services etc).
To add an Incidents List dashlet to a custom dashboard:
- When adding a dashlet to a new custom dashboard or editing an existing custom dashboard, follow the instructions for adding a dashlet, select Incidents List in the Select Dashlet Type, and click Next.
- The Create Dashlet form will slide in on the right, which contains the following sections and fields:
Dashlet Settings
- Enter a name of your dashlet in the Name field.
- You can then choose the source of the data to be displayed in the dashlet. You have three options:
- If you want this dashlet to source its data from the context of its parent dashboard, select Dashboard. You can see the context of the parent dashboard in the Dashboard Context field at the top of the form.
- If you want this dashlet to source its data from another dashlet in this current dashboard, select Dashlet.
- If you want this dashlet to source its data from a specific managed object or objects on your network, select Fixed Object. You can then click Browse to an object to search for the object(s) in explorer, or drag into the box your desired object(s) in from another browser window.
Incident State
- Specify the types of incident state that you want to include in the incidents list by clicking on the State field. This opens a new form, where you can tick boxes for Open, Closed and Expired incidents to be included in your dashlet.
Incident Severity
- Select the incident severity states you want to include by clicking on the Severity field. This opens a new form, where you can tick boxes for Information, Minor, Major, Severe and Critical.
Incident Type
- Specify which events you want to include in the list in the Incident Filter dropdown field. You can choose between All Incidents (default), Include Incidents and Exclude Incidents. If you choose Include Incidents or Exclude Incidents, the Incidents Included / Excluded field appears below. Clicking this takes you to a new form where you can choose the events you include or exclude respectively.
Incident Timeframe
- Specify the timeframe of included events in the Apply Timeframe To field. You can use this field to filter incidents depending on how 'active' they have been within the specified timeframe, e.g. whether they have been opened and not updated, or if they have since been updated. Select from one of the following options:
- Last Updated Time.
- First Opened Time.
- Last Closed Time.
- Specify whether to Use Dashboard Timeframe. If switched off, you can then specify a custom timeframe to apply to the dashlet.
Assigned To
- Select the user or user group to whom you want to assign the incident list in the Assigned To dropdown filter. The default is Anyone.
Advanced Settings
- Click the Advanced Settings field to open the Advanced Settings form.
- Choose whether you want to hide the title of the dashlet in the Hide Title Bar field. If selected, the dashlet's Overflow Menu will also be hidden, but in the Promote Menu Options field you can then choose if you want to display the options in the dashlet's Overflow Menu in the overall dashboard's Overflow Menu.
- Choose whether you want the dashlet to automatically refresh in the Auto Refresh field. By default this is set to On.
- Click Done in the top right of the form to save and return to the Create Dashlet form, otherwise click Cancel.
- Click Done to save your dashlet, otherwise click Cancel.
To view details of an incident:
- You can either view the details of an incident in the table of the Incidents List dashlet, you can select the incident and click Details in the top right, or you can select the incident and right click to bring up the Context Menu and click Show Details. You can also access details by right clicking on the selected incident and clicking Details.
- The Incident Details form will slide in on the right with important details about the incident.
The Incident Details form lists the following information about the selected incident:- Name - name of the incident, e.g. 'Blacklisted Application Detected'.
- State - state that the incident is in, which is either Open, Closed or Expired.
- Open For - how long the incident has been open for.
- Source - source of the incident. This will be a managed object, e.g. 'netbios on hq01:[Se0/1/0] Serial0/1/'
- Details - details of the incident, e.g. 'netbios detected (out)'.
- First Opened - time and date the incident was first raised.
- Last Opened - time and date the incident was last opened, if it had previously been closed.
- Last Closed - time and date the incident was last closed, if at all.
- Annotation - any annotation added to the incident by a user.
- Annotated by - user who added the annotation (Entuity v19.0 P03 upwards).
- Closed by - user who last closed the incident (Entuity v19.0 P03 upwards).
- Contributing Events - a list of every event that contributes to the selected incident. You can click on the individual event to open the Event Details form, which provides further information.
To close an incident:
- Select the incident that you want to close and click Close in the top right of the browser, via the dashlet Overflow Menu, or via the incident's Context Menu.
- This will open the Close Incident form on the right of the screen. You can choose to enter an annotation about this closure in the Annotation field, and if you want to immediately close the incident, turn the Expire the incident(s) immediately switch to On.
- Click Done in the top right of the form to close the incident, otherwise click Cancel.
To annotate an incident:
- Select the incident to which you want to add an annotation and click Annotate in the top right of the browser, or via the dashlet Overflow Menu.
- The Annotate Incidents form will slide in on the right. Enter the note in the Annotation field and click Done to save, otherwise click Cancel.
To assign an incident:
Each incident can be assigned to a specific user. This way, a user can easily filter all incidents to see which are assigned to them.
- Select the incident you want to assign to a user and click Assign in the top right of the browser, or via the dashlet Overflow Menu.
- The Assign Incidents form will open on the right of the browser. Select the user to whom you want to assign the incident in the User dropdown menu and click Done to assign, otherwise click Cancel.
If you select multiple incidents that are assigned to multiple users, a warning message will appear to inform you that the incidents are assigned to more than one user.
To configure, filter or export the table in the dashlet:
Please see the article on configuring tables in Entuity.
Column Name | Column Description |
---|---|
! | severity level of the incident, which is inherited from the highest severity level of its constituent events. |
A | indicates with a tick if the incident has any annotations/notes. |
# | number of events raised against the incident, including opening, updating and closing events. |
Name | name of the incident, e.g. 'Blacklisted Application Detected'. |
Source | source of the incident. This will be a managed object. |
Details | details of the incident. |
Last Updated | time and date the incident information was last updated. |
First Updated | time and date the incident was first raised. |
Last Closed | time and date the incident was last closed, if at all. |
State | state that the incident is in, which is either Open, Closed or Expired. |
Server | the server on which the incident has been raised. |
Assigned User | the specific user who has been assigned the incident. |
Closed By | Entuity v19.0 P03 upwards. User who last closed the incident. |
Annotated By | Entuity v19.0 P03 upwards. User who added the annotation. |
[Custom Attribute Name] | Entuity v19.0 P04 upwards. User-specified custom attribute added to the incident, e.g. as an event rule or event trigger. |
RESTful API:
Please see the following for help and information on incident functionality in Entuity RESTful API:
Comments
0 comments
Please sign in to leave a comment.