> For the complete documentation index, see [llms.txt](https://ticketking.xyz/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ticketking.xyz/docs/ko/logging.md).

# 로깅

- [로그 채널](https://ticketking.xyz/docs/ko/logging/three-log-channels.md): 열린 티켓, 닫힌 티켓, 프리미엄 티켓 평점 로그에 대한 Discord 로그 채널.
- [패널별 로그 재정의](https://ticketking.xyz/docs/ko/logging/per-panel-overrides.md): 한 패널의 로그를 서버 전체 기본값과 다른 채널로 전송합니다.
- [로그 항목에 표시되는 내용](https://ticketking.xyz/docs/ko/logging/log-embed-contents.md): 로그 항목이 알려주는 내용과 트랜스크립트 링크 위치.
- [트랜스크립트 캡처 제한](https://ticketking.xyz/docs/ko/logging/transcript-capture-limits.md): 트랜스크립트에 포함되는 메시지 수입니다. 무료 1000개, 프리미엄 5000개.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ticketking.xyz/docs/ko/logging.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.