Power Automate Webhooks - Dopady na feature layer v jiném AGOL účtu.

ArturOliveiraSecto

Při použití webhooků ve feature layers hostovaných v jiném Organization Account chápeme, že nedochází k využití kreditů. <\/P>

Co se týče šířky pásma, je na ni velký dopad? Jak můžeme vypočítat tento dopad? Snažíme se zaznamenat pouze jednu změnu atributu, kterou zachytí webhook povolený ve feature layer jiné organizace. <\/P>

Řekněme: v jednom feature layer sdíleném jinou organizací pro nás k úpravám máme 500 aktualizací tohoto atributu, rozdělených mezi 5 sublayerů. Toto se násobí 5, vzhledem k tomu, že pracujeme současně ve 5 feature layers. To znamená 2 500 změn zachycených během dne. poznámka: tyto metriky nadhodnocujeme jen pro větší jistotu.<\/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
  }
}