1############################ 2# GRAYLOG CONFIGURATION FILE 3############################ 4# 5# This is the Graylog configuration file. The file has to use ISO 8859-1/Latin-1 character encoding. 6# Characters that cannot be directly represented in this encoding can be written using Unicode escapes 7# as defined in https://docs.oracle.com/javase/specs/jls/se8/html/jls-3.html#jls-3.3, using the \u prefix. 8# For example, \u002c. 9# 10# * Entries are generally expected to be a single line of the form, one of the following: 11# 12# propertyName=propertyValue 13# propertyName:propertyValue 14# 15# * White space that appears between the property name and property value is ignored, 16# so the following are equivalent: 17# 18# name=Stephen 19# name = Stephen 20# 21# * White space at the beginning of the line is also ignored. 22# 23# * Lines that start with the comment characters ! or # are ignored. Blank lines are also ignored. 24# 25# * The property value is generally terminated by the end of the line. White space following the 26# property value is not ignored, and is treated as part of the property value. 27# 28# * A property value can span several lines if each line is terminated by a backslash (‘\’) character. 29# For example: 30# 31# targetCities=\ 32# Detroit,\ 33# Chicago,\ 34# Los Angeles 35# 36# This is equivalent to targetCities=Detroit,Chicago,Los Angeles (white space at the beginning of lines is ignored). 37# 38# * The characters newline, carriage return, and tab can be inserted with characters \n, \r, and \t, respectively. 39# 40# * The backslash character must be escaped as a double backslash. For example: 41# 42# path=c:\\docs\\doc1 43# 44 45# If you are running more than one instances of Graylog server you have to select one of these 46# instances as master. The master will perform some periodical tasks that non-masters won't perform. 47is_master = true 48 49# The auto-generated node ID will be stored in this file and read after restarts. It is a good idea 50# to use an absolute file path here if you are starting Graylog server from init scripts or similar. 51node_id_file = /usr/local/etc/graylog/server/node-id 52 53# You MUST set a secret to secure/pepper the stored user passwords here. Use at least 64 characters. 54# Generate one by using for example: pwgen -N 1 -s 96 55# ATTENTION: This value must be the same on all Graylog nodes in the cluster. 56# Changing this value after installation will render all user sessions and encrypted values in the database invalid. (e.g. encrypted access tokens) 57password_secret = 58 59# The default root user is named 'admin' 60#root_username = admin 61 62# You MUST specify a hash password for the root user (which you only need to initially set up the 63# system and in case you lose connectivity to your authentication backend) 64# This password cannot be changed using the API or via the web interface. If you need to change it, 65# modify it in this file. 66# Create one by using for example: echo -n yourpassword | shasum -a 256 67# and put the resulting hash value into the following line 68root_password_sha2 = 69 70# The email address of the root user. 71# Default is empty 72#root_email = "" 73 74# The time zone setting of the root user. See http://www.joda.org/joda-time/timezones.html for a list of valid time zones. 75# Default is UTC 76#root_timezone = UTC 77 78# Set the bin directory here (relative or absolute) 79# This directory contains binaries that are used by the Graylog server. 80# Default: bin 81bin_dir = /usr/local/share/graylog/bin 82 83# Set the data directory here (relative or absolute) 84# This directory is used to store Graylog server state. 85# Default: data 86data_dir = /var/db/graylog 87 88# Set plugin directory here (relative or absolute) 89plugin_dir = /usr/local/share/graylog/plugin 90 91############### 92# HTTP settings 93############### 94 95#### HTTP bind address 96# 97# The network interface used by the Graylog HTTP interface. 98# 99# This network interface must be accessible by all Graylog nodes in the cluster and by all clients 100# using the Graylog web interface. 101# 102# If the port is omitted, Graylog will use port 9000 by default. 103# 104# Default: 127.0.0.1:9000 105#http_bind_address = 127.0.0.1:9000 106#http_bind_address = [2001:db8::1]:9000 107 108#### HTTP publish URI 109# 110# The HTTP URI of this Graylog node which is used to communicate with the other Graylog nodes in the cluster and by all 111# clients using the Graylog web interface. 112# 113# The URI will be published in the cluster discovery APIs, so that other Graylog nodes will be able to find and connect to this Graylog node. 114# 115# This configuration setting has to be used if this Graylog node is available on another network interface than $http_bind_address, 116# for example if the machine has multiple network interfaces or is behind a NAT gateway. 117# 118# If $http_bind_address contains a wildcard IPv4 address (0.0.0.0), the first non-loopback IPv4 address of this machine will be used. 119# This configuration setting *must not* contain a wildcard address! 120# 121# Default: http://$http_bind_address/ 122#http_publish_uri = http://192.168.1.1:9000/ 123 124#### External Graylog URI 125# 126# The public URI of Graylog which will be used by the Graylog web interface to communicate with the Graylog REST API. 127# 128# The external Graylog URI usually has to be specified, if Graylog is running behind a reverse proxy or load-balancer 129# and it will be used to generate URLs addressing entities in the Graylog REST API (see $http_bind_address). 130# 131# When using Graylog Collector, this URI will be used to receive heartbeat messages and must be accessible for all collectors. 132# 133# This setting can be overriden on a per-request basis with the "X-Graylog-Server-URL" HTTP request header. 134# 135# Default: $http_publish_uri 136#http_external_uri = 137 138#### Enable CORS headers for HTTP interface 139# 140# This allows browsers to make Cross-Origin requests from any origin. 141# This is disabled for security reasons and typically only needed if running graylog 142# with a separate server for frontend development. 143# 144# Default: false 145#http_enable_cors = false 146 147#### Enable GZIP support for HTTP interface 148# 149# This compresses API responses and therefore helps to reduce 150# overall round trip times. This is enabled by default. Uncomment the next line to disable it. 151#http_enable_gzip = false 152 153# The maximum size of the HTTP request headers in bytes. 154#http_max_header_size = 8192 155 156# The size of the thread pool used exclusively for serving the HTTP interface. 157#http_thread_pool_size = 16 158 159################ 160# HTTPS settings 161################ 162 163#### Enable HTTPS support for the HTTP interface 164# 165# This secures the communication with the HTTP interface with TLS to prevent request forgery and eavesdropping. 166# 167# Default: false 168#http_enable_tls = true 169 170# The X.509 certificate chain file in PEM format to use for securing the HTTP interface. 171#http_tls_cert_file = /path/to/graylog.crt 172 173# The PKCS#8 private key file in PEM format to use for securing the HTTP interface. 174#http_tls_key_file = /path/to/graylog.key 175 176# The password to unlock the private key used for securing the HTTP interface. 177#http_tls_key_password = secret 178 179 180# Comma separated list of trusted proxies that are allowed to set the client address with X-Forwarded-For 181# header. May be subnets, or hosts. 182#trusted_proxies = 127.0.0.1/32, 0:0:0:0:0:0:0:1/128 183 184# List of Elasticsearch hosts Graylog should connect to. 185# Need to be specified as a comma-separated list of valid URIs for the http ports of your elasticsearch nodes. 186# If one or more of your elasticsearch hosts require authentication, include the credentials in each node URI that 187# requires authentication. 188# 189# Default: http://127.0.0.1:9200 190#elasticsearch_hosts = http://node1:9200,http://user:password@node2:19200 191 192# Maximum number of retries to connect to elasticsearch on boot for the version probe. 193# 194# Default: 0, retry indefinitely with the given delay until a connection could be established 195#elasticsearch_version_probe_attempts = 5 196 197# Waiting time in between connection attempts for elasticsearch_version_probe_attempts 198# 199# Default: 5s 200#elasticsearch_version_probe_delay = 5s 201 202# Maximum amount of time to wait for successful connection to Elasticsearch HTTP port. 203# 204# Default: 10 Seconds 205#elasticsearch_connect_timeout = 10s 206 207# Maximum amount of time to wait for reading back a response from an Elasticsearch server. 208# (e. g. during search, index creation, or index time-range calculations) 209# 210# Default: 60 seconds 211#elasticsearch_socket_timeout = 60s 212 213# Maximum idle time for an Elasticsearch connection. If this is exceeded, this connection will 214# be tore down. 215# 216# Default: inf 217#elasticsearch_idle_timeout = -1s 218 219# Maximum number of total connections to Elasticsearch. 220# 221# Default: 200 222#elasticsearch_max_total_connections = 200 223 224# Maximum number of total connections per Elasticsearch route (normally this means per 225# elasticsearch server). 226# 227# Default: 20 228#elasticsearch_max_total_connections_per_route = 20 229 230# Maximum number of times Graylog will retry failed requests to Elasticsearch. 231# 232# Default: 2 233#elasticsearch_max_retries = 2 234 235# Enable automatic Elasticsearch node discovery through Nodes Info, 236# see https://www.elastic.co/guide/en/elasticsearch/reference/5.4/cluster-nodes-info.html 237# 238# WARNING: Automatic node discovery does not work if Elasticsearch requires authentication, e. g. with Shield. 239# 240# Default: false 241#elasticsearch_discovery_enabled = true 242 243# Filter for including/excluding Elasticsearch nodes in discovery according to their custom attributes, 244# see https://www.elastic.co/guide/en/elasticsearch/reference/5.4/cluster.html#cluster-nodes 245# 246# Default: empty 247#elasticsearch_discovery_filter = rack:42 248 249# Frequency of the Elasticsearch node discovery. 250# 251# Default: 30s 252# elasticsearch_discovery_frequency = 30s 253 254# Set the default scheme when connecting to Elasticsearch discovered nodes 255# 256# Default: http (available options: http, https) 257#elasticsearch_discovery_default_scheme = http 258 259# Enable payload compression for Elasticsearch requests. 260# 261# Default: false 262#elasticsearch_compression_enabled = true 263 264# Enable use of "Expect: 100-continue" Header for Elasticsearch index requests. 265# If this is disabled, Graylog cannot properly handle HTTP 413 Request Entity Too Large errors. 266# 267# Default: true 268#elasticsearch_use_expect_continue = true 269 270# Graylog will use multiple indices to store documents in. You can configure the strategy it uses to determine 271# when to rotate the currently active write index. 272# It supports multiple rotation strategies, the default being "count": 273# - "count" of messages per index, use elasticsearch_max_docs_per_index below to configure 274# - "size" per index, use elasticsearch_max_size_per_index below to configure 275# - "time" interval between index rotations, use elasticsearch_max_time_per_index to configure 276# A strategy may be disabled by specifying the optional enabled_index_rotation_strategies list and excluding that strategy. 277#enabled_index_rotation_strategies = count,size,time 278 279# 280# ATTENTION: These settings have been moved to the database in 2.0. When you upgrade, make sure to set these 281# to your previous 1.x settings so they will be migrated to the database! 282# This configuration setting is only used on the first start of Graylog. After that, 283# index related settings can be changed in the Graylog web interface on the 'System / Indices' page. 284# Also see https://docs.graylog.org/docs/index-model#index-set-configuration 285rotation_strategy = count 286 287# (Approximate) maximum number of documents in an Elasticsearch index before a new index 288# is being created, also see no_retention and elasticsearch_max_number_of_indices. 289# Configure this if you used 'rotation_strategy = count' above. 290# 291# ATTENTION: These settings have been moved to the database in 2.0. When you upgrade, make sure to set these 292# to your previous 1.x settings so they will be migrated to the database! 293# This configuration setting is only used on the first start of Graylog. After that, 294# index related settings can be changed in the Graylog web interface on the 'System / Indices' page. 295# Also see https://docs.graylog.org/docs/index-model#index-set-configuration 296elasticsearch_max_docs_per_index = 20000000 297 298# (Approximate) maximum size in bytes per Elasticsearch index on disk before a new index is being created, also see 299# no_retention and elasticsearch_max_number_of_indices. Default is 1GB. 300# Configure this if you used 'rotation_strategy = size' above. 301# 302# ATTENTION: These settings have been moved to the database in 2.0. When you upgrade, make sure to set these 303# to your previous 1.x settings so they will be migrated to the database! 304# This configuration setting is only used on the first start of Graylog. After that, 305# index related settings can be changed in the Graylog web interface on the 'System / Indices' page. 306# Also see https://docs.graylog.org/docs/index-model#index-set-configuration 307#elasticsearch_max_size_per_index = 1073741824 308 309# (Approximate) maximum time before a new Elasticsearch index is being created, also see 310# no_retention and elasticsearch_max_number_of_indices. Default is 1 day. 311# Configure this if you used 'rotation_strategy = time' above. 312# Please note that this rotation period does not look at the time specified in the received messages, but is 313# using the real clock value to decide when to rotate the index! 314# Specify the time using a duration and a suffix indicating which unit you want: 315# 1w = 1 week 316# 1d = 1 day 317# 12h = 12 hours 318# Permitted suffixes are: d for day, h for hour, m for minute, s for second. 319# 320# ATTENTION: These settings have been moved to the database in 2.0. When you upgrade, make sure to set these 321# to your previous 1.x settings so they will be migrated to the database! 322# This configuration setting is only used on the first start of Graylog. After that, 323# index related settings can be changed in the Graylog web interface on the 'System / Indices' page. 324# Also see https://docs.graylog.org/docs/index-model#index-set-configuration 325#elasticsearch_max_time_per_index = 1d 326 327# Optional upper bound on elasticsearch_max_time_per_index 328# elasticsearch_max_write_index_age = 1d 329 330# Disable checking the version of Elasticsearch for being compatible with this Graylog release. 331# WARNING: Using Graylog with unsupported and untested versions of Elasticsearch may lead to data loss! 332#elasticsearch_disable_version_check = true 333 334# Disable message retention on this node, i. e. disable Elasticsearch index rotation. 335#no_retention = false 336 337# How many indices do you want to keep? 338# 339# ATTENTION: These settings have been moved to the database in 2.0. When you upgrade, make sure to set these 340# to your previous 1.x settings so they will be migrated to the database! 341# This configuration setting is only used on the first start of Graylog. After that, 342# index related settings can be changed in the Graylog web interface on the 'System / Indices' page. 343# Also see https://docs.graylog.org/docs/index-model#index-set-configuration 344elasticsearch_max_number_of_indices = 20 345 346# Decide what happens with the oldest indices when the maximum number of indices is reached. 347# The following strategies are availble: 348# - delete # Deletes the index completely (Default) 349# - close # Closes the index and hides it from the system. Can be re-opened later. 350# 351# ATTENTION: These settings have been moved to the database in 2.0. When you upgrade, make sure to set these 352# to your previous 1.x settings so they will be migrated to the database! 353# This configuration setting is only used on the first start of Graylog. After that, 354# index related settings can be changed in the Graylog web interface on the 'System / Indices' page. 355# Also see https://docs.graylog.org/docs/index-model#index-set-configuration 356retention_strategy = delete 357 358# How many Elasticsearch shards and replicas should be used per index? Note that this only applies to newly created indices. 359# ATTENTION: These settings have been moved to the database in Graylog 2.2.0. When you upgrade, make sure to set these 360# to your previous settings so they will be migrated to the database! 361# This configuration setting is only used on the first start of Graylog. After that, 362# index related settings can be changed in the Graylog web interface on the 'System / Indices' page. 363# Also see https://docs.graylog.org/docs/index-model#index-set-configuration 364elasticsearch_shards = 4 365elasticsearch_replicas = 0 366 367# Prefix for all Elasticsearch indices and index aliases managed by Graylog. 368# 369# ATTENTION: These settings have been moved to the database in Graylog 2.2.0. When you upgrade, make sure to set these 370# to your previous settings so they will be migrated to the database! 371# This configuration setting is only used on the first start of Graylog. After that, 372# index related settings can be changed in the Graylog web interface on the 'System / Indices' page. 373# Also see https://docs.graylog.org/docs/index-model#index-set-configuration 374elasticsearch_index_prefix = graylog 375 376# Name of the Elasticsearch index template used by Graylog to apply the mandatory index mapping. 377# Default: graylog-internal 378# 379# ATTENTION: These settings have been moved to the database in Graylog 2.2.0. When you upgrade, make sure to set these 380# to your previous settings so they will be migrated to the database! 381# This configuration setting is only used on the first start of Graylog. After that, 382# index related settings can be changed in the Graylog web interface on the 'System / Indices' page. 383# Also see https://docs.graylog.org/docs/index-model#index-set-configuration 384#elasticsearch_template_name = graylog-internal 385 386# Do you want to allow searches with leading wildcards? This can be extremely resource hungry and should only 387# be enabled with care. See also: https://docs.graylog.org/docs/query-language 388allow_leading_wildcard_searches = false 389 390# Do you want to allow searches to be highlighted? Depending on the size of your messages this can be memory hungry and 391# should only be enabled after making sure your Elasticsearch cluster has enough memory. 392allow_highlighting = false 393 394# Analyzer (tokenizer) to use for message and full_message field. The "standard" filter usually is a good idea. 395# All supported analyzers are: standard, simple, whitespace, stop, keyword, pattern, language, snowball, custom 396# Elasticsearch documentation: https://www.elastic.co/guide/en/elasticsearch/reference/2.3/analysis.html 397# Note that this setting only takes effect on newly created indices. 398# 399# ATTENTION: These settings have been moved to the database in Graylog 2.2.0. When you upgrade, make sure to set these 400# to your previous settings so they will be migrated to the database! 401# This configuration setting is only used on the first start of Graylog. After that, 402# index related settings can be changed in the Graylog web interface on the 'System / Indices' page. 403# Also see https://docs.graylog.org/docs/index-model#index-set-configuration 404elasticsearch_analyzer = standard 405 406# Global timeout for index optimization (force merge) requests. 407# Default: 1h 408#elasticsearch_index_optimization_timeout = 1h 409 410# Maximum number of concurrently running index optimization (force merge) jobs. 411# If you are using lots of different index sets, you might want to increase that number. 412# Default: 20 413#elasticsearch_index_optimization_jobs = 20 414 415# Mute the logging-output of ES deprecation warnings during REST calls in the ES RestClient 416#elasticsearch_mute_deprecation_warnings = true 417 418# Time interval for index range information cleanups. This setting defines how often stale index range information 419# is being purged from the database. 420# Default: 1h 421#index_ranges_cleanup_interval = 1h 422 423# Time interval for the job that runs index field type maintenance tasks like cleaning up stale entries. This doesn't 424# need to run very often. 425# Default: 1h 426#index_field_type_periodical_interval = 1h 427 428# Batch size for the Elasticsearch output. This is the maximum (!) number of messages the Elasticsearch output 429# module will get at once and write to Elasticsearch in a batch call. If the configured batch size has not been 430# reached within output_flush_interval seconds, everything that is available will be flushed at once. Remember 431# that every outputbuffer processor manages its own batch and performs its own batch write calls. 432# ("outputbuffer_processors" variable) 433output_batch_size = 500 434 435# Flush interval (in seconds) for the Elasticsearch output. This is the maximum amount of time between two 436# batches of messages written to Elasticsearch. It is only effective at all if your minimum number of messages 437# for this time period is less than output_batch_size * outputbuffer_processors. 438output_flush_interval = 1 439 440# As stream outputs are loaded only on demand, an output which is failing to initialize will be tried over and 441# over again. To prevent this, the following configuration options define after how many faults an output will 442# not be tried again for an also configurable amount of seconds. 443output_fault_count_threshold = 5 444output_fault_penalty_seconds = 30 445 446# The number of parallel running processors. 447# Raise this number if your buffers are filling up. 448processbuffer_processors = 5 449outputbuffer_processors = 3 450 451# The following settings (outputbuffer_processor_*) configure the thread pools backing each output buffer processor. 452# See https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/ThreadPoolExecutor.html for technical details 453 454# When the number of threads is greater than the core (see outputbuffer_processor_threads_core_pool_size), 455# this is the maximum time in milliseconds that excess idle threads will wait for new tasks before terminating. 456# Default: 5000 457#outputbuffer_processor_keep_alive_time = 5000 458 459# The number of threads to keep in the pool, even if they are idle, unless allowCoreThreadTimeOut is set 460# Default: 3 461#outputbuffer_processor_threads_core_pool_size = 3 462 463# The maximum number of threads to allow in the pool 464# Default: 30 465#outputbuffer_processor_threads_max_pool_size = 30 466 467# UDP receive buffer size for all message inputs (e. g. SyslogUDPInput). 468#udp_recvbuffer_sizes = 1048576 469 470# Wait strategy describing how buffer processors wait on a cursor sequence. (default: sleeping) 471# Possible types: 472# - yielding 473# Compromise between performance and CPU usage. 474# - sleeping 475# Compromise between performance and CPU usage. Latency spikes can occur after quiet periods. 476# - blocking 477# High throughput, low latency, higher CPU usage. 478# - busy_spinning 479# Avoids syscalls which could introduce latency jitter. Best when threads can be bound to specific CPU cores. 480processor_wait_strategy = blocking 481 482# Size of internal ring buffers. Raise this if raising outputbuffer_processors does not help anymore. 483# For optimum performance your LogMessage objects in the ring buffer should fit in your CPU L3 cache. 484# Must be a power of 2. (512, 1024, 2048, ...) 485ring_size = 65536 486 487inputbuffer_ring_size = 65536 488inputbuffer_processors = 2 489inputbuffer_wait_strategy = blocking 490 491# Enable the message journal. 492message_journal_enabled = true 493 494# The directory which will be used to store the message journal. The directory must be exclusively used by Graylog and 495# must not contain any other files than the ones created by Graylog itself. 496# 497# ATTENTION: 498# If you create a seperate partition for the journal files and use a file system creating directories like 'lost+found' 499# in the root directory, you need to create a sub directory for your journal. 500# Otherwise Graylog will log an error message that the journal is corrupt and Graylog will not start. 501message_journal_dir = /var/db/graylog/journal 502 503# Journal hold messages before they could be written to Elasticsearch. 504# For a maximum of 12 hours or 5 GB whichever happens first. 505# During normal operation the journal will be smaller. 506#message_journal_max_age = 12h 507#message_journal_max_size = 5gb 508 509#message_journal_flush_age = 1m 510#message_journal_flush_interval = 1000000 511#message_journal_segment_age = 1h 512#message_journal_segment_size = 100mb 513 514# Number of threads used exclusively for dispatching internal events. Default is 2. 515#async_eventbus_processors = 2 516 517# How many seconds to wait between marking node as DEAD for possible load balancers and starting the actual 518# shutdown process. Set to 0 if you have no status checking load balancers in front. 519lb_recognition_period_seconds = 3 520 521# Journal usage percentage that triggers requesting throttling for this server node from load balancers. The feature is 522# disabled if not set. 523#lb_throttle_threshold_percentage = 95 524 525# Every message is matched against the configured streams and it can happen that a stream contains rules which 526# take an unusual amount of time to run, for example if its using regular expressions that perform excessive backtracking. 527# This will impact the processing of the entire server. To keep such misbehaving stream rules from impacting other 528# streams, Graylog limits the execution time for each stream. 529# The default values are noted below, the timeout is in milliseconds. 530# If the stream matching for one stream took longer than the timeout value, and this happened more than "max_faults" times 531# that stream is disabled and a notification is shown in the web interface. 532#stream_processing_timeout = 2000 533#stream_processing_max_faults = 3 534 535# Since 0.21 the Graylog server supports pluggable output modules. This means a single message can be written to multiple 536# outputs. The next setting defines the timeout for a single output module, including the default output module where all 537# messages end up. 538# 539# Time in milliseconds to wait for all message outputs to finish writing a single message. 540#output_module_timeout = 10000 541 542# Time in milliseconds after which a detected stale master node is being rechecked on startup. 543#stale_master_timeout = 2000 544 545# Time in milliseconds which Graylog is waiting for all threads to stop on shutdown. 546#shutdown_timeout = 30000 547 548# MongoDB connection string 549# See https://docs.mongodb.com/manual/reference/connection-string/ for details 550mongodb_uri = mongodb://localhost/graylog 551 552# Authenticate against the MongoDB server 553# '+'-signs in the username or password need to be replaced by '%2B' 554#mongodb_uri = mongodb://grayloguser:secret@localhost:27017/graylog 555 556# Use a replica set instead of a single host 557#mongodb_uri = mongodb://grayloguser:secret@localhost:27017,localhost:27018,localhost:27019/graylog?replicaSet=rs01 558 559# DNS Seedlist https://docs.mongodb.com/manual/reference/connection-string/#dns-seedlist-connection-format 560#mongodb_uri = mongodb+srv://server.example.org/graylog 561 562# Increase this value according to the maximum connections your MongoDB server can handle from a single client 563# if you encounter MongoDB connection problems. 564mongodb_max_connections = 1000 565 566# Number of threads allowed to be blocked by MongoDB connections multiplier. Default: 5 567# If mongodb_max_connections is 100, and mongodb_threads_allowed_to_block_multiplier is 5, 568# then 500 threads can block. More than that and an exception will be thrown. 569# http://api.mongodb.com/java/current/com/mongodb/MongoOptions.html#threadsAllowedToBlockForConnectionMultiplier 570mongodb_threads_allowed_to_block_multiplier = 5 571 572 573# Email transport 574#transport_email_enabled = false 575#transport_email_hostname = mail.example.com 576#transport_email_port = 587 577#transport_email_use_auth = true 578#transport_email_auth_username = you@example.com 579#transport_email_auth_password = secret 580#transport_email_subject_prefix = [graylog] 581#transport_email_from_email = graylog@example.com 582 583# Encryption settings 584# 585# ATTENTION: 586# Using SMTP with STARTTLS *and* SMTPS at the same time is *not* possible. 587 588# Use SMTP with STARTTLS, see https://en.wikipedia.org/wiki/Opportunistic_TLS 589#transport_email_use_tls = true 590 591# Use SMTP over SSL (SMTPS), see https://en.wikipedia.org/wiki/SMTPS 592# This is deprecated on most SMTP services! 593#transport_email_use_ssl = false 594 595 596# Specify and uncomment this if you want to include links to the stream in your stream alert mails. 597# This should define the fully qualified base url to your web interface exactly the same way as it is accessed by your users. 598#transport_email_web_interface_url = https://graylog.example.com 599 600# The default connect timeout for outgoing HTTP connections. 601# Values must be a positive duration (and between 1 and 2147483647 when converted to milliseconds). 602# Default: 5s 603#http_connect_timeout = 5s 604 605# The default read timeout for outgoing HTTP connections. 606# Values must be a positive duration (and between 1 and 2147483647 when converted to milliseconds). 607# Default: 10s 608#http_read_timeout = 10s 609 610# The default write timeout for outgoing HTTP connections. 611# Values must be a positive duration (and between 1 and 2147483647 when converted to milliseconds). 612# Default: 10s 613#http_write_timeout = 10s 614 615# HTTP proxy for outgoing HTTP connections 616# ATTENTION: If you configure a proxy, make sure to also configure the "http_non_proxy_hosts" option so internal 617# HTTP connections with other nodes does not go through the proxy. 618# Examples: 619# - http://proxy.example.com:8123 620# - http://username:password@proxy.example.com:8123 621#http_proxy_uri = 622 623# A list of hosts that should be reached directly, bypassing the configured proxy server. 624# This is a list of patterns separated by ",". The patterns may start or end with a "*" for wildcards. 625# Any host matching one of these patterns will be reached through a direct connection instead of through a proxy. 626# Examples: 627# - localhost,127.0.0.1 628# - 10.0.*,*.example.com 629#http_non_proxy_hosts = 630 631# Disable the optimization of Elasticsearch indices after index cycling. This may take some load from Elasticsearch 632# on heavily used systems with large indices, but it will decrease search performance. The default is to optimize 633# cycled indices. 634# 635# ATTENTION: These settings have been moved to the database in Graylog 2.2.0. When you upgrade, make sure to set these 636# to your previous settings so they will be migrated to the database! 637# This configuration setting is only used on the first start of Graylog. After that, 638# index related settings can be changed in the Graylog web interface on the 'System / Indices' page. 639# Also see https://docs.graylog.org/docs/index-model#index-set-configuration 640#disable_index_optimization = true 641 642# Optimize the index down to <= index_optimization_max_num_segments. A higher number may take some load from Elasticsearch 643# on heavily used systems with large indices, but it will decrease search performance. The default is 1. 644# 645# ATTENTION: These settings have been moved to the database in Graylog 2.2.0. When you upgrade, make sure to set these 646# to your previous settings so they will be migrated to the database! 647# This configuration setting is only used on the first start of Graylog. After that, 648# index related settings can be changed in the Graylog web interface on the 'System / Indices' page. 649# Also see https://docs.graylog.org/docs/index-model#index-set-configuration 650#index_optimization_max_num_segments = 1 651 652# The threshold of the garbage collection runs. If GC runs take longer than this threshold, a system notification 653# will be generated to warn the administrator about possible problems with the system. Default is 1 second. 654#gc_warning_threshold = 1s 655 656# Connection timeout for a configured LDAP server (e. g. ActiveDirectory) in milliseconds. 657#ldap_connection_timeout = 2000 658 659# Disable the use of a native system stats collector (currently OSHI) 660#disable_native_system_stats_collector = false 661 662# The default cache time for dashboard widgets. (Default: 10 seconds, minimum: 1 second) 663#dashboard_widget_default_cache_time = 10s 664 665# For some cluster-related REST requests, the node must query all other nodes in the cluster. This is the maximum number 666# of threads available for this. Increase it, if '/cluster/*' requests take long to complete. 667# Should be http_thread_pool_size * average_cluster_size if you have a high number of concurrent users. 668proxied_requests_thread_pool_size = 32 669 670# The server is writing processing status information to the database on a regular basis. This setting controls how 671# often the data is written to the database. 672# Default: 1s (cannot be less than 1s) 673#processing_status_persist_interval = 1s 674 675# Configures the threshold for detecting outdated processing status records. Any records that haven't been updated 676# in the configured threshold will be ignored. 677# Default: 1m (one minute) 678#processing_status_update_threshold = 1m 679 680# Configures the journal write rate threshold for selecting processing status records. Any records that have a lower 681# one minute rate than the configured value might be ignored. (dependent on number of messages in the journal) 682# Default: 1 683#processing_status_journal_write_rate_threshold = 1 684 685# Configures the prefix used for graylog event indices 686# Default: gl-events 687#default_events_index_prefix = gl-events 688 689# Configures the prefix used for graylog system event indices 690# Default: gl-system-events 691#default_system_events_index_prefix = gl-system-events 692 693# Automatically load content packs in "content_packs_dir" on the first start of Graylog. 694#content_packs_loader_enabled = false 695 696# The directory which contains content packs which should be loaded on the first start of Graylog. 697#content_packs_dir = data/contentpacks 698 699# A comma-separated list of content packs (files in "content_packs_dir") which should be applied on 700# the first start of Graylog. 701# Default: empty 702#content_packs_auto_install = grok-patterns.json 703 704# The allowed TLS protocols for system wide TLS enabled servers. (e.g. message inputs, http interface) 705# Setting this to an empty value, leaves it up to system libraries and the used JDK to chose a default. 706# Default: TLSv1.2,TLSv1.3 (might be automatically adjusted to protocols supported by the JDK) 707#enabled_tls_protocols= TLSv1.2,TLSv1.3 708 709# Enable Prometheus exporter HTTP server. 710# Default: false 711#prometheus_exporter_enabled = false 712 713# IP address and port for the Prometheus exporter HTTP server. 714# Default: 127.0.0.1:9833 715#prometheus_exporter_bind_address = 127.0.0.1:9833 716 717# Path to the Prometheus exporter core mapping file. If this option is enabled, the full built-in core mapping is 718# replaced with the mappings in this file. 719# This file is monitored for changes and updates will be applied at runtime. 720# Default: none 721#prometheus_exporter_mapping_file_path_core = prometheus-exporter-mapping-core.yml 722 723# Path to the Prometheus exporter custom mapping file. If this option is enabled, the mappings in this file are 724# configured in addition to the built-in core mappings. The mappings in this file cannot overwrite any core mappings. 725# This file is monitored for changes and updates will be applied at runtime. 726# Default: none 727#prometheus_exporter_mapping_file_path_custom = prometheus-exporter-mapping-custom.yml 728 729# Configures the refresh interval for the monitored Prometheus exporter mapping files. 730# Default: 60s 731#prometheus_exporter_mapping_file_refresh_interval = 60s 732 733# Optional allowed paths for Graylog data files. If provided, certain operations in Graylog will only be permitted 734# if the data file(s) are located in the specified paths (for example, with the CSV File lookup adapter). 735# All subdirectories of indicated paths are allowed by default. This Provides an additional layer of security, 736# and allows administrators to control where in the file system Graylog users can select files from. 737#allowed_auxiliary_paths = /etc/graylog/data-files,/etc/custom-allowed-path 738