> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/new-alarms/ja/reptotomonitaringu/alarms-devices-bandwidth-usage.md).

# アラームデバイスの帯域幅使用量

Verkada アラームデバイスの帯域幅使用量

{% hint style="success" %}
この記事は新しいアラーム向けのガイドです。こちらを参照してください [記事](/classic-alarms/ja/monittorepto/classic-alarms-devices-bandwidth-usage.md) クラシック アラームをお使いの場合は、こちらを参照してください。詳細は [New アラームと Classic アラームの違い](/new-alarms/ja/hajimeni/new-alarms-vs-classic-alarms.md) どのバージョンのアラームをお使いか不明な場合は、こちらをご覧ください。
{% endhint %}

## BP52（アラームパネル）

* 5分間の出力レート: 10kps
* 5分間の入力レート: 10bps

{% hint style="warning" %}
これらの数値は、特定のパネルに有線または無線で接続されているセンサーの数や、これらのセンサーが生成するイベント数によって、増減する場合があります。その他の要因としては、BK22/BE32の更新があり、これにはより多くのネットワーク帯域幅が使用されます。
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.verkada.com/new-alarms/ja/reptotomonitaringu/alarms-devices-bandwidth-usage.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.