Viewing Existing Incidents

the incidents screen displays a list of incidents that were either created manually or automatically generated by the system by default, if it was automatically created, the name will include the following structure \<root cause category> \<identifier> root cause category the name of the root cause category see root cause column description below for example, ‘server network’ identifier for networks, the identifier used is the network’s asn parameter description name the name of the incident the name can be edited by default, if it was automatically created, the name will include the following structure \<root cause category> \<identifier> root cause category the name of the root cause category see root cause column description below for example, ‘server network’ identifier for networks, the identifier used is the network’s asn state indicates whether the incident has been marked as closed by the user or is still open the open state can be active – errors are still being generated ended – errors are no longer generated by default, the window duration for checking if it has ended or it’s ongoing is 20 minutes (i e , if no issues occurred during 20 minutes then it has ended) this parameter is relevant for automatically generated incidents only start time the time in which the incident was first created duration the overall time from the creation of the incident until now runtime state indicates whether the incident is ongoing or it has ended by default, the window duration for checking if it has ended or it’s ongoing is 20 minutes (i e , if no issues occurred during 20 minutes then it has ended) this parameter is relevant for automatically generated incidents only root cause indicates the probable root cause of the incidents by categorizing it into the following categories server network the network where the broadcaster resides client network the network where the target or source resides broadcaster indicates that although this is not a network related incident, a broadcaster may be the root cause of the incident content analysis – the incident is related to errors detected in the audio and video content itself performance – the incident is related to performance issues other the incident is related to other issues description in case of an auto generated incident, the description includes the reason for generating the event this description includes an indication of the number of components in the network that have experienced the issue (e g , unrecovered packets events) around the same time currently, the threshold for generating an event is that over 50% of the components (targets/sources/broadcasters) in the network have experienced the issue around the same time # objects indicates the number of objects that are involved in the incident actions click the trash icon to delete the incident