Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Defining dynamic collectors

Dynamic collectors are created automatically when specified events are received. When specified events are deleted or changed and the associated collector becomes empty, the collector is removed. Dynamic collectors reflect the dynamic nature of event sources.

Events are generated for network-related issues in the following definition of class NET:

MC_EV_CLASS: NET ISA EVENT ; END

In the following example, NET events are generated for network-related issues. When the issue is specific to a subsystem, the kind of subsystem is specified in the mc_object_class slot. The collector definitions shown create a collector structure for each subsystem that produces events. The name of the collector is determined by the mc_object_class slot. Events that are not related to a specific subsystem are collected in the Global subcollector.

Within the subsystem collector, a distinction is made between events coming from servers and events coming from clients. When the mc_origin_class slot has the value SERVER, the event is assumed to come from a server. In that case, a subcollector is created for each server that produces events. The name of the subcollector is taken from the mc_origin slot.

collector Net END
collector Net.* : NET where [$THIS.mc_object_class != '']
create $THIS.mc_object_class delete
END
collector Net.*.Server : NET where [$THIS.mc_origin_class == SERVER]
END
collector Net.*.Server.* : NET
create $THIS.mc_origin
END
collector Net.*.Client : NET
END
collector Net.Global : NET
END

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*