Power Automate Webhooks - Invloed op feature layer in een ander AGOL-account.

ArturOliveiraSecto

Bij het gebruik van webhooks in feature layers die worden gehost in een ander Organization Account, begrijpen we dat er geen creditgebruik is. <\/P>

Met betrekking tot bandbreedte, is er een grote impact? Hoe kunnen we de impact berekenen? We streven ernaar om slechts één attribuutwijziging vast te leggen die wordt opgevangen door de webhook ingeschakeld in een feature layer van een andere organisatie. <\/P>

Laten we zeggen: in één feature layer gedeeld door de andere organisatie zodat wij kunnen bewerken, hebben we 500 updates in dat attribuut, verdeeld over 5 sublayers. Dit wordt vermenigvuldigd met 5, rekening houdend met het feit dat we tegelijkertijd in 5 feature layers werken. Dat betekent 2.500 wijzigingen die gedurende de dag worden vastgelegd. Opmerking: we overschatten deze cijfers om veilig te spelen.<\/P>

KevinHibma

This is a difficult question to answer, but simply, you shouldn't see any impact on the feature layer because of the webhook traffic. After the edit is performed, the information for the webhook is processed in a separate process from the feature layer. The feature layer doesn't become locked, or wait for the webhook to finish.

Is it possible this many edits could cause the webhook process to degrade? Maybe? Probably not? Again, a very difficult question to answer without actually benchmarking it (I do not have metrics like these). You can't control the ArcGIS Online processes that do this. What you do have control over is where the webhook is being sent to, which is either a commercial vendor or your own custom service -- does this process scale and handle a lot of webhooks? You might want to try and reduce the number of webhooks being dispatch which would reduce load everywhere. Take a look at the scheduleInfo parameter when you create your webhook. By increasing the frequency, more edits will be grouped into a single webhook. However, as-is, you shouldn't really expect more than 2 webhooks dispatched every minute (based on the 30 second default). That means you could have 3 edits or 10,000 edits in a single 30 second time period, it'll only ever be 1 webhook.

{
  "name":"Every-30seconds",
  "startAt":"1478280677536", //Integer
  "state":"enabled",
  "recurrenceInfo": {
    "frequency":"second",
    "interval":30
  }
}