> 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/understanding-key-data-platform-concepts/nexthink-query-language-nql/nql-functions/nql-count.md).
# NQL count()
`count()` 関数はユニークなオブジェクトや特定のイベントの数を返します。
## ‘compute’句を使用する
### オブジェクトの場合:
ユニークなオブジェクトの数を返します。
{% code overflow="wrap" lineNumbers="true" %}
```
devices during past 7d
| include execution.events during past 7d
| compute number_of_devices = device.count()
```
{% endcode %}
### 特定のイベントの場合:
オブジェクトごとのイベント数を計算します。
{% code overflow="wrap" lineNumbers="true" %}
```
devices during past 7d
| include execution.crashes during past 7d
| compute number_of_crashes_ = count()
```
{% endcode %}
### サンプリングしたイベントの場合:
サンプリングされたイベントに`count()`関数を使用することは推奨されません。なぜなら実際のイベント数ではなくデータサンプルの数を返すからです。
## ‘summarize’句を使用する
`summarize`句とともに使用されると、`count()` 関数は常にルートテーブル内のレコード数を返します。
### オブジェクトの場合:
オブジェクトの数を返します。
{% code overflow="wrap" lineNumbers="true" %}
```
devices during past 7d
| summarize c1 = count()
```
{% endcode %}
### 特定のイベントの場合:
イベントの数を返します。
{% code overflow="wrap" lineNumbers="true" %}
```
execution.crashes during past 7d
| summarize c1 = number_of_crashes.count()
```
{% endcode %}
以下のクエリはルートテーブル（この場合、デバイス）のレコードの数を返します。ユニークなイベントの数ではありません。イベントを数えるには、代わりに‘summarize’句の中で`sum()`関数を使用してください。
{% code overflow="wrap" lineNumbers="true" %}
```
devices during past 7d
| include execution.crashes during past 7d
| compute number_of_crashes_ = number_of_crashes.count()
| summarize c1 = number_of_crashes_.count()
```
{% endcode %}
### サンプリングしたイベントの場合:
サンプリングされたイベントに`count()`関数を使用することは推奨されません。なぜなら実際のイベント数ではなくデータサンプルの数を返すからです。
---
# 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/understanding-key-data-platform-concepts/nexthink-query-language-nql/nql-functions/nql-count.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.