> 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/creating-investigations.md).
# 調査の作成
[調査の作成](/platform/ja/user-guide/investigations/getting-started-with-investigations.md#creating-investigations)を行った後、調査ページの左上にあるトグルを使用して**ビジュアルエディタ**と**NQLエディタ**の間を切り替えて、調査クエリを構築してください。
* [ビジュアルエディタ](/platform/ja/user-guide/investigations/creating-investigations/visual-editor.md)を選択して、調査クエリを構築するためのグラフィカルツールを使用します。
* [NQLエディタ](/platform/ja/user-guide/investigations/creating-investigations/nql-editor.md)を選択して、[Nexthink Query Language (NQL)](https://docs.nexthink.com/platform/ja/user-guide/nexthink-query-language-nql)で調査クエリを記述します。
あるいは、[Nexthink Assist](https://docs.nexthink.com/platform/ja/user-guide/search-and-nexthink-assist/using-nexthink-assist#query-data-with-assist)のサポートを受けて、**ビジュアルエディタ**やNQLの事前知識なしに調査クエリを構築することも可能です。
{% hint style="info" %}
事前に定義された調査を含む[Nexthink Library Investigations starter](https://docs.nexthink.com/platform/ja/library-packs/it-operations/investigations-starter-pack)パックをインストールすると、NQLクエリを手動で記述したり、Nexthink AssistまたはVisualエディタを使用してデータをクエリすることなく、一般的な問題に関する洞察を迅速に得ることができます。
{% 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://docs.nexthink.com/platform/ja/user-guide/investigations/creating-investigations.md?ask=&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.
