vy closed issue #3442: make SocketAppender support server list
URL: https://github.com/apache/logging-log4j2/issues/3442
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsu
vy commented on issue #3442:
URL:
https://github.com/apache/logging-log4j2/issues/3442#issuecomment-2724028069
Since multiple solutions (i.e., using a `Routing` appender or creating a
custom one) are provided to the user, closing this one as `Not Planned`.
--
This is an automated message
lu-xiaoshuang commented on issue #3442:
URL:
https://github.com/apache/logging-log4j2/issues/3442#issuecomment-2699866460
> [@lu-xiaoshuang](https://github.com/lu-xiaoshuang), in
[#3482](https://github.com/apache/logging-log4j2/pull/3482), I see you randomly
choose hosts to write to. Can't
vy commented on issue #3442:
URL:
https://github.com/apache/logging-log4j2/issues/3442#issuecomment-2676323382
@lu-xiaoshuang, in #3482, I see you randomly choose hosts to write to. Can't
you simply define multiple socket appenders and choose them using [scripted
routes](https://logging.ap
lu-xiaoshuang commented on issue #3442:
URL:
https://github.com/apache/logging-log4j2/issues/3442#issuecomment-2653507527
> 1. in your personal or company repo under Apache-2.0.
Good idea.
--
This is an automated message from the Apache Git Service.
To respond to the message, pleas
ppkarwasz commented on issue #3442:
URL:
https://github.com/apache/logging-log4j2/issues/3442#issuecomment-2652808212
> KafkaAppender is not capable of sending logs generated by
org.apache.kafka:kafka-clients:jar, is it?
Right, that usually causes problems with recursive logging.
lu-xiaoshuang commented on issue #3442:
URL:
https://github.com/apache/logging-log4j2/issues/3442#issuecomment-2652418157
> [@lu-xiaoshuang](https://github.com/lu-xiaoshuang),
>
> > At present, a SocketAppender only supports one address-port. Seems that
remote server represented by t
lu-xiaoshuang commented on issue #3442:
URL:
https://github.com/apache/logging-log4j2/issues/3442#issuecomment-2652407866
> [@lu-xiaoshuang](https://github.com/lu-xiaoshuang), curious: what is the
log sink you use where you encounter this problem?
logstash
--
This is an automated
vy commented on issue #3442:
URL:
https://github.com/apache/logging-log4j2/issues/3442#issuecomment-2649208156
@lu-xiaoshuang, curious: what is the log sink you use where you encounter
this problem?
--
This is an automated message from the Apache Git Service.
To respond to the message, p
ppkarwasz commented on issue #3442:
URL:
https://github.com/apache/logging-log4j2/issues/3442#issuecomment-2646179772
@lu-xiaoshuang,
> At present, a SocketAppender only supports one address-port. Seems that
remote server represented by this address-port is very likely the bottleneck
lu-xiaoshuang commented on issue #3442:
URL:
https://github.com/apache/logging-log4j2/issues/3442#issuecomment-2644538331
> Have you considered sending logging events via the [fluent-bit Forward
Upstream
plugin](https://docs.fluentbit.io/manual/administration/configuring-fluent-bit/classic
swebb2066 commented on issue #3442:
URL:
https://github.com/apache/logging-log4j2/issues/3442#issuecomment-2644524432
Have you considered sending logging events via the [fluent-bit Forward
Upstream
plugin](https://docs.fluentbit.io/manual/administration/configuring-fluent-bit/classic-mode/
lu-xiaoshuang opened a new issue, #3442:
URL: https://github.com/apache/logging-log4j2/issues/3442
Typically, applications generate massive amounts of log data, which need to
be sent to the backend systems for storage, analyzing and so on.
At present, a SocketAppender only supports on
13 matches
Mail list logo
