Hi Paolo,
>> Last question so far: Why am I not seeing data in the database when
>> using "sql_history: 1" (or "10")? I have both "sql_history" and
>> "sql_refresh_time" set to the same amount of seconds.
>
> In super short, you can't set time-bins below 1 minute, anything below
> that will be
Hi Mathias,
Inline:
On Tue, Sep 05, 2017 at 03:05:55PM +0200, Mathias Gumz wrote:
> Exactly that is what I switched to and it does its job. :)
Great :)
> Last question so far: Why am I not seeing data in the database when
> using "sql_history: 1" (or "10")? I have both "sql_history" and
>
Hi Paolo,
> On Tue, Aug 29, 2017 at 05:00:34PM +0200, Mathias Gumz wrote:
>> > Currently I have set the "sql_history" and "sql_refresh_time" to 60s. I
>> > wonder,
>> > how the algorithm works. "sql_refresh_time" seems to scan the cache and, if
>> > needed, writes/updates an entry in the current
Hi Mathias,
Inline:
On Tue, Aug 29, 2017 at 05:00:34PM +0200, Mathias Gumz wrote:
> > Currently I have set the "sql_history" and "sql_refresh_time" to 60s. I
> > wonder,
> > how the algorithm works. "sql_refresh_time" seems to scan the cache and, if
> > needed, writes/updates an entry in the
Hi Mathias,
Can you please post your config? Gut feeling says you may be missing the
sql_history directive (essentially indicate what is the time-binning
period).
Paolo
On Mon, Aug 28, 2017 at 03:36:02PM +0200, Mathias Gumz wrote:
> Hi,
>
> we are using nfacctd to collect NAT events (event