AdguardTeam / AdguardTeam/AdGuardHome
Statistics do not add up or match upstream logs
- Vorherrschende Sprache
- TypeScript
- Sterne
- 36.9k
- Forks
- 2.5k
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
### Prerequisites
- [x] I have checked the [Wiki](https://github.com/AdguardTeam/AdGuardHome/wiki) and [Discussions](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a) and found no answer
- [x] I have searched other issues and found no duplicates
- [x] I want to report a bug and not [ask a question or ask for help](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a)
- [x] I have set up AdGuard Home correctly and [configured clients to use it](https://github.com/AdguardTeam/AdGuardHome/wiki/Clients). (Use the [Discussions](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a) for help with installing and configuring clients.)
### Platform (OS and CPU architecture)
Linux, MIPS64 LE
### Installation
GitHub releases or script from README
### Setup
On a router, DHCP is handled by the router
### AdGuard Home version
v0.108.0-b.62
### Action
- General stats over past 30 days show 2.1M requests.
- Top upstreams are way off and they don't match the stats from the upstreams, e.g. ControlD as reported by AGH shows 162K requests, but looking at the actual ControlD stats on their side, there were 1.4M requests over the past month. This is ~10x difference.
I do have `optimistic caching` and `parallel requests` enabled in AGH, but still the stats for top upstreams are way off and they don't match the actual requests seen by the upstream.
Not sure whether there is a reasonable explanation for this or a bug where it is literally off by a factor of 10?

First 192.168 upstream below is the local LAN DHCP+DNS server that only serves requests for the local LAN domain.

ControlD Stats:

### Expected result
Stats should match (within some small margin of error).
### Actual result
Stats do not match actual requests seen by the upstreams, they are way off by ~10x.
### Additional information and/or screenshots
_No response_
Beitragsleitfaden
Bewertung
Dieses Issue wurde noch nicht bewertet.