YoWuwuuuw opened a new pull request, #7259:
URL: https://github.com/apache/incubator-seata/pull/7259

   <!--
       Licensed to the Apache Software Foundation (ASF) under one or more
       contributor license agreements.  See the NOTICE file distributed with
       this work for additional information regarding copyright ownership.
       The ASF licenses this file to You under the Apache License, Version 2.0
       (the "License"); you may not use this file except in compliance with
       the License.  You may obtain a copy of the License at
   
       http://www.apache.org/licenses/LICENSE-2.0
       
       Unless required by applicable law or agreed to in writing, software
       distributed under the License is distributed on an "AS IS" BASIS,
       WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
       See the License for the specific language governing permissions and
       limitations under the License.
   -->
   <!-- Please make sure you have read and understood the contributing 
guidelines -->
   
   - [ ] I have registered the PR [changes](../changes).
   
   ### Ⅰ. Describe what this PR did
   Optimisation Points:
   If you need to collect seata-server logs to Kafka and logstash, you need to 
modify the logback-spring.xml configuration file (uncomment the corresponding 
appender), and you need to revise the specific configuration of Kafka-appender 
by revising kafka-appender.xml and application.yml.
   It's a hassle.
   
   Optimisation Scheme: Establish SpringProperty mapping
   The configuration of open Kafka, logstash and metric's appender will be 
transferred to application.yml.
   Transfer the specific configuration of Kafka to application.yml.
   
   About dynamic updates to configuration changes
   in logback-spring.xml, 
   `configuration scan="true" scanPeriod="60 seconds" debug="false"`
   The configuration is scaned every minute, so if you introduce a 
configuration center to change the yml configuration, it is visible to logback 
originally.
   
   ### Ⅱ. Does this pull request fix one issue?
   <!-- If that, add "fixes #xxx" below in the next line, for example, fixes 
#97. -->
   #4648
   
   ### Ⅲ. Why don't you add test cases (unit test/integration test)? 
   
   
   ### Ⅳ. Describe how to verify it
   
   
   ### Ⅴ. Special notes for reviews
   
   


-- 
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 unsubscribe, e-mail: notifications-unsubscr...@seata.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@seata.apache.org
For additional commands, e-mail: notifications-h...@seata.apache.org

Reply via email to