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

Clients (over time) should be hidden when privacy level 3 or higher is enabled. #932

Closed
3 tasks done
mwoolweaver opened this issue Apr 17, 2019 · 16 comments
Closed
3 tasks done

Comments

@mwoolweaver
Copy link

mwoolweaver commented Apr 17, 2019

In raising this issue, I confirm the following: {please fill the checkboxes, e.g: [X]}

How familiar are you with the the source code relevant to this issue?:

{ 1 }


Expected behaviour:

when enabling privacy level 3 it states:
" Hide domains and clients: Display and store all domains as "hidden" and all clients as "0.0.0.0" This disables all tables on the dashboard "
So one would assume since the graph isn't populated with any stats it wouldn't be shown.

more details on expected behavior:

i would think that when the privacy level has been enabled for any level higher than level 2 this graph should not be shown as there is no information shown in it.

Privacy Level 3 - 5 this graph should be off.

Actual behaviour:

{ Clients (over time) is shown as an empty graph when privacy level 3 or higher is enabled. }

Steps to reproduce:

{ Enable privacy level 3 and view the dashboard when logged in. }

Debug token provided by uploading pihole -d log:

{ https://tricorder.pi-hole.net/v96pimhd8r! }

Troubleshooting undertaken, and/or other relevant information:

{ Not sure how to. }

@mwoolweaver mwoolweaver changed the title Clients (over time) should be hidden when privacy level 3 is enabled. Clients (over time) should be hidden when privacy level 3 or higher is enabled. Apr 17, 2019
@AzureMarker
Copy link
Contributor

Have you tested enabling level 3 and waiting for a few hours? The clients in the graph would then show as 0.0.0.0 starting from the moment you changed the privacy level. Previous queries are not retroactively changed.

@mwoolweaver
Copy link
Author

mwoolweaver commented Apr 23, 2019

will investigate. probably not a bug. will leave on for a few hours

@mwoolweaver
Copy link
Author

pi-hole has been running for a couple hours and chart has yet to show any data at all.

@AzureMarker
Copy link
Contributor

Closing the issue as there seems to be no bug.

@mwoolweaver
Copy link
Author

mwoolweaver commented Apr 23, 2019

The clients in the graph would then show as 0.0.0.0 starting from the moment you changed the privacy level.

this is not what's happening in my case. If you'd like I'd be willing to share a little more info via email so you can see this.

pi-hole has been running for well over 12 hrs and the graph shows no data at all.

@AzureMarker
Copy link
Contributor

It may be that the 0.0.0.0 clients are not shown in the graph. I will test this tonight. You can share info with mark@pi-hole.net if you would like.

@AzureMarker
Copy link
Contributor

I closed this as we are correctly not showing new client information after changing the privacy level, however I see now that you are trying to get at a different point. You want to remove the graph when there is no information to be shown. That borders on a feature request (hide charts when they do not have data), but I will keep it as an issue for now, just note that it is not a bug as this is expected behavior.

@mwoolweaver
Copy link
Author

So if understand correctly.

When clients are being shown as 0.0.0.0 the Clients (over time) graph is supposed to be empty by design?

@AzureMarker
Copy link
Contributor

Yes, you can see here that no client over time information is sent if the privacy level is 3 or higher:
https://github.com/pi-hole/FTL/blob/master/api.c#L1018

I was traveling and unable to test this until now, so sorry for any confusion.

@mwoolweaver
Copy link
Author

That's good to know! I have resorted to using uBlock to just hide it for the time being.

So what the reason for it still being shown if it's not being populated with any data?

@AzureMarker
Copy link
Contributor

No particular reason, that is just how it worked out when we added the privacy levels.

We are working on a new web interface to replace this one, and so we are trying to avoid any unnecessary changes to this web interface. Changes made to this interface will either need to be rewritten for the new web interface, or lost. I can change the new web interface to hide the charts based on privacy level, which is the best way to implement this feature. However, it will take time for that to happen, as actually shipping the new web interface has higher priority than this feature.

Preview: http://web.pi-hole.io/
Repo: https://github.com/pi-hole/web

@mwoolweaver
Copy link
Author

as actually shipping the new web interface has higher priority than this feature.

TFW I forgot this was coming . . .

Is there a way to use it with live data?

@AzureMarker
Copy link
Contributor

There is a draft PR which has some instructions for testing the API and new web interface. Note that it is still in a alpha or even pre-alpha stage: pi-hole/pi-hole#2692

DL6ER added a commit that referenced this issue Jun 15, 2019
… data for the graph so we can hide it. Fixes #932

Signed-off-by: DL6ER <dl6er@dl6er.de>
@DL6ER DL6ER added the Bug label Jun 15, 2019
@DL6ER
Copy link
Member

DL6ER commented Jun 15, 2019

Sorry for the delay, I just discovered this issue ticket. The function @mwoolweaver asks for is already there, however, a bug prevents it from working as expected. This will be fixed by #966.

@mwoolweaver
Copy link
Author

has the release for this fix been released yet?

@AzureMarker
Copy link
Contributor

No, it will be released with v5.0.

AzureMarker pushed a commit that referenced this issue Sep 11, 2019
… data for the graph so we can hide it. Fixes #932

Signed-off-by: DL6ER <dl6er@dl6er.de>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants