Power Automate Webhooks - 別の AGOL アカウントのフィーチャ レイヤーへの影響。

ArturOliveiraSecto

別の Organization Account にホストされているフィーチャ レイヤーで webhooks を使用する場合、クレジット使用量はないと理解しています。 <\/P>

帯域幅に関しては、大きな影響がありますか？影響をどのように計算できますか？別の組織のフィーチャ レイヤーで有効になっている webhook によってキャプチャされる属性の変更を 1 つだけ保存しようとしています。 <\/P>

例えば：他の組織が共有して編集できる 1 つのフィーチャ レイヤーで、その属性に 500 の更新があり、5 つのサブレイヤーに分散しています。これを 5 倍すると、同時に 5 つのフィーチャ レイヤーで作業していることを考慮しています。つまり、1 日中に 2,500 の変更がキャプチャされることになります。注：安全を期すためにこれらの指標は過大評価しています。<\/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
  }
}