[syslog-ng] Syslog-ng 2.0rc3 duplicate stats counter bug

[Evan Rempel]

Balazs Scheidler wrote:
> On Thu, 2006-10-05 at 13:43 -0700, Evan Rempel wrote:
> 
>>I was doing this on AIX 5.2
>>
>>
>>If I have multiple destination defined to the same destination
>>(because I want different formats) I get the
>>Duplicate stats counter; counter='udp(AF_INET(xxx))'
>>Duplicate stats counter; counter='udp(AF_INET(xxx))'
>>Duplicate stats counter; counter='udp(AF_INET(xxx))'
>>Duplicate stats counter; counter='udp(AF_INET(xxx))'
>>Duplicate stats counter; counter='udp(AF_INET(xxx))'
>>Duplicate stats counter; counter='udp(AF_INET(xxx))'
>>Duplicate stats counter; counter='udp(AF_INET(xxx))'
>>Duplicate stats counter; counter='udp(AF_INET(xxx))'
>>
>>This destination host had 9 coresponding "destination" and "log" configurations.
> 
> 
> Hmm.. each destination has a generated name, which is supposed to be
> unique, and that does not include the template string. Is it a problem
> if processed/dropped counters are shared between these writers?
> 

For statistics, I don't have any problem that the same counter is used. 
Currently, I get a single element dropped statistic for the protocal/IP 
pair, which in my opinion is goo since it is a single communications 
channel, and is sufficient for trouble shooting and auditing. Example:

Log statistics;
dropped='tcp(AF_INET(142.104.5.206:514))=0',
dropped='udp(AF_INET(142.104.5.76:514))=0',
processed='center(queued)=393', processed='center(received)=131',
processed='destination(syslogServer1.local2.debug)=0',
processed='destination(syslogServer1.local2.notice)=0',
processed='destination(syslogServer1.local2.crit)=0',
processed='destination(syslogServer1.local2.err)=0',
processed='destination(syslogServer2)=131',
processed='destination(syslogServer1.local2.alert)=0',
processed='destination(syslogServer1)=131',
processed='destination(syslog)=131',
processed='destination(syslogServer1.local2.info)=0',
processed='destination(syslogServer1.local2.emerg)=0',
processed='destination(syslogServer1.local2.warning)=0',
processed='source(local)=131'


If everything is working as designed, and correctly, I would NOT expect 
to get the messages about Duplicate stats counters which imply that 
there is some kind of problem. Perhaps those messages could be removed.

Evan.