Add eventTime to all webhooks

[alexanderdean]

As a webhook, we don't have a device sent timestamp, so we need an updateTime (or equivalent name) sent with each event.

[alexanderdean]

Bringing this forward as this will really simplify @ihortom's visualization...

[ninjabear]

Hey @alexanderdean (or @ihortom) , what's the plan for the update information? When I initially wrote the webhooks I didn't include this because it seemed like you'd only ever need to know the start/end time of tasks. Based on this ticket I think there's a use case I missed?

[alexanderdean]

Hey @ninjabear - I think the name of this new field is misleading - I've updated it to eventTime.

The reason for this field is so that there is a uniform top-level field in all webhooks which indicates when the webhook event was created.

This is important because otherwise an analyst looking at these webhooks in Snowplow is left relying on webhook-specific fields or worse the collector_tstamp.

Does that make sense?

[ninjabear]

Ah cool, yes I see what you mean. I did think of adding a "sequence number" so you could sort events based on that (e.g. event 1 of n) but eventTime is probably an easier way to reason about it!