> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/platform/ja/user-guide/investigations.md).

# Investigations

Investigations では、従業員のデジタル Experience に関するインサイトを取得し、特定の技術メトリックを確認できます。

Investigations に関するドキュメントは以下をご覧ください。

* [Investigations を使い始める](https://docs.nexthink.com/platform/ja/user-guide/investigations/getting-started-with-investigations.md)
* [ビジュアルエディター](https://docs.nexthink.com/platform/ja/user-guide/investigations/creating-investigations/visual-editor.md)
* [NQL エディター](https://docs.nexthink.com/platform/ja/user-guide/investigations/creating-investigations/nql-editor.md)
* [Investigations の分析](https://docs.nexthink.com/platform/ja/user-guide/investigations/analyzing-investigations.md)
* [Investigations の管理](https://docs.nexthink.com/platform/ja/user-guide/investigations/managing-investigations.md)
* [Investigations の NQL の例](https://docs.nexthink.com/platform/ja/user-guide/investigations/investigations-nql-examples.md)
* [Finder (クラシック) での Investigation の作成](https://docs.nexthink.com/platform/ja/user-guide/investigations/creating-an-investigation-with-finder-classic.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://docs.nexthink.com/platform/ja/user-guide/investigations.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.
