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

AdguardHome DNS Graphs Blank #211

Closed
samcro1967 opened this issue Sep 8, 2024 · 5 comments
Closed

AdguardHome DNS Graphs Blank #211

samcro1967 opened this issue Sep 8, 2024 · 5 comments

Comments

@samcro1967
Copy link

The DNS widget seems to be connected to both my AdguardHome servers and is retuning some data, but the graphs are blank. It has been running for several hours now. Not sure if it just needs to run longer, I am missing something, or I have done something wrong.

glance DNS Widgets for 2 AdguardHome servers
image

AdguardHome Stastics from 1 of the servers
image

Relevant glance.yml config

  - name: Monitoring
    columns:
      - size: full
        widgets:
          - type: dns-stats
            title: server1
            service: adguard
            url: http://192.168.1.106:8126/
            username: <redacted>
            password: <redacted>
      - size: full
        widgets:
          - type: dns-stats
            service: adguard
            title: server2
            url: http://192.168.1.108:8126/
            username: <redacted>
            password: <redacted>
@svilenmarkov
Copy link
Member

Thanks for reporting this!

I think I know what the issue is. I naively assumed that AdGuard always returns data for the last 24 hours since that's what Pi-hole does, but I had just coincidentally set my statistics retention to 24 hours. Could you please confirm that your statistics retention is set to more than 24 hours if you go to Settings -> Statistics configuration?

@samcro1967
Copy link
Author

It is set to 90 days:
image

@svilenmarkov
Copy link
Member

Thanks for confirming, I'll get it sorted out soon.

@svilenmarkov
Copy link
Member

I've just released v0.6.1 which should fix this.

@samcro1967
Copy link
Author

Can confirm it is now working.
image

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