# Consolidation d'événements Métier - Besoin d'appenders Elasticsearch pour Log4J2
**URL:** https://discuss.elastic.co/t/consolidation-devenements-metier-besoin-dappenders-elasticsearch-pour-log4j2/28251
**Category:** Discussions en français
**Created:** [August 28, 2015, 2:21pm UTC](https://discuss.elastic.co/t/consolidation-devenements-metier-besoin-dappenders-elasticsearch-pour-log4j2/28251 "2015-08-28T14:21:28Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Jeff\_Contour](https://discuss.elastic.co/u/Jeff_Contour)
#### Post date: [August 28, 2015, 2:21pm UTC](https://discuss.elastic.co/t/consolidation-devenements-metier-besoin-dappenders-elasticsearch-pour-log4j2/28251/1 "2015-08-28T14:21:28Z")
Je répond (de préférence) en français... 😀
> [@Centralizing Business Events : RFC for log4j2 appenders for Elasticsearch](https://discuss.elastic.co/t/centralizing-business-events-rfc-for-log4j2-appenders-for-elasticsearch/28250):
>
> Centralizing Business events is a very common need that could be handled much more easily and this is the subject of this "Request For Comments". I tried to make it as short as possible. wink As opposed to a technical (think log4j) event, a business event : has a potentially complexe structure should never be lost (think audit purposes) could trigger more use cases if stored asap (Watcher) There are already a few open source projects that have implemented a log4j appender for Elasticsea…
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 1:51pm UTC](https://discuss.elastic.co/t/consolidation-devenements-metier-besoin-dappenders-elasticsearch-pour-log4j2/28251/2 "2017-07-06T13:51:13Z")