| Jane,
> I am working with a customer to migrate them from VCS to PCM. Due to
> the VCS limitation of max number of events/scan profiles that can be in
> a scan profile, the customer has many scan profiles that are 'nested'.
> I have not found any reference within this notesfile or in the
> documentation that PCM has the same or a similar limitation re:max # of
> events/scan profiles within a scan profile - can anyone verify for me
> whether such a limitation exists? Can anyone comment on the efficient
> way to set up scan profiles? Is it more efficient to select all events
> or is it better to break them up into scan profiles ? Or does it not
> matter at all and is instead at the administrators' discretion?
There are no limits within PCM as to the number of events in a scan or the
number of scans within a scan. As with VCS only a single scan is linked to a
system, but the number of events and scans linked are not limited. The PCM
system actually decomposes the scans into lists of events at initialization
time, so it is up to the customer how he wants to arrange the scans.
Realistically the concept of a scan is to group releated events together as a
convenience for the PCM administrator rather than any performance enhancement.
> Second question: Can anyone comment on how best to set up 'groups' of
> events for filter purposes? Is it best /most efficient to filter on
> class or event or system or??? I have the opportunity to set this right,
> so am interested in comments as to how others have approached this.
If you look at figure 8.6 in the PCM User guide this shows the matching flow
through ENS. Although there is very little difference really the absoulute best
performance is given when the first checks of a filter fail and hence get
discarded quicker for non-match cases.
Hope this helps.
Cheers Simon...
|