|
@ -1,16 +1,13 @@
|
|
|
package com.yihu.hos.broker.services;
|
|
|
|
|
|
import ch.qos.logback.classic.spi.ILoggingEvent;
|
|
|
import com.fasterxml.jackson.databind.ObjectMapper;
|
|
|
import com.yihu.hos.broker.models.BusinessLog;
|
|
|
import com.yihu.hos.core.datatype.DateUtil;
|
|
|
import com.yihu.hos.core.log.Logger;
|
|
|
import com.yihu.hos.core.log.LoggerFactory;
|
|
|
import org.springframework.beans.factory.annotation.Autowired;
|
|
|
import org.springframework.data.mongodb.core.MongoOperations;
|
|
|
import org.springframework.stereotype.Component;
|
|
|
|
|
|
import java.io.IOException;
|
|
|
import java.util.Date;
|
|
|
import java.util.Map;
|
|
|
|
|
@ -28,11 +25,12 @@ public class BusinessLogService {
|
|
|
* camel.messageId The message id
|
|
|
* camel.correlationId The correlation id of the exchange if it's correlated. For example a sub message from the Splitter EIP
|
|
|
* camel.transactionKey The id of the transaction for transacted exchanges.
|
|
|
* Note the id is not unique, but its the id of the transaction template that marks the transaction boundary for the given transaction.
|
|
|
* Hence we decided to name the key transactionKey and not transactionID to point out this fact.
|
|
|
* Note the id is not unique, but its the id of the transaction template that marks the transaction boundary for the given transaction.
|
|
|
* Hence we decided to name the key transactionKey and not transactionID to point out this fact.
|
|
|
* camel.routeId The id of the route, in which the exchange is currently being routed
|
|
|
* camel.breadcrumbId An unique id used for tracking messages across transports.
|
|
|
* camel.contextId The camel context id used for tracking the message from different camel context.
|
|
|
*
|
|
|
* @param event
|
|
|
*/
|
|
|
public void log(ILoggingEvent event) {
|