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
forward destinations over time #21
Comments
How do you think that this should be resolved? As you say
and the specific reason is that nothing has been forwarded - so what should be displayed? Even if there have been some queries in this time frame, they must have all been answered from the cache. An option might be to add a third forward destination which is the local cache. But then, "forward destination" doesn't seem to be the correct wording anymore. Also, this would still lead to empty slots if there are zero queries in that time - as in no other service is running on the Pi-hole and all clients are shut down, so there is really nobody asking anything. |
Hi, |
The debug token will not help here since it does not contain any historic data of your log (only what you browsed during it saying that it is recording). I frankensteined together a synthetic log for tonight on my Pi-hole that is supposed to show the same behavior: lots of activity, but then one 10 minutes interval that only contains one forwarded query. I don't see a hole in this situation. If, however, the single query has been blocked which is the same as if it would have been answered from the local cache - there is the hole you are describing. Next, I removed an entire hour from my log (02:00 - 03:00), leaving only one query at 02:59: And then removed even this one: Can you send me the output of maybe through a PastBin? |
Hi, I will try to send the output via PM... |
this might be getting too complex but would it be a possibility to have the forward destination also check the status IE whether it was piholed or not and have that separated into two categories ? as i understand the status returns there was one for successful vs blocked. seems like it might be do able to me |
@technicalpyro Yes, that is in principle doable, but I don't really like it. It somewhat spoils the idea of presenting it as a forward destination if we separate between allowed and blocked cache answers... |
i guess the followup would then be since it is possible to separate them could they just be removed from the graph in the local portion ? |
If I remove the blocked ones then we will again have the situation with holes as there have been queries in the time frame in question but no forward destination was responsible for serving them (not even local since we artificially removed that). |
ahhh yes yes sorry still waking up over here |
No worries. I've just finished with work and go home now. I'll release the update of |
|
Fix deadlock caused by concurrent FTL API accesses
In raising this issue, I confirm the following (please check boxes, eg [X]) Failure to fill the template will close your issue:
How familiar are you with the codebase?:
1
[BUG | ISSUE] Expected Behaviour:
forward destination graphic should display all logs
http://fs5.directupload.net/images/170418/4853ocop.png
[BUG | ISSUE] Actual Behaviour:
sometimes gaps are appearing in the graphic, but pi-hole and query logging are working normal
[BUG | ISSUE] Steps to reproduce:
it appears sometimes when not so many querys have to be logged
Log file output [if available]
output
Device specifics
Hardware Type: rPi, VPS, etc
OS:
This template was created based on the work of
udemy-dl
.The text was updated successfully, but these errors were encountered: