anchor.diff:  
   === Build the image yourself
   
  -You can build component starter server in docker following those instructions :
  +You can register component server images in docker using those instructions in the corresponding image directory :
   
   [source,sh]
   ----
  -cd images/component-server-images
  +# ex: cd images/component-server-image
   mvn clean compile jib:dockerBuild
   ----
  
positive.code: The component server docker image comes with two log4j2 profiles: `TEXT` (default) and `JSON`.
  The logging profile can be changed by setting the environment variable `LOGGING_LAYOUT` to `JSON`.
  
  ==== default profile
  
  The console logging is on at `INFO` level by default and you can customize it by setting `CONSOLE_LOG_LEVEL` environment variable to `DEBUG`, `INFO`, `WARN` or any other log level supported by log4j2.
  
  
negative.code: 	component-server
  ----
  
  ==== JSON profile
  
  The JSON profile does the following:
  
  1. logs on the console using `CONSOLE_LOG_LEVEL` configuration as in default profile. It uses the formatting you will find just after this list.
  2. if `TRACING_KAFKA_URL` environment variable is set it logs the opentracing data on this Kafka using the topic `TRACING_KAFKA_TOPIC`. This level can be customized using `KAFKA_LOG_LEVEL`, default being `INFO`.
  
  It uses the following format for log events:
  
  [source,json]
  ----
  {
     "eventUUID":"%uuid{RANDOM}",
     "correlationId":"%X{traceId}",
     "spanId":"%X{spanId}",
     "traceId":"%X{traceId}",
     "category":"components",
     "eventType":"LOGEvent",
     "severity":"%level",
     "logMessage":"%encode{%message}{JSON}",
     "logSource":{
        "class.name":"%class",
        "file.name":"%file",
        "host.name":"%X{hostname}",
        "line.number":"%line",
        "logger.name":"%logger",
        "method.name":"%method",
        "process.id":"%pid"
     },
     "service":"${env:LOG_SERVICE_NAME:-component-server}",
     "application":"${env:LOG_APP_NAME:-component-server}",
     "exportable":"${env:LOG_EXPORTABLE:-true}",
     "audit":"${env:LOG_AUDIT:-false}",
     "logTimestamp":"%d{ISO8601}{UTC}",
     "serverTimestamp":"%d{ISO8601}{UTC}",
     "customInfo":{
        "threadName":"%encode{%thread}{JSON}",
        "stackTrace":"%encode{%xThrowable{full}}{JSON}"
     }
  }
  ----
  
  ==== KAFKA profile
  
  This profile is very close to the previous one except it logs even the default logs - and not only the tracing ones,
  on Kafka. It adds the configuration `LOG_KAFKA_TOPIC` and `LOG_KAFKA_URL` - same as the tracing flavors but for the other logs.
  
  ==== OpenTracing
  
  The component server uses Geronimo OpenTracing to monitor request.
  
  The tracing can be activated by setting the `TRACING_ON` environment variable to `true`.
  
  The tracing rate is configurable by setting the `TRACING_SAMPLING_RATE` environment variable.
  It accepts `0` (none) and `1` (all, default) as values to ensure the consistency of the reporting.
  
  TIP: you can find all the details on the configuration in `org.talend.sdk.component.server.configuration.OpenTracingConfigSource`.
  
  Run docker image with tracing on.
  
  