The article mentioned a Mout'z Soudani, but went into no further detail. This article has a little more context on the investigation into Orange County and the bribery scheme.
Martin Soudani was charged and pleaded guilty last year to an alleged $1.6 million cryptocurrency scheme that was investigated by then Executive Assistant District Attorney Stewart Rosenwasser.
™The former prosecutor and retired Orange County Court Judge is accused of knowing the alleged victim, Moutz “Marty” Soudani, the suspect’s uncle, and taking almost $50,000 from him to investigate the case.
I am really not sure how I feel about this. It feels like when Cisco Systems bought Kalpana back in '94 and brought us the Catalyst 3000. So sexy, much disaster. Very bugs.
I really wanted to like that switch. It got better, but so did I.
Where was I?
Oh right: Qualcomm buying Intel. That's not gonna help anything or anyone. Bad idea.
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.
#### 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