Power Automate Webhooks - Impactos en la capa de entidades en otra cuenta AGOL.

ArturOliveiraSecto

Al usar webhooks en capas de entidades alojadas en otra Cuenta de Organización, entendemos que no hay uso de créditos. <\/P>

En relación con el ancho de banda, ¿hay un gran impacto? ¿Cómo podemos calcular el impacto? Estamos intentando almacenar solo un cambio de atributo para que sea capturado por el webhook habilitado en la capa de entidades de otra organización. <\/P>

Digamos: en una capa de entidades compartida por la otra organización para que editemos, tenemos 500 actualizaciones en ese atributo, distribuidas entre 5 subcapas. Esto se multiplica por 5, considerando que trabajamos en 5 capas de entidades simultáneamente. Eso significa 2,500 cambios capturados durante el día. nota: estamos sobreestimando estas métricas solo para estar seguros.<\/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
  }
}