Statistics
| Branch: | Tag: | Revision:

root / rudder-web / src / main / resources / logback.xml @ 8c0328a9

History | View | Annotate | Download (5.1 kB)

1
<!--
2
Copyright 2011 Normation SAS
3

4
This program is free software: you can redistribute it and/or modify
5
it under the terms of the GNU Affero General Public License as
6
published by the Free Software Foundation, either version 3 of the
7
License, or (at your option) any later version.
8

9
In accordance with the terms of section 7 (7. Additional Terms.) of
10
the GNU Affero GPL v3, the copyright holders add the following
11
Additional permissions:
12
Notwithstanding to the terms of section 5 (5. Conveying Modified Source
13
Versions) and 6 (6. Conveying Non-Source Forms.) of the GNU Affero GPL v3
14
licence, when you create a Related Module, this Related Module is
15
not considered as a part of the work and may be distributed under the
16
license agreement of your choice.
17
A "Related Module" means a set of sources files including their
18
documentation that, without modification of the Source Code, enables
19
supplementary functions or services in addition to those offered by
20
the Software.
21

22
This program is distributed in the hope that it will be useful,
23
but WITHOUT ANY WARRANTY; without even the implied warranty of
24
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
25
GNU Affero General Public License for more details.
26

27
You should have received a copy of the GNU Affero General Public License
28
along with this program. If not, see <http://www.gnu.org/licenses/agpl.html>.
29
-->
30

    
31
<configuration>
32
  <!-- 
33
    This is the default logging configuration file. It will be used if you
34
    didn't specify the "logback.configurationFile" JVM option. 
35
    For example, to use a loggin configuration file in "/etc/rudder":
36
    java ... -Dlogback.configurationFile=/etc/rudder/logback.xml
37
    
38
    Full information about the file format is available on the project
39
    web site: http://logback.qos.ch/manual/configuration.html#syntax
40
   -->
41

    
42
  <!-- 
43
    Appender configuration - where&how to write logs in SLF4J speaking.
44
    ===================================================================
45
    Our default configuration : log on stdout appender so that our logs
46
    are managed by the container log system (and so, if Tomcat/Jetty/etc
47
    logs are stored in files and rotated, so are our log information).
48
    
49
    Log format is:
50
    - date/time/thread of the log on 30 chars (fixed)
51
    - log level on 5 char (fixed)
52
    - name of the logger (and so the class) on 36 chars, with
53
      package name folding
54
    - log message follows
55
    - limit exception trace to 30 calls
56
    
57
    You should not have to modify that. 
58
  -->
59
  <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
60
    <encoder class="ch.qos.logback.classic.encoder.PatternLayoutEncoder">
61
      <Pattern>%-30(%d{HH:mm:ss.SSS} [%thread]) %-5level %logger{36} - %msg%n%xEx{30}</Pattern>
62
    </encoder>
63
  </appender>
64

    
65
  <!-- 
66
    Manage the global log level of the application.
67
    ===============================================
68
    
69
    That level will be used for all logs that are not
70
    more precisely defined below (i.e for whom there is
71
    no <logger name="...." level="..."/> defined)  
72
    
73
    Available log levels are: 
74
         trace < debug < info < warn < error < off 
75
    "off" completely shut down logging for the given logger
76
    
77
    Do not modify the appender part if you don't know what you
78
    are doing.
79
  -->
80
  
81
  <root level="info">
82
    <appender-ref ref="STDOUT" />
83
  </root>
84
  
85
  <!--
86
    Debug LDAP write operations
87
    ===========================
88
    
89
    This logger allow to trace LDAP writes operation and
90
    to output them in LDIF file (the output directory path 
91
    is configured in the main configuration file)
92
    The trace is done only if level is set to "trace"
93
    WARNING: setting the level to trace may have major
94
    performance issue, as A LOT of LDIF files will have
95
    to be written. 
96
    You should activate that log only for debugging purpose.
97
  -->
98
  
99
  <logger name="trace.ldif.in.file" level="off" />
100

    
101

    
102
  <!-- ==================================================== -->
103
  <!-- YOU SHOULD NOT HAVE TO CHANGE THINGS BELOW THAT LINE -->
104
  <!-- ==================================================== -->
105
  
106
  <!-- 
107
    Display AJAX information of the Web interface
108
    =============================================
109
    Whatever the root logger level is, you are likely
110
    to not wanting these information. 
111
    Set the level to debug if you are really interested
112
    in AJAX-related debug messages.
113
  -->
114
  <logger name="comet_trace" level="info" />
115
  
116
  <!-- 
117
    Spring Framework log level
118
    ==========================
119
    We really don't want to see SpringFramework debug info, 
120
    whatever the root logger level is - it's an internal
121
    component only.
122
  -->
123
  <logger name="org.springframework" level="warn" />
124
 
125
  <!-- 
126
    We don't need to have a timing information for each 
127
    HTTP request.
128
    If you want to have these information, set the log
129
    level for that logger to (at least) "info"
130
   -->
131
  <logger name="net.liftweb.util.TimeHelpers" level="warn" />
132
  
133
  <!-- Uncomment to have precise log about LDAP queries done by the node search engine -->
134
<!--   <logger name="com.normation.rudder.services.queries.InternalLDAPQueryProcessor" level="debug" /> -->
135
 
136
</configuration>