blob: d15a4550d1019fc7668a7ad74bf17d5f394a63fd (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
|
; This is a sample configuration file for ELAPI
; The dispatcher section defines general configuration
; for the ELAPI. It has following configuration parameters:
;
; targets - (required)
; Defines possible logical destinations where message can be sent.
; It is one of the arguments of the calling interface. It is numeric.
; It is done this way for performance reasons so it is faster to compare.
; But in the configuration it is easier to deal with targets as strings.
; To overcome this issue each target is assigned a number in the INI file.
; The ELAPI convention is to have three default targets:
; "debug", "audit" and "log" but application developers can add others as needed.
; The default value for debug target is 1, for audit 2 and log is 4.
; Changing the value defined for debug to be 7 ( logical OR of 1, 2 and 4)
; will result in all messages sent into debug log.
; This might be convenient during troubleshooting and would allow seeing all
; events emitted by the application in one place.
; If you want the event to be sent into two targets at the same time
; add a target with different name but same value.
; For example if the log events need to go to local and remote files
; in parallel you would create another target: logremote
; and give it same value as log (which by convention is 4)
[dispatcher]
targets=debug, audit, log
; Inside section for each target the following parameters can be defined:
;
; value - (optional)
; Stores the value associated with this target.
; If the bit-wise AND of this value and the value provided by caller
; of the interface is greater than 0 the event is logged into the
; target destination. If omitted all events are sent to this target.
; sinks - (required)
; Defines the list of the sink names that need to be loaded
; each will have its own section.
; Only one of the sinks is active - first in the list.
; The list contains sinks in the fail over order.
;
[debug]
value = 1
sinks = debugfile, stderr
[audit]
value = 2
sinks = auditfile, syslog
[log]
value = 4
sinks = logfile, syslog
; Each sink needs to have it's own section.
;
; COMMON FOR EVERY SINK
;
; provider - (required)
; Defines the name of the sink or the special reserved word to
; indecate that it is a sink provided natively by ELAPI library.
;
; Special sinks provided natively by ELAPI are:
; file
; stderr
; syslog
;
; Example:
; provider=file
;
; this would mean the destination for this sink is a file.
;
; If the sink is provided as an external plugin
; the syntax should be the following:
;
; provider=custom_audit
;
; In this case the ELAPI will try to load shared library with the name
; constructed using specified value. In the given example
; ELAPI will try to load libelapi_sink_custom_audit.so library.
; The general pattern is: libelapi_sink_<source>.so
[debugfile]
provider=file
[logfile]
provider=file
[auditfile]
provider=file
[stderr]
provider=stderr
[syslog]
provider=syslog
|
