> For the complete documentation index, see [llms.txt](https://docs.fusion.vectra.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fusion.vectra.ai/netodns/reading-statistics-from-netodns-api.md).

# Reading statistics from NetoDNS API

## About the NetoDNS API

The NetoDNS API is a very simple API endpoint that provides client-side statistics from a running NetoDNS instance. By default, the API listens on TCP port 8080. The API is unauthenticated and read-only. For a production deployment, access to the API port on NetoDNS should be restricted by network access, or the API should be disabled if it is not needed.

Per-device statistics are calculated pre-filter and pre-downsample.

### Configuring the NetoDNS API

#### environment variable configuration settings

```
NETO_API__ENABLED=true  
NETO_API__PORT=8080  
```

For more details on how to modify the configuration of NetoDNS, see see: [Install NetoDNS (container)](/netodns/install-netodns-container.md) or [Install NetoDNS (Linux package)](/netodns/install-netodns-linux-package.md)

##

### Reading statistics with the NetoDNS API

Read statistics from port 8080 on the NetoDNS host using this endpoint: `/api/v1/stats/rate`

On your local system: `http://localhost:8080/api/v1/stats/rate`

If you cannot access this port when NetoDNS is running, ensure you do not have a local firewall in place that is blocking the port, you have mapped the container port 8080 to a local port if you are using the NetoDNS container, and you have not disabled or changed the port in the NetoDNS configuration.

#### Using `curl` to read statistics from NetoDNS running on localhost

`curl localhost:8080/api/v1/stats/rate`


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.fusion.vectra.ai/netodns/reading-statistics-from-netodns-api.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.