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

# Read activity, consumption and workload

> Distinguish API traffic, product charges and processing workload, and export the right records for your task.

**Reporting** separates operational activity from billing. Use the view that answers your question instead of treating request volume, processing counts and product consumption as interchangeable.

## Choose the right report

| View | Use it for |
| - | - |
| **Reporting** | API traffic, errors and response times by endpoint or key. |
| **Consumption** | Insights and Signal quantities and historical charges. Owner access is required. |
| **Workload** | Processing counts and agreed workload limits, separate from charges. |
| **Reports & exports** | Available published reports and export records. |

Confirm the workspace, environment and reporting period. Filters on one view do not change the meaning or time window of a different report.

## Review consumption

Open **Consumption** and inspect the product, subject, quantity, amount and period. Select a row to inspect its detail and related identifiers.

![Consumption table showing usage records, subjects, products, quantities, CAD amounts and periods.](https://mintcdn.com/amlok-docs/HXjKmnxFg9L3P2cw/images/console/consumption.jpg?fit=max\&auto=format\&n=HXjKmnxFg9L3P2cw\&q=85\&s=754969f660ab292784faeedb1dee6c6e)

Consumption records describe product usage and charges. They are separate from raw API traffic.

Insights quantities represent completed underwritings. Signal quantities represent active subject-months under the billing contract. API calls and workload counts are not additional financial units. Use the recorded historical amount and billing context rather than recalculating an old charge from today's price.

To reconcile money, compare these records with **Billing**, **Funding history** and **Statements**. See the [billing guide](https://docs.amlok.io/console/billing.md).

## Investigate operational changes

If errors or response time increase, narrow the time range and endpoint, then open [request logs](https://docs.amlok.io/console/request-logs.md) for specific examples. If processing counts approach an agreed workload limit, review **Workload** and the applicable API capacity information.

Check the denominator and period before comparing charts. A count of requests includes different operations from a count of completed underwritings; a processing failure may appear in operational activity without becoming a completed billable underwriting.

## Export records

The table's **Export** action downloads the filtered records currently available to that console collection. It is useful for a focused review, but is not a guarantee that you have exported every record in a large workspace.

For complete programmatic retrieval, use the [large-results workflow](https://docs.amlok.io/api-reference/large-results.md), pagination or the appropriate API export. In **Reports & exports**, open a record to inspect its status and available artifact information. An export that is still processing is not ready for download, and an expired download link must be refreshed through the documented flow.

Respect the selected workspace, environment and your authorization when sharing exported data. Use [enterprise operation](https://docs.amlok.io/api-reference/enterprise-operation.md) and [workload reporting](https://docs.amlok.io/api-reference/workload-reporting.md) for automated collection at volume.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.