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

# 데이터 리포트

## 개요 <a href="#overview" id="overview"></a>

데이터 분석에서 저장한 데이터 분석 차트를 리포트에 추가하여 모아 볼 수 있습니다.\
리포트를 통해 필요한 데이터를 한눈에 빠르게 모니터링하고, 팀원들과 손쉽게 데이터를 공유해보세요.

![데이터 리포트](https://2738466581-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLHRZjjknm5KdNgPtDsbl%2Fuploads%2Fgit-blob-0206c88b4ab9e2b38c0ef3115df88288dd2923b1%2F3a1c5642b3c97fa19c28cd346430c05e2623e5cf_ea91e2efd4be4986.png?alt=media)

## 데이터 리포트 목록 <a href="#data-report-list" id="data-report-list"></a>

![데이터 리포트 목록](https://2738466581-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLHRZjjknm5KdNgPtDsbl%2Fuploads%2Fgit-blob-fb030382876bc63c821c85502c7509ad0d1ac400%2F2abbee1d8362d14a36076f7cb69f3ad58da12896_a6cc6c68de38c4e1.png?alt=media)

1. **데이터 리포트**\
   워크스페이스 내 모든 데이터 리포트를 조회할 수 있습니다.
2. **즐겨찾는 리포트**\
   자주 보는 리포트는 즐겨찾는 리포트로 추가하여 사이드 메뉴에서도 확인할 수 있습니다. (즐겨찾기는 최대 10개까지 추가 가능)
3. **데이터 분석 차트**\
   데이터 분석에서 저장한 모든 차트를 해당 탭에서 확인할 수 있습니다.

![데이터 분석 차트](https://2738466581-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLHRZjjknm5KdNgPtDsbl%2Fuploads%2Fgit-blob-0ceeb1e0677e44f5159c7936151c55a7188972df%2F1e85807dc1d455c5042893d2e13b56fcb9f99fd8_27e04dedfb659614.png?alt=media)


---

# 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://docs.hackle.io/data/data-report.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.
