Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Statistics do not add up or match upstream logs #7578

Open
4 tasks done
timkgh opened this issue Jan 20, 2025 · 3 comments
Open
4 tasks done

Statistics do not add up or match upstream logs #7578

timkgh opened this issue Jan 20, 2025 · 3 comments

Comments

@timkgh
Copy link

timkgh commented Jan 20, 2025

Prerequisites

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?

Image

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

Image

ControlD Stats:

Image

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

@schzhn
Copy link
Member

schzhn commented Jan 20, 2025

It is most likely due to a combination of caching and the Parallel requests mode.

@timkgh
Copy link
Author

timkgh commented Jan 20, 2025

Alright, I'll turn off parallel requests but I have to leave caching on. Let's see what happens to the stats now.

@timkgh
Copy link
Author

timkgh commented Jan 20, 2025

Even with parallel requests off, the stats are still way off. And it is not that the responses are cached because the requests do make it to the upstreams, I can see them in the upstream logs.

It looks like proper accounting for upstream requests needs some work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants