75SM5vy6

1# If you are running more than one instances of Graylog server you have to select one of these
2# instances as master. The master will perform some periodical tasks that non-masters won't perform.
3is_master = true
4
5# The auto-generated node ID will be stored in this file and read after restarts. It is a good idea
6# to use an absolute file path here if you are starting Graylog server from init scripts or similar.
7node_id_file = /etc/graylog/server/node-id
8
9# You MUST set a secret to secure/pepper the stored user passwords here. Use at least 64 characters.
10# Generate one by using for example: pwgen -N 1 -s 96
11password_secret = secretkey
12
13# The default root user is named 'admin'
14root_username = admin
15
16# You MUST specify a hash password for the root user (which you only need to initially set up the
17# system and in case you lose connectivity to your authentication backend)
18# This password cannot be changed using the API or via the web interface. If you need to change it,
19# modify it in this file.
20# Create one by using for example: echo -n yourpassword | shasum -a 256
21# and put the resulting hash value into the following line
22root_password_sha2 = root password
23
24# The email address of the root user.
25# Default is empty
26root_email = "tech@thatsus.com"
27
28# The time zone setting of the root user. See http://www.joda.org/joda-time/timezones.html for a list of valid time zones.
29# Default is UTC
30root_timezone = GMT
31
32# Set plugin directory here (relative or absolute)
33plugin_dir = /usr/share/graylog-server/plugin
34
35# REST API listen URI. Must be reachable by other Graylog server nodes if you run a cluster.
36# When using Graylog Collectors, this URI will be used to receive heartbeat messages and must be accessible for all collectors.
37rest_listen_uri = http://127.0.0.1:12900/
38
39# REST API transport address. Defaults to the value of rest_listen_uri. Exception: If rest_listen_uri
40# is set to a wildcard IP address (0.0.0.0) the first non-loopback IPv4 system address is used.
41# If set, this will be promoted in the cluster discovery APIs, so other nodes may try to connect on
42# this address and it is used to generate URLs addressing entities in the REST API. (see rest_listen_uri)
43# You will need to define this, if your Graylog server is running behind a HTTP proxy that is rewriting
44# the scheme, host name or URI.
45#rest_transport_uri = http://192.168.1.1:12900/
46
47# Enable CORS headers for REST API. This is necessary for JS-clients accessing the server directly.
48# If these are disabled, modern browsers will not be able to retrieve resources from the server.
49# This is enabled by default. Uncomment the next line to disable it.
50#rest_enable_cors = false
51
52# Enable GZIP support for REST API. This compresses API responses and therefore helps to reduce
53# overall round trip times. This is disabled by default. Uncomment the next line to enable it.
54#rest_enable_gzip = true
55
56# Enable HTTPS support for the REST API. This secures the communication with the REST API with
57# TLS to prevent request forgery and eavesdropping. This is disabled by default. Uncomment the
58# next line to enable it.
59#rest_enable_tls = true
60
61# The X.509 certificate chain file in PEM format to use for securing the REST API.
62#rest_tls_cert_file = /path/to/graylog.crt
63
64# The PKCS#8 private key file in PEM format to use for securing the REST API.
65#rest_tls_key_file = /path/to/graylog.key
66
67# The password to unlock the private key used for securing the REST API.
68#rest_tls_key_password = secret
69
70# The maximum size of the HTTP request headers in bytes.
71#rest_max_header_size = 8192
72
73# The maximal length of the initial HTTP/1.1 line in bytes.
74#rest_max_initial_line_length = 4096
75
76# The size of the thread pool used exclusively for serving the REST API.
77#rest_thread_pool_size = 16
78
79# Enable the embedded Graylog web interface.
80# Default: true
81web_enable = true
82
83# Web interface listen URI
84web_listen_uri = http://ipaddress:9000/
85
86# Web interface endpoint URI. This setting can be overriden on a per-request basis with the X-Graylog-Server-URL header.
87# Default: $rest_transport_uri
88#web_endpoint_uri =
89
90# Enable CORS headers for the web interface. This is necessary for JS-clients accessing the server directly.
91# If these are disabled, modern browsers will not be able to retrieve resources from the server.
92#web_enable_cors = false
93
94# Enable/disable GZIP support for the web interface. This compresses HTTP responses and therefore helps to reduce
95# overall round trip times. This is enabled by default. Uncomment the next line to disable it.
96#web_enable_gzip = false
97
98# Enable HTTPS support for the web interface. This secures the communication of the web browser with the web interface
99# using TLS to prevent request forgery and eavesdropping.
100# This is disabled by default. Uncomment the next line to enable it and see the other related configuration settings.
101#web_enable_tls = true
102
103# The X.509 certificate chain file in PEM format to use for securing the web interface.
104#web_tls_cert_file = /path/to/graylog-web.crt
105
106# The PKCS#8 private key file in PEM format to use for securing the web interface.
107#web_tls_key_file = /path/to/graylog-web.key
108
109# The password to unlock the private key used for securing the web interface.
110#web_tls_key_password = secret
111
112# The maximum size of the HTTP request headers in bytes.
113#web_max_header_size = 8192
114
115# The maximal length of the initial HTTP/1.1 line in bytes.
116#web_max_initial_line_length = 4096
117
118# The size of the thread pool used exclusively for serving the web interface.
119#web_thread_pool_size = 16
120
121# Configuration file for the embedded Elasticsearch instance in Graylog.
122# Pay attention to the working directory of the server, maybe use an absolute path here.
123# Default: empty
124#elasticsearch_config_file = /etc/graylog/server/elasticsearch.yml
125
126# Disable checking the version of Elasticsearch for being compatible with this Graylog release.
127# WARNING: Using Graylog with unsupported and untested versions of Elasticsearch may lead to data loss!
128#elasticsearch_disable_version_check = true
129
130# Disable message retention on this node, i. e. disable Elasticsearch index rotation.
131#no_retention = false
132
133# How many Elasticsearch shards and replicas should be used per index? Note that this only applies to newly created indices.
134elasticsearch_shards = 4
135elasticsearch_replicas = 0
136
137# Prefix for all Elasticsearch indices and index aliases managed by Graylog.
138elasticsearch_index_prefix = graylog
139
140# Name of the Elasticsearch index template used by Graylog to apply the mandatory index mapping.
141# # Default: graylog-internal
142#elasticsearch_template_name = graylog-internal
143
144# Do you want to allow searches with leading wildcards? This can be extremely resource hungry and should only
145# be enabled with care. See also: https://www.graylog.org/documentation/general/queries/
146allow_leading_wildcard_searches = false
147
148# Do you want to allow searches to be highlighted? Depending on the size of your messages this can be memory hungry and
149# should only be enabled after making sure your Elasticsearch cluster has enough memory.
150allow_highlighting = false
151
152# settings to be passed to elasticsearch's client (overriding those in the provided elasticsearch_config_file)
153# all these
154# this must be the same as for your Elasticsearch cluster
155elasticsearch_cluster_name = graylog-production
156
157# The prefix being used to generate the Elasticsearch node name which makes it easier to identify the specific Graylog
158# server running the embedded Elasticsearch instance. The node name will be constructed by concatenating this prefix
159# and the Graylog node ID (see node_id_file), for example "graylog-17052010-1234-5678-abcd-1337cafebabe".
160# Default: graylog-
161#elasticsearch_node_name_prefix = graylog-
162
163# A comma-separated list of Elasticsearch nodes which Graylog is using to connect to the Elasticsearch cluster,
164# see https://www.elastic.co/guide/en/elasticsearch/reference/2.3/modules-discovery-zen.html for details.
165# Default: 127.0.0.1
166#elasticsearch_discovery_zen_ping_unicast_hosts = 127.0.0.1:9300, 127.0.0.2:9500
167
168# we don't want the Graylog server to store any data, or be master node
169#elasticsearch_node_master = false
170#elasticsearch_node_data = false
171
172# use a different port if you run multiple Elasticsearch nodes on one machine
173#elasticsearch_transport_tcp_port = 9350
174
175# we don't need to run the embedded HTTP server here
176#elasticsearch_http_enabled = false
177
178# Enable Elasticsearch multicast discovery. This requires the installation of an Elasticsearch plugin,
179# see https://www.elastic.co/guide/en/elasticsearch/plugins/2.3/discovery-multicast.html for details.
180# Default: false
181#elasticsearch_discovery_zen_ping_multicast_enabled = false
182
183# Change the following setting if you are running into problems with timeouts during Elasticsearch cluster discovery.
184# The setting is specified in milliseconds, the default is 5000ms (5 seconds).
185#elasticsearch_cluster_discovery_timeout = 5000
186
187# the following settings allow to change the bind addresses for the Elasticsearch client in Graylog
188# these settings are empty by default, letting Elasticsearch choose automatically,
189# override them here or in the 'elasticsearch_config_file' if you need to bind to a special address
190# refer to http://www.elasticsearch.org/guide/en/elasticsearch/reference/0.90/modules-network.html
191# for special values here
192#elasticsearch_network_host =
193#elasticsearch_network_bind_host =
194#elasticsearch_network_publish_host =
195
196# The total amount of time discovery will look for other Elasticsearch nodes in the cluster
197# before giving up and declaring the current node master.
198#elasticsearch_discovery_initial_state_timeout = 3s
199
200# Analyzer (tokenizer) to use for message and full_message field. The "standard" filter usually is a good idea.
201# All supported analyzers are: standard, simple, whitespace, stop, keyword, pattern, language, snowball, custom
202# Elasticsearch documentation: http://www.elasticsearch.org/guide/reference/index-modules/analysis/
203# Note that this setting only takes effect on newly created indices.
204elasticsearch_analyzer = standard
205
206# Global request timeout for Elasticsearch requests (e. g. during search, index creation, or index time-range
207# calculations) based on a best-effort to restrict the runtime of Elasticsearch operations.
208# Default: 1m
209#elasticsearch_request_timeout = 1m
210
211# Time interval for index range information cleanups. This setting defines how often stale index range information
212# is being purged from the database.
213# Default: 1h
214#index_ranges_cleanup_interval = 1h
215
216# Batch size for the Elasticsearch output. This is the maximum (!) number of messages the Elasticsearch output
217# module will get at once and write to Elasticsearch in a batch call. If the configured batch size has not been
218# reached within output_flush_interval seconds, everything that is available will be flushed at once. Remember
219# that every outputbuffer processor manages its own batch and performs its own batch write calls.
220# ("outputbuffer_processors" variable)
221output_batch_size = 500
222
223# Flush interval (in seconds) for the Elasticsearch output. This is the maximum amount of time between two
224# batches of messages written to Elasticsearch. It is only effective at all if your minimum number of messages
225# for this time period is less than output_batch_size * outputbuffer_processors.
226output_flush_interval = 1
227
228# As stream outputs are loaded only on demand, an output which is failing to initialize will be tried over and
229# over again. To prevent this, the following configuration options define after how many faults an output will
230# not be tried again for an also configurable amount of seconds.
231output_fault_count_threshold = 5
232output_fault_penalty_seconds = 30
233
234# The number of parallel running processors.
235# Raise this number if your buffers are filling up.
236processbuffer_processors = 5
237outputbuffer_processors = 3
238
239#outputbuffer_processor_keep_alive_time = 5000
240#outputbuffer_processor_threads_core_pool_size = 3
241#outputbuffer_processor_threads_max_pool_size = 30
242
243# UDP receive buffer size for all message inputs (e. g. SyslogUDPInput).
244#udp_recvbuffer_sizes = 1048576
245
246# Wait strategy describing how buffer processors wait on a cursor sequence. (default: sleeping)
247# Possible types:
248#  - yielding
249#     Compromise between performance and CPU usage.
250#  - sleeping
251#     Compromise between performance and CPU usage. Latency spikes can occur after quiet periods.
252#  - blocking
253#     High throughput, low latency, higher CPU usage.
254#  - busy_spinning
255#     Avoids syscalls which could introduce latency jitter. Best when threads can be bound to specific CPU cores.
256processor_wait_strategy = blocking
257
258# Size of internal ring buffers. Raise this if raising outputbuffer_processors does not help anymore.
259# For optimum performance your LogMessage objects in the ring buffer should fit in your CPU L3 cache.
260# Must be a power of 2. (512, 1024, 2048, ...)
261ring_size = 65536
262
263inputbuffer_ring_size = 65536
264inputbuffer_processors = 2
265inputbuffer_wait_strategy = blocking
266
267# Enable the disk based message journal.
268message_journal_enabled = true
269
270# The directory which will be used to store the message journal. The directory must me exclusively used by Graylog and
271# must not contain any other files than the ones created by Graylog itself.
272message_journal_dir = /var/lib/graylog-server/journal
273
274# Journal hold messages before they could be written to Elasticsearch.
275# For a maximum of 12 hours or 5 GB whichever happens first.
276# During normal operation the journal will be smaller.
277#message_journal_max_age = 12h
278#message_journal_max_size = 5gb
279
280#message_journal_flush_age = 1m
281#message_journal_flush_interval = 1000000
282#message_journal_segment_age = 1h
283#message_journal_segment_size = 100mb
284
285# Number of threads used exclusively for dispatching internal events. Default is 2.
286#async_eventbus_processors = 2
287
288# How many seconds to wait between marking node as DEAD for possible load balancers and starting the actual
289# shutdown process. Set to 0 if you have no status checking load balancers in front.
290lb_recognition_period_seconds = 3
291
292# Every message is matched against the configured streams and it can happen that a stream contains rules which
293# take an unusual amount of time to run, for example if its using regular expressions that perform excessive backtracking.
294# This will impact the processing of the entire server. To keep such misbehaving stream rules from impacting other
295# streams, Graylog limits the execution time for each stream.
296# The default values are noted below, the timeout is in milliseconds.
297# If the stream matching for one stream took longer than the timeout value, and this happened more than "max_faults" times
298# that stream is disabled and a notification is shown in the web interface.
299#stream_processing_timeout = 2000
300#stream_processing_max_faults = 3
301
302# Length of the interval in seconds in which the alert conditions for all streams should be checked
303# and alarms are being sent.
304#alert_check_interval = 60
305
306# Since 0.21 the Graylog server supports pluggable output modules. This means a single message can be written to multiple
307# outputs. The next setting defines the timeout for a single output module, including the default output module where all
308# messages end up.
309#
310# Time in milliseconds to wait for all message outputs to finish writing a single message.
311#output_module_timeout = 10000
312
313# Time in milliseconds after which a detected stale master node is being rechecked on startup.
314#stale_master_timeout = 2000
315
316# Time in milliseconds which Graylog is waiting for all threads to stop on shutdown.
317#shutdown_timeout = 30000
318
319# MongoDB connection string
320# See http://docs.mongodb.org/manual/reference/connection-string/ for details
321mongodb_uri = mongodb://localhost/graylog
322
323# Authenticate against the MongoDB server
324#mongodb_uri = mongodb://grayloguser:secret@localhost:27017/graylog
325
326# Use a replica set instead of a single host
327#mongodb_uri = mongodb://grayloguser:secret@localhost:27017,localhost:27018,localhost:27019/graylog
328
329# Increase this value according to the maximum connections your MongoDB server can handle from a single client
330# if you encounter MongoDB connection problems.
331mongodb_max_connections = 1000
332
333# Number of threads allowed to be blocked by MongoDB connections multiplier. Default: 5
334# If mongodb_max_connections is 100, and mongodb_threads_allowed_to_block_multiplier is 5,
335# then 500 threads can block. More than that and an exception will be thrown.
336# http://api.mongodb.org/java/current/com/mongodb/MongoOptions.html#threadsAllowedToBlockForConnectionMultiplier
337mongodb_threads_allowed_to_block_multiplier = 5
338
339# Drools Rule File (Use to rewrite incoming log messages)
340# See: https://www.graylog.org/documentation/general/rewriting/
341#rules_file = /etc/graylog/server/rules.drl
342
343# Email transport
344#transport_email_enabled = false
345#transport_email_hostname = mail.example.com
346#transport_email_port = 587
347#transport_email_use_auth = true
348#transport_email_use_tls = true
349#transport_email_use_ssl = true
350#transport_email_auth_username = you@example.com
351#transport_email_auth_password = secret
352#transport_email_subject_prefix = [graylog]
353#transport_email_from_email = graylog@example.com
354
355# Specify and uncomment this if you want to include links to the stream in your stream alert mails.
356# This should define the fully qualified base url to your web interface exactly the same way as it is accessed by your users.
357#transport_email_web_interface_url = https://graylog.example.com
358
359# The default connect timeout for outgoing HTTP connections.
360# Values must be a positive duration (and between 1 and 2147483647 when converted to milliseconds).
361# Default: 5s
362#http_connect_timeout = 5s
363
364# The default read timeout for outgoing HTTP connections.
365# Values must be a positive duration (and between 1 and 2147483647 when converted to milliseconds).
366# Default: 10s
367#http_read_timeout = 10s
368
369# The default write timeout for outgoing HTTP connections.
370# Values must be a positive duration (and between 1 and 2147483647 when converted to milliseconds).
371# Default: 10s
372#http_write_timeout = 10s
373
374# HTTP proxy for outgoing HTTP connections
375#http_proxy_uri =
376
377# Disable the optimization of Elasticsearch indices after index cycling. This may take some load from Elasticsearch
378# on heavily used systems with large indices, but it will decrease search performance. The default is to optimize
379# cycled indices.
380#disable_index_optimization = true
381
382# Optimize the index down to <= index_optimization_max_num_segments. A higher number may take some load from Elasticsearch
383# on heavily used systems with large indices, but it will decrease search performance. The default is 1.
384#index_optimization_max_num_segments = 1
385
386# The threshold of the garbage collection runs. If GC runs take longer than this threshold, a system notification
387# will be generated to warn the administrator about possible problems with the system. Default is 1 second.
388#gc_warning_threshold = 1s
389
390# Connection timeout for a configured LDAP server (e. g. ActiveDirectory) in milliseconds.
391#ldap_connection_timeout = 2000
392
393# Enable collection of Graylog-related metrics into MongoDB
394# WARNING: This will add *a lot* of data into your MongoDB database on a regular interval (1 second)!
395# DEPRECATED: This setting and the respective feature will be removed in a future version of Graylog.
396#enable_metrics_collection = false
397
398# Disable the use of SIGAR for collecting system stats
399#disable_sigar = false
400
401# The default cache time for dashboard widgets. (Default: 10 seconds, minimum: 1 second)
402#dashboard_widget_default_cache_time = 10s
403
404# Automatically load content packs in "content_packs_dir" on the first start of Graylog.
405#content_packs_loader_enabled = true
406
407# The directory which contains content packs which should be loaded on the first start of Graylog.
408content_packs_dir = /usr/share/graylog-server/contentpacks
409
410# A comma-separated list of content packs (files in "content_packs_dir") which should be applied on
411# the first start of Graylog.
412# Default: empty
413content_packs_auto_load = grok-patterns.json