Event synchronization

Synchronization enables the probe to collect any events that the NNMi system generated while the probe was disconnected. In addition, the probe can resynchronize with the NNMi system at regular intervals. You can use any combination of these synchronization features.

Initial synchronization

Each time the probe starts it can synchronize with the NNMi system to acquire all the events that the NNMi system holds. Use the InitialResync property to control whether the probe carries out an initial synchronization, but instead performs a resynchronization at the interval defined by the ResyncInterval property.

When the value of the property is true, the probe carries out an initial synchronization. When the value of the property is false, the probe does not carry out an initial synchronization.

By default, the probe does not synchronize with the NNMi system at startup.

Synchronization at intervals

In addition to synchronizing with the NNMi system at startup, the probe can also resynchronize with the NNMi system at regular intervals. Use the ResyncInterval property to define whether the probe synchronizes with the NNMi system at intervals and how frequently.

When the value of the property is 0 or less, the probe does not resynchronize with the NNMi system at regular intervals. When the value of the property is a positive number, the probe resynchronizes with the NNMi system regularly. The value of the property specifies the number of seconds between each resynchronization operation.

By default, the probe does not regularly resynchronize with the NNMi system.

Synchronization in batches

You can use the ResyncBatchSize property to specify the maximum number of alarms contained in each batch that the probe receives during the resynchronization operation. There may be multiple batches within one resynchronization operation.

The default value of this property is 100.

Defining a resynchronization filter

By default, a synchronization operation retrieves all the events that the NNMi server currently holds. You can use a resynchronization filter to limit the number of events that the event retrieves. Three properties contain the resynchronization filter:

  • ResyncFilterName
  • ResyncFilterOperation
  • ResyncFilterValue

ResyncFilterName

ResyncFilterName identifies a field in the event that you want to filter on. You can specify the following:

  • assignedTo
  • category
  • cias
  • created
  • duplicateCount
  • family
  • firstOccurrenceTime
  • formattedMessage
  • id
  • lastOccurrenceTime
  • lifecycleState
  • modified
  • nature
  • name
  • notes
  • origin
  • originOccurrenceTime
  • priority
  • rcaActive
  • severity
  • sourceName
  • sourceNodeName
  • sourceNodeUuid
  • sourceType
  • sourceUuid
  • uuid

ResyncFilterOperation

ResyncFilterOperation defines a condition to use in the filter. You can use the following operators:

  • =
  • !=
  • <
  • <=
  • >
  • >=
  • LIKE
  • NOT IN

ResyncFilterValue

ResyncFilterValue defines the value of the field identified in ResyncFilterName to be compared against the corresponding field in each event using the operation in ResyncFilterOperation.

Example

To retrieve only those events that have a severity of Error or greater, use the following property values:

ResyncFilterName: "severity"
ResyncFilterOperation: ">="
ResyncFiltervalue: "ERROR"

Optimized Synchronization

During a resynchronization operation, the probe tries to optimize the process by only retrieving events that it has not retrieved previously. The probe does this using the time stamp associated with each event.