> For the complete documentation index, see [llms.txt](https://docs.threatdefence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.threatdefence.com/getting-started/frequently-asked-questions/ndrfaq.md).
# NDR (Network Sensor)
## How can I see all NDR alerts?
Many options:
* On the main Security Detections dashboard, under Data Source drop down menu, choose Network Sensor or Network Intrusion;
* OR click on the NDR section in the pie chart:
* Under Main menu/My SOC/Alerts\&Detections/Network Behavior and Network Intrusion dashboards.
## How can I see all network traffic events (not alerts)
Under main menu/Network. Network traffic flows contains all traffic metadata for full assurance, so breaches will be recorded even if not detected and includes all business traffic. The other dashboards contain data for individual traffic types:
## How to inspect incoming traffic only?
In the top right corner, click on inbound to see all inbound traffic:
## How to see all anomalies and attacks?
Under main menu/Network/network Intrusion Detection, All network Intrusion Events. This module only records suspicious activity. To see all attacks from the outside, click on inbound under the Network Direction pie chart. To see what ports/services attract hackers, refer to the Destination Ports table that lists the count of unique incoming source IP's.
---
# 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.threatdefence.com/getting-started/frequently-asked-questions/ndrfaq.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.
