Doubt on setting the PageSize in Events function.

[akankshadokania]

Hi,
func (m Manager) Events(ctx context.Context, objects []types.ManagedObjectReference, pageSize int32, tail bool, force bool, f func(types.ManagedObjectReference, []types.BaseEvent) error, kind ...string) error {
What is the pageSize generally preferred? And, suppose if I set it to 25 and from vCenter I receive 35 events, is there a way to fetch the older events than those 25 events...the previous 10 events to these 25 events?

[dougm]

You'll get the updates, but can't go back in history. However, you can use HistoryCollector for that:
https://code.vmware.com/apis/704/vsphere/vim.HistoryCollector.html

There are wrappers in the govmomi 'event' package. The Events() method has the advantage of also working directly against ESX, but HistoryCollector is vCenter only.

As for the page size, it's mainly tuning for memory use and network transfer.

[dougm]

We need some examples for EventHistoryCollector, but there's a test that'll do for the moment:

govmomi/simulator/event_manager_test.go

Line 160 in deff37c

c, err := event.NewManager(vc.Client).CreateCollectorForEvents(ctx, spec)

[dougm]

I was thinking ReadNextEvents would block until there were more events, but looks like that's not the case. Sorry for the confusion, the Events() method actually does use EventHistoryCollector:

govmomi/event/processor.go

Line 61 in deff37c

collector, err := p.mgr.CreateCollectorForEvents(ctx, filter)

It must have been TaskHistoryCollector that is vCenter only.

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Mark as fresh by adding the comment /remove-lifecycle stale.

[embano1]

In the upcoming release, this method will be marked deprecated (see #1775)

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Mark as fresh by adding the comment /remove-lifecycle stale.