[pmacct-discussion] MySQL Timezone handling

2016-05-30 Thread Vaggelis Koutroumpas
Hello, I am using nfacct to process flows from our routers and store them in a mysql database for processing and visualization. I have a 'daily' table for storing the daily traffic for each IP. I've set sql_history to 1d to store one record per day per IP. This worked fine for months. Each

Re: [pmacct-discussion] MySQL Timezone handling

2016-05-30 Thread Will Dowling
> I look forward to any thoughts about data types. Personally, the very > first reaction this trigger is: the backend of the accounting system > should be set to a timezone that does not change during the year and, > even more ideally, to UTC. UTC is ideal because it helps when stuff is > spanning

Re: [pmacct-discussion] MySQL Timezone handling

2016-05-30 Thread Paolo Lucente
Hi Vaggelis, I look forward to any thoughts about data types. Personally, the very first reaction this trigger is: the backend of the accounting system should be set to a timezone that does not change during the year and, even more ideally, to UTC. UTC is ideal because it helps when stuff is