> 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.md).

# 보고 및 모니터링

- [알람 보고서](https://help.verkada.com/new-alarms/ko/reports-and-monitoring/alarm-reports.md): 모든 사이트의 활동을 보고 감사하세요
- [새 알람용 Verkada 알람 모니터링 전화번호를 저장하세요](https://help.verkada.com/new-alarms/ko/reports-and-monitoring/save-the-verkada-alarms-monitoring-phone-number-for-new-alarms.md): 휴대폰이 무음 또는 방해 금지 모드여도 알람 중 걸려오는 전화가 전달되도록 하세요
- [Verkada 모니터링 전화번호](https://help.verkada.com/new-alarms/ko/reports-and-monitoring/save-the-verkada-alarms-monitoring-phone-number-for-new-alarms/verkada-monitoring-phone-numbers.md): Verkada 모니터링 팀이 연락할 때 사용할 전화번호를 저장하세요
- [Verkada 모니터링 전화번호 - 캐나다](https://help.verkada.com/new-alarms/ko/reports-and-monitoring/save-the-verkada-alarms-monitoring-phone-number-for-new-alarms/verkada-monitoring-phone-numbers-canada.md): 주별 올바른 캐나다 출동 전화번호를 찾으세요
- [알람 장치 대역폭 사용량](https://help.verkada.com/new-alarms/ko/reports-and-monitoring/alarms-devices-bandwidth-usage.md): Verkada 알람 장치의 대역폭 사용량
- [새 알람의 긴급 출동](https://help.verkada.com/new-alarms/ko/reports-and-monitoring/emergency-dispatch-in-new-alarms.md)


---

# 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.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.