8-10
Cisco Prime Network 4.0 User Guide
OL-29343-01
Chapter 8 Tracking Faults Using Prime Ne t work Events
Working with Cisco Prime Network Events
For information about viewing ticket properties, see Viewing Ticket Properties, page 8-14.
Working with Cisco Prime Network Events
The following topics describe how to view, filter, and display the properties of specific events and
tickets, and how to refresh and export events:
• Viewing Event Properties, page 8-10
• Viewing Ticket Properties, page 8-14
• Refreshing Cisco Prime Network Events Information, page 8-17
• Filtering Events, page 8-18
• Exporting Displayed Data, page 8-21

Viewing Event Properties

Cisco Prime Network Events enables you to view the properties of a specific event type. The Event
Properties window displays detailed information about the event; for example, the severity and the
number of affected parties.
Tip Clicking the Details tab on the Event Properties window displays the properties of the selected ticket or
event in the Properties pane.
Acknowledged Whether the ticket is acknowledged or has been modified: Yes, No, or
Modified. If a ticket changes after it has been acknowledged, it is
marked as Modified. If an acknowledged ticket is deacknowledged, the
status changes from Yes to No in this column.
Creation Time Date and time that the ticket was created.
Event Count Number of events associated with the ticket.
Affected Devices Count Number of devices affected by the ticket (the sources of the alarm and
their subsequent alarms).
Duplication Count For tickets, the duplication count is the sum of the duplication counts of
all events that are associated with the root alarm.
Reduction Count Ticket reduction count is the sum of reduction counts of all the events
that are associated to the ticket. The History tab in the Ticket Properties
window displays one reduction count for each event listed. For mor e
information, see Chapter 9, “Working with Tickets in Prime Network
Vision.”
Alarm Count Total number of alarms associated with the ticket, including the root
alarm.
Table 8-12 Ticket Tab (continued)
Column Description