1 ##########################################################################
2 # Required configuration
3 # At a minimum, the items in this section will need to be adjusted to
4 # fit your environment. The remaining options are optional.
5 ##########################################################################
7 # Points to the root of the installation. All relative
8 # paths will be resolved with the help of this path.
9 CollectorRoot "/var/log/mlogc"
11 # ModSecurity Console receiving URI. You can change the host
12 # and the port parts but leave everything else as is.
13 ConsoleURI "https://CONSOLE_IP_ADDRESS:8888/rpc/auditLogReceiver"
16 SensorUsername "SENSOR_USERNAME"
17 SensorPassword "SENSOR_PASSWORD"
19 # Base directory where the audit logs are stored. This can be specified
20 # as a path relative to the CollectorRoot, or a full path.
23 # Transaction log will contain the information on all log collector
24 # activities that happen between checkpoints. The transaction log
25 # is used to recover data in case of a crash (or if Apache kills
27 TransactionLog "mlogc-transaction.log"
29 # The file where the pending audit log entry data is kept. This file
30 # is updated on every checkpoint.
31 QueuePath "mlogc-queue.log"
33 # The location of the error log.
34 ErrorLog "mlogc-error.log"
36 # The location of the lock file.
39 # Keep audit log entries after sending? (0=false 1=true)
40 # NOTE: This is required to be set in SecAuditLog mlogc config if you
41 # are going to use a secondary console via SecAuditLog2.
45 ##########################################################################
46 # Optional configuration
47 ##########################################################################
49 # The error log level controls how much detail there
50 # will be in the error log. The levels are as follows:
60 # How many concurrent connections to the server
61 # are we allowed to open at the same time? Log collector uses
62 # multiple connections in order to speed up audit log transfer.
63 # This is especially needed when the communication takes place
64 # over a slow link (e.g. not over a LAN).
67 # How many requests a worker will process before recycling itself.
68 # This is to help prevent problems due to any memory leaks that may
69 # exists. If this is set to 0, then no maximum is imposed. The default
70 # is 1000 requests per worker (the number of workers is controlled by the
71 # MaxConnections limit).
72 MaxWorkerRequests 1000
74 # The time each connection will sit idle before being reused,
75 # in milliseconds. Increase if you don't want ModSecurity Console
76 # to be hit with too many log collector requests.
79 # The time to wait before initialization on startup in milliseconds.
80 # Increase if mlogc is starting faster then termination when the
84 # How often is the pending audit log entry data going to be written
85 # to a file. The default is 15 seconds.
88 # If the server fails all threads will back down until the
89 # problem is sorted. The management thread will periodically
90 # launch a thread to test the server. The default is to test
94 # The following two parameters are not used yet, but
95 # reserved for future expansion.
97 # KeepAliveTimeout 300