[ 
https://issues.apache.org/jira/browse/LOG4J2-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17600653#comment-17600653
 ] 

Deepak Pareek commented on LOG4J2-3586:
---------------------------------------

Hi [~rgoers] ,
To be specific, currently in our project we are using customised appender with 
log4j.1.X, wherein we are sending few parameters from log4j.xml, which is used 
for creating the logs.
Example : 
<param name="appName" value="Tomcat"/>
<param name="gridNames" value="Cuca"/>

Now we want to migrate from log4j1x to log4j2, if any customised appender is 
created using log4j2 (by making it as a plugin). Is there any way to send PARAM 
with this customised plugin in log4j2.xml?

Thank You.

> AppenderSkeleton substitute in Log4j2.17.
> -----------------------------------------
>
>                 Key: LOG4J2-3586
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3586
>             Project: Log4j 2
>          Issue Type: Question
>          Components: Appenders
>    Affects Versions: 2.17.2
>            Reporter: Deepak Pareek
>            Priority: Major
>              Labels: features
>
> Hello Team,
> We are using log4j 1.x in our project, it has custom appender for logging 
> which leverages org.apache.log4j.AppenderSkeleton.
> It uses Grid name and App name mapping for dumping app specific logs.
> We have to upgrade log4j version to Log4j2. Hence we are looking for 
> AppenderSkeleton substitute, which uses the same underlying architecture. We 
> have already explored the available customized appender options [using 
> @Plugin], but that is not feasible for us as our core framework is designed 
> in such a way that we need to provide App name and Grid name in log4j.xml 
> itself.
> So to summarize we are looking forward for help on below points : 
> 1. Is there any way to add app name and grid name in Log4j2.xml ? 
> 2. Is the any AppenderSkeleton substitute, which uses the same underlying 
> architecture ?
> Any help on the above mentioned points will be highly appreciated.
>  
> Thanks,
> Deepak Pareek



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to