Incidents

the incident view groups together related errors into incidents to simplify the process of identifying the common root cause incidents can be manually created or automatically generated manually created incidents incidents can be created manually through the history tab of a resource (zixi edge device, broadcasters, sources, and targets) by selecting a time range during which a series of related failures took place you can customize the display of relevant graphs and data, enabling you to build your own customized incident reports, and share them with the relevant stakeholders automatically created incidents – zen master automatically groups errors into incidents, by determining correlations between individual object incidents the incidents are reported when there are 3 or more sources, targets, or broadcasters having errors at the same time that share a common resource, and when at least 50% of the objects that share that resource are experiencing errors at the same time frame of 10 minutes errors that happen on these objects within 10 minutes of a previous error are grouped together into the incident it is possible to have multiple related incidents if there is a period of more than 10 minutes without any errors in some cases, if there are multiple shared resources, the system may also report multiple related incident records the shared resources, which determine the type of grouping include the following client network – the network where source or target objects are connected networks are identified by network asn (autonomous system number), country code, and region code for example, us oh 123 is a network in ohio in the united states with asn 123 server network – the network where a broadcaster is connected network path – the connection between a source and a broadcaster broadcaster – the shared zixi broadcaster there are two types of automatically created incidents network error – this type of incident is triggered by errors related to the network, such as unrecovered packets, etc object error – this type of incident is triggered by a tr101 cc error on a source, or a broadcaster max cpu error, or any error reported in zen master viewing existing incidents docid bdtvgzcmrtrtvt1cecit filtering the list of incidents docid\ h0dpko0qdu1mvotorz9m viewing the incident details docid\ sdalylpt9pin6qdiizxwy incident details graphs view docid\ plshiaahmtmknpgaa6qr5 incident details events view docid\ if823wvxglufkjfxdsifa notes pane docid\ ittoxx8gcopfsuxmlly4h creating an incident manually docid\ aomjabsyzylzy3gq4zh8o