On Thu, 14 Mar 2013, Rainer Gerhards wrote:
Why re-implementing a translation module doing the same directly in
Rsyslog, as it is handled by PostgreSQL?
Well, obviously this is just a pg solution, so in long term, doing it
generally would make sense IMHO.
Well, the databases engines rsyslog is able to work with until now (MySQL,
PostgreSQL, Oracle) all allow the definition of the character set.
In Postgresql this is SET client_encoding='value';
In MySQL this is SET NAMES 'value' which combine in itself 3 other MySQL
instructions that are
SET character_set_client = 'value'; SET character_set_results = /'value'/; SET
character_set_connection = /'value'/;
The SET NAMES syntax is SQL92 standard.
In Oracle, I may be wrong, but it should be SET NLS_LANG='value'
So generally, any database should have this instruction available in a way or
another.
That's good to know, but still limits it to databases. A very important
use-case IMHO is relaying, to solve exactly the problem you mentioned
that a single sender sends in multiple character sets.
The other problem is that different sources may use different encoding, so if
you try to define the encoding at output time, you may not know which one to
use.
If rsyslog has the ability to fix it earlier in the path, then you can fix just
the logs that are 'wrong'.
David Lang
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
