简体   繁体   English

LOGEVENT记录到WSO2 BAM

[英]LOGEVENT logging to WSO2 BAM

I am trying to use LOGEVENT appender to send ERROR logs to BAM for alerts and notification. 我正在尝试使用LOGEVENT附加程序将错误日志发送到BAM以获得警报和通知。 LOGEVENT is configured in log4j.properties. LOGEVENT在log4j.properties中配置。 However, I am facing 2 issues - a. 但是,我面临两个问题-a。 Stream name is generated with following convention : _ eg log_0_ESB_2014_09_29 b. 流名称是按照以下约定生成的:_例如log_0_ESB_2014_09_29 b。 IP address of ESB is not captured. 未捕获ESB的IP地址。 Cassandra explorer shows " Non displayable value " Cassandra资源管理器显示“ 非显示值

Please advise, if stream name can be generated as eg "ESB_Stream" without date part and IP address can be published with text value. 请告知,是否可以生成流名称,例如不带日期部分的“ ESB_Stream”,并且可以使用文本值发布IP地址。

log4j.properties snippet : log4j.appender.LOGEVENT=org.wso2.carbon.logging.appender.LogEventAppender log4j.appender.LOGEVENT.url=tcp://localhost:7611 log4j.appender.LOGEVENT.layout=org.wso2.carbon.utils.logging.TenantAwarePatternLayout log4j.appender.LOGEVENT.columnList=%T,%S,%A,%d,%c,%p,%m,%H,%I,%Stacktrace log4j.appender.LOGEVENT.userName=admin log4j.appender.LOGEVENT.password=admin log4j.appender.LOGEVENT.processingLimit=1000 log4j.appender.LOGEVENT.maxTolerableConsecutiveFailure=20 log4j.appender.LOGEVENT.threshold=WARN log4j.properties代码段: log4j.appender.LOGEVENT=org.wso2.carbon.logging.appender.LogEventAppender log4j.appender.LOGEVENT.url=tcp://localhost:7611 log4j.appender.LOGEVENT.layout=org.wso2.carbon.utils.logging.TenantAwarePatternLayout log4j.appender.LOGEVENT.columnList=%T,%S,%A,%d,%c,%p,%m,%H,%I,%Stacktrace log4j.appender.LOGEVENT.userName=admin log4j.appender.LOGEVENT.password=admin log4j.appender.LOGEVENT.processingLimit=1000 log4j.appender.LOGEVENT.maxTolerableConsecutiveFailure=20 log4j.appender.LOGEVENT.threshold=WARN

At the moment you cannot configure the stream definition name, and it gets created dynamically per tenant per date per instance type. 目前,您无法配置流定义名称,并且每个实例类型的每个日期每个租户都会动态创建它。 However, we have decided to add this feature for our next releases[1] 但是,我们决定在以后的版本中添加此功能[1]

Regarding the IP not getting populated issue, we have identified this issue[2] and we have fixed it for our next 关于IP人口不足的问题,我们已经确定了此问题[2],并且已在下一个版本中对其进行了修复。

Please refer the below public jiras. 请参考下面的公共jiras。

[1] - https://wso2.org/browse/CARBON-14851 [1] -https://wso2.org/browse/CARBON-14851

[2] - https://wso2.org/jira/browse/CARBON-14991 [2] -https://wso2.org/jira/browse/CARBON-14991

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM