> 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/ko/reports-and-monitoring/alarms-devices-bandwidth-usage.md).

# 알람 장치 대역폭 사용량

Verkada 알람 장치의 대역폭 사용량

{% hint style="success" %}
이 문서는 새 Alarms를 위한 가이드입니다. 이 문서를 참조하세요 [문서](/classic-alarms/ko/monitoring-and-reports/classic-alarms-devices-bandwidth-usage.md) 기존 Alarms를 사용하는 경우. 다음을 참조하세요 [New Alarms와 Classic Alarms 비교](/new-alarms/ko/getting-started/new-alarms-vs-classic-alarms.md) 어떤 버전의 Alarms를 사용 중인지 확실하지 않은 경우.
{% 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/ko/reports-and-monitoring/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.