> For the complete documentation index, see [llms.txt](https://docs.eseye.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eseye.com/infinity-classic/manage-your-sim-estate/sim-actions/view-netflow-activity.md).

# View NetFlow activity

To display the NetFlow activity for a SIM, on the SIM List page menu, select ![](https://3470471310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2pbiEZepRfUhnzoMb7nU%2Fuploads%2FRbb9iYCEnAMfzvYxIVBo%2Finfinityclassic-0073-SimActionIconNetflow_24x24.png?alt=media) next to the chosen SIM. NetFlow data enables you to track traffic flow and volume per SIM, and outputs Mobile Terminated (MT) and Mobile Originated (MO) data in a graph that you can drill into.

The NetFlow dialog displays a graphical breakdown of data transmission over time. The blue bars are MT (received), and the black bars are MO (sent) data transmissions. The default view displays an entire month of data, with each bar representing one day. You can change the current data window using the arrows above the graph.

![](https://3470471310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2pbiEZepRfUhnzoMb7nU%2Fuploads%2FmYDdVHhMDs5PNdd5iwaH%2Finfinityclassic-218-SIMNetflowActivity_thumb_400_400.png?alt=media)

Selecting one bar will update to show a new graph with one bar representing an hour and the whole graph covering a day. Selecting an hour bar will update to show a new graph, with one bar representing a minute and the whole graph covering an hour.

If you would like to receive NetFlow data in greater detail, speak to your Account Manager about the Push API. For more information, see [Monitoring and administering network usage](/anynet-sim/connectivity/monitoring-and-diagnostics/monitoring-and-administering-network-usage.md).

### Results table

The table below the graph provides a breakdown of the data in the graph in tabular form.

![](https://3470471310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2pbiEZepRfUhnzoMb7nU%2Fuploads%2FhtBIu239ZGErjeMGdZzQ%2Finfinityclassic-220-NetFlowActivityTable_thumb_400_400.png?alt=media)

To scroll through all of the pages, use the numbers above the table.

The following table describes the fields represented in the table and graph.

| Field                  | Description                                                                          |
| ---------------------- | ------------------------------------------------------------------------------------ |
| Date (Day/Hour/Minute) | Displays the day, hour or minute representing one of the bars on the bar chart.      |
| MO Bytes               | The data usage for mobile originated data for the SIM over the selected time window. |
| MT Bytes               | The data usage for mobile terminated data for the SIM over the selected time window. |
| Total Bytes            | The total data usage across all bars on the chart.                                   |

## Related tasks

Back to overview


---

# 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.eseye.com/infinity-classic/manage-your-sim-estate/sim-actions/view-netflow-activity.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.