I just checked and he still says 'we' didn't start the fire. Emphatically, in fact. Several times, even.
Seems that yep, this is all that Trump fella's fault.
solidgrue
joined 1 year ago
My next mower will probably be a lawn service
When you're angling to be a minion of Cruz, its the epitome of aspiring to sub-mediocrity.
Who's fully mediocre? I dunno... At random, Jack Reed maybe?
I didn't so much forget it as I did assume Texans were just playing the martyr for getting their collective asses kicked in. Again.
You know... Like Dallas Cowboys fans?
No worries, the other poster was just wasn't being helpful. And/or doesn't understand statistics & databases, but I don't care to speculate on that or to waste more of my time on them.
The setting above maxes out at 24h in stock builds, but can be extended beyond that if you are willing to recompile the FTL database with different parameters to allow for a deeper look back window for your query log. Even at that point, a second database setting farther down that page sets the max age of all query logs to 1y, so at best you'd get a running tally of up to a year. This would probably at the expense of performance for dashboard page loads since the number is probably computed at page load. The live DB call is intended for relatively short windows vs database lifetime.
If you want an all-time count, you'll have to track it off box because FTL doesn't provide an all-time metric, or deep enough data persistence. I was just offering up a methodology that could be an interesting and beneficial project for others with similar needs.
Hey, this was fun. See you around.
If you're wrong then I don't wanna be right.
You know what? I'm gonna disengage here. You're not hearing what I am saying.
#### MAXLOGAGE=24.0
Up to how many hours of queries should be imported from the database and logs? Values greater than the hard-coded maximum of 24h need a locally compiled `FTL` with a changed compile-time value.
I assume this is the setting you are suggesting can extend the query count period. It still will only give you the last N hours' worth of queries, which is not what OP asked. I gather OP wants to see the cumulative total of blocked queries over all time, and I doubt the FTL database tracks the data in a usable way to arrive at that number.
Ah, well if you know differently then please do share with the rest of us? I think the phrasing in my post makes it pretty clear I was open to being corrected.
So, like a running sum? No, I don't think so, not in Pi-hole at least.
Pi-hole does have an API you could scrape, though. A Prometheus stack could track it and present a dashboard that shows the summation you want. There are other stats you could pull as well. This is a quick sample of what my home assistant integration sees
That counter, I believe, for the last 24 hours. It will fluctuate up and down across your active daily periods
Pretty sure we had the E9112 and E9116 back in the day. Now I have a legit B92FS but it doesn't squirt water. For work reasons.
Ah, nostalgia. (Don't play with guns!)
383
I'd imagine they fake an American accent. Maybe Burbank, CA?
view more: next ›
Ironic, isn't it?