From: Bob Brewer <ipfire-devel@grantura.co.uk>
To: development@lists.ipfire.org
Subject: RE: Peeking at unbound statistics from WUI
Date: Mon, 21 Jan 2019 10:28:44 +0000 [thread overview]
Message-ID: <q246ss$387$1@tuscan3.grantura.co.uk> (raw)
In-Reply-To: =?utf-8?q?=3CAM0PR03MB4932BA80DE9C25FB099EDAC2B69E0=40AM0PR03MB?= =?utf-8?q?4932=2Eeurprd03=2Eprod=2Eoutlook=2Ecom=3E?=
[-- Attachment #1: Type: text/plain, Size: 1809 bytes --]
Rachid Groeneveld wrote:
> I've been looking at PiHole and Firewalla and I like how those dashboards
> are pleasing to the eye and wanted to achieve the same within IPFire. I
> think it's quite possible and IPFire hosts way more functionality, so why
> not the fancy dashboard? With that in mind I looked for info on the themes
> in IPF, I found that someone - a few years ago - already created an admin
> dashboard, but I never received responses to my communication attempts. So
> I thought, what the heck, I'll just create the dashboard myself, but in
> order to actually - have a dashboard - I need metrics. PiHole has an FTL
> implementation which includes (parts of) Unbound and they're able to show
> quite a bit of interesting information (see attachment, apologies for the
> size I had to google it). Firewalla has the same, but is more tailored to
> SOHO and is managed through an app.
>
>
>
> TLDR; I want the dashboard to show metrics you can work with, like PiHole
> does. The whole controlling DNS and traffic part is not yet part of the
> scope. I already queried the network info (I used parts of other cgi's),
> DNS is the next step and then firewall stats (blocked/dropped, maybe per
> country etc.)
>
Looking at what you are trying to do, I think you need at least 2 programs.
The first would gather your time series data and save this to a file or an
RRD or similar and would be updated from cron. This would allow root to run
“unbound-control stats_noreset" but the data would be accessible to user
nobody.
A second perl cgi program would then read the time series data and display
it through the IPFire web interface.
For inspiration have a look at my adslmonitor addon for IPCop which does
something similar.
https://sourceforge.net/projects/adslmonitor/
Rob
next reply other threads:[~2019-01-21 10:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 10:28 Bob Brewer [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-22 14:16 Michael Tremer
2019-01-21 11:02 Michael Tremer
2019-01-21 11:35 ` Tom Rymes
2019-01-21 11:38 ` Michael Tremer
2019-01-18 15:03 Michael Tremer
2019-01-19 10:44 ` Bob Brewer
2019-01-21 10:51 ` Michael Tremer
2019-01-21 11:50 ` Bob Brewer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='q246ss$387$1@tuscan3.grantura.co.uk' \
--to=ipfire-devel@grantura.co.uk \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox