1ORG.FREEDESKTOP.LOGCONTROL1o(r5g).freedesktop.LogContOrRoGl.1FREEDESKTOP.LOGCONTROL1(5)
2
3
4
6 org.freedesktop.LogControl1 - D-Bus interface to query and set logging
7 configuration
8
10 org.freedesktop.LogControl1 is a generic interface that is intended to
11 be used by any daemon which allows the log level and target to be set
12 over D-Bus. It is implemented by various daemons that are part of the
13 systemd(1) suite.
14
15 It is assumed that those settings are global for the whole program, so
16 a fixed object path is used. The interface should always be available
17 under the path /org/freedesktop/LogControl1.
18
20 The following interface is exposed:
21
22 node /org/freedesktop/LogControl1 {
23 interface org.freedesktop.LogControl1 {
24 properties:
25 @org.freedesktop.DBus.Property.EmitsChangedSignal("false")
26 @org.freedesktop.systemd1.Privileged("true")
27 readwrite s LogLevel = '...';
28 @org.freedesktop.DBus.Property.EmitsChangedSignal("false")
29 @org.freedesktop.systemd1.Privileged("true")
30 readwrite s LogTarget = '...';
31 @org.freedesktop.DBus.Property.EmitsChangedSignal("false")
32 readonly s SyslogIdentifier = '...';
33 };
34 interface org.freedesktop.DBus.Peer { ... };
35 interface org.freedesktop.DBus.Introspectable { ... };
36 interface org.freedesktop.DBus.Properties { ... };
37 };
38
39
40
41
42
43
44 Properties
45 LogLevel describes the syslog(3)-style log-level, and should be one of
46 "emerg", "alert", "crit", "err", "warning", "notice", "info", "debug",
47 in order of increasing verbosity.
48
49 LogTarget describes the log target (mechanism). It should be one of
50 "console" (log to the console or standard output), "kmsg" (log to the
51 kernel ring buffer), "journal" (log to the journal natively, see
52 systemd-journald.service(8)), "syslog" (log using the syslog(3) call).
53
54 Those two properties are writable, so they may be set by sufficiently
55 privileged users.
56
57 SyslogIdentifier is a read-only property that shows the "syslog
58 identifier". It is a short string that identifies the program that is
59 the source of log messages that is passed to the syslog(3) call.
60
62 journalctl option -p/--priority= may be used to filter log messages by
63 log level, option -t/--identifier= may be used to by the syslog
64 identifier, and filters like "_TRANSPORT=syslog", "_TRANSPORT=journal",
65 and "_TRANSPORT=kernel" may be used to filter messages by the mechanism
66 through which they reached systemd-journald.
67
68 systemctl log-level and systemctl log-target verbs may be used to query
69 and set the LogLevel and LogTarget properties of the service manager.
70 systemctl service-log-level and systemctl service-log-target may
71 similarly be used for individual services. (Services must have the
72 BusName= property set and must implement the interface described here.
73 See systemd.service(5) for details about BusName=.)
74
76 systemd(1), journalctl(1), systemctl(1), systemd.service(5), syslog(3)
77
78
79
80systemd 251 ORG.FREEDESKTOP.LOGCONTROL1(5)