This is a documented feature of syslog-ng; I am not aware of any reason why this would be considered a bad idea. Please see https://syslog-ng.gitbooks.io/getting-started/content/chapters/chapter_5/section_2.html for more information. 

Additionally, TextLogDestination and StructuredLogDestination are Java classes provided by syslog-ng in the syslog-ng-core.jar.
 
On Thu, Feb 20, 2020 at 01:55:33AM +0000, Jamal Habash wrote:
> Hey All,
>
> I am interested in developing a Java destination for syslog-ng. I have read the documentation which states "To interface with syslog-ng, you will need to extend the TextLogDestination or StructuredLogDestination".
>


that sounds like a really bad idea


> There is no documentation or code comments for either of these classes.
>
> 1) What is the intended use-case for TextLogDestination?
> 2) What is the intended use-case for StructuredLogDestination?
>
> Additionally, as there are no comments in the code, it is unclear what the abstract methods in these classes are meant to do. For example, each class has the same abstract methods called open(), close(), isOpened(), getNameUniqOptions().
>
> 3) What is the purpose of these methods?
> 4) When will they be invoked by syslog-ng?


It seems to me it is written in C..

am I wrong here?

>
> It is difficult to write a valid implementation without knowing the purpose of each method. Is there any documentation for this?
>
> Thanks in advance!
>
> J