Probes collect fault messages throughout the network and forward them in a common format to the ObjectServer for further processing and filtering, and for display and management in customizable operator views.
Users, using a point-and-click interface, can prioritize events according to the business services they could potentially impact. The user can react to events in real-time and see them in color-coded severity through event lists, or monitor the availability of business services using service-level histogram summaries.
Probes have three basic components
· Executable (nco_p_<probename>)
· Properties (.props) file
· Rules (.rules) file.
The Executable is what creates the connection to the source and performs all of the “work”.
The Properties File is what sets up the environment that the executable runs in. It is basically a list of arguments that could be set as command line arguments. They are in a name/value pair format using a colon (:) as a separator.
The Rules File is used by the executable to format all of the events received by the probe in to a common format that is then forwarded to the ObjectServer in a common format. It is also used to create the Identifier field that is unique to each event. This allows for the deduplication process to correlate duplicate events.
The script language used by the rules file is proprietary, but is similar to many other common scripting languages. The best source for details is Chapter 2 of the Probe and Gateway Guide.