> ## Documentation Index
> Fetch the complete documentation index at: https://docs.apinizer.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Clients Not Making Requests

> You can detect users who do not make requests or make few requests in a specific date range in Apinizer. You can perform passive client analysis by filtering according to minimum-maximum record counts and analyze user activity metrics.

<Warning>
  The maximum number of records this report can return is 512.
</Warning>

<img src="https://mintcdn.com/apinizer/QnlawYOmsE7aqwqT/images/yonetici/istek3.png?fit=max&auto=format&n=QnlawYOmsE7aqwqT&q=85&s=420b40851472dc49a3155fa116087c1f" alt="Clients Not Making Requests" width="1000" height="800" style={{ borderRadius: '0.5rem' }} data-path="images/yonetici/istek3.png" />

<Info>
  Since an API Proxy can be loaded into multiple environments, metrics must also be evaluated according to the environment it is loaded into. Therefore, in all analytics screens, metrics are filtered by first selecting environment information.
</Info>

## Filters

This report allows you to detect users who do not make requests or make few requests based on specific criteria. You can configure the filters by following the steps below:

<Steps>
  <Step title="Environment Selection">
    You must first select an environment to run the report. Environment selection is mandatory and metrics are filtered according to the selected environment.

    <Info>
      Since an API Proxy can be loaded into multiple environments, metrics must also be evaluated according to the environment it is loaded into.
    </Info>
  </Step>

  <Step title="Project Selection (Admin)">
    Multiple project selection is available for administrator users. When a project is selected, users in the selected projects are analyzed.

    <Note>
      This filter is only visible for administrator users.
    </Note>
  </Step>

  <Step title="User Selection">
    You can specify the users to be analyzed by making multiple selections. If no selection is made, all users are analyzed.
  </Step>

  <Step title="Status Filter">
    You can filter by the status of users:

    * **All**: Users in all statuses
    * **Active (ACTIVE)**: Users in active status
    * **Inactive (INACTIVE)**: Users in inactive status
  </Step>

  <Step title="Minimum Usage Count Threshold">
    You can define a minimum usage count threshold to determine the usage status of users. Users who make requests below the specified value are listed.

    This threshold allows you to detect users who are completely passive or make very few requests.
  </Step>

  <Step title="Maximum Usage Count Threshold">
    You can define a maximum usage count threshold to determine the usage status of users. Users who make requests above the specified value are listed.

    This threshold allows you to detect users within a specific usage range.
  </Step>

  <Step title="Date Range Selection">
    You can select the date range to be analyzed. When a date range is selected, only requests within this range are analyzed.
  </Step>
</Steps>

## Report Table

Report results are displayed in the following columns:

| Field                                       | Description                                                                              |
| ------------------------------------------- | ---------------------------------------------------------------------------------------- |
| Project (*Project*) (Admin)                 | The name of the project to which the user belongs (only visible for administrator users) |
| Client Organization (*Client Organization*) | The name of the organization to which the user belongs                                   |
| Client Username (*Client Username*)         | Username                                                                                 |
| Successful (*Successful*)                   | The number of requests that completed successfully                                       |
| Blocked (*Blocked*)                         | The number of requests blocked due to security policies or rate limiting                 |
| Error (*Error*)                             | The number of requests that resulted in an error                                         |
| Total (*Total*)                             | Total number of requests (successful + blocked + error)                                  |

<Note>
  The report cannot be run for environments where Elasticsearch integration is not active. In this case, a warning message is displayed on the screen.
</Note>