CIS-Event Management CIS-EM Syllabus Exam Questions Answers

The Alert Priority score 3106020.001 was calculated according to the following factors, ordered by their respective priority (2018-06-01 19:34:01 GMT) Category (Score, Weight)

1. Business services – (3.0, 1000000)

2. Severity – (1.0, 100000)

3. CI type – (60.0, 100)

4. Role – (2.0, 10)

5. Secondary – (0)

6. State – (1.0, 0.001)

The Alert Priority score 4406020.001 was calculated according to the following factors, ordered by their respective priority (2018-05-31 20:04:47 GMT) Category (Score, Weight)

1. Business services – (4.0, 1000000.0)

2. Severity – (4.0, 100000.0)

3. CI type – (60.0, 100.0)

4. Role – (2.0, 10.0)

5. Secondary – (0)

6. State – (1.0, 0.001)

The Alert Priority score 3306020.001 was calculated according to the following factors, ordered by their respective priority (2018-05-31 19:56:54 GMT) Category (Score, Weight)

1. Business services – (3.0, 1000000.0)

2. Severity – (3.0, 100000.0)

3. CI type – (60.0, 100.0)

4. Role – (2.0, 10.0)

5. Secondary – (0)

6. State – (1.0, 0.001)

They should be processed in the order in which they were received.

em_event table

System log module

Event Mangement dashboard

State management logs module

A business service

A technical service

An application service

A manual service

A scoped service

Filter out events on ServiceNow Instance for easier consolidation and aggregation.

Promote all events to alerts during initial implementation until you fully understand which should be ignored.

Filter out events at source rather than in the ServiceNow instance.

Base-line “normal-state” events to filter out background noise.

Ignore all non-critical events during initial implementation to streamline processing; add alerts over time as time and resources allow.