Notices tagged with log4j
-
I’ve got a customer with what looks like a character encoding issue in either #elasticsearch or #fluentd. Here’s the message: 2021-06-08 17:05:50 +0800 [warn]: #0 dump an error event: error_class=Fluent::Plugin::ElasticsearchErrorHandler::ElasticsearchError error=“400 - Rejected by Elasticsearch [error type]: mapper_parsing_exception [reason]: ‘failed to parse field [me…
-
just marked my first customer issue resolved on my new team. It's always frustrating when a customer doesn't get back to you, but it's been over a week and I've checked in, so I am calling it done.
In any case, I told him the answer in my first response, he just didn't like it. I mean, #log4j may well be a better longterm solution for them, but it doesn't do exactly what they asked like my first response.
Douglas A. Whitfield
All Hacker Poesy content and data are available under the