Advertisement
Guest User

Untitled

a guest
Jul 1st, 2016
48
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 31.85 KB | None | 0 0
  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.
  3. is_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.
  7. node_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
  11. password_secret = lwk4afk6z6gNsXLFDMYS6LnqXvNNBkisusG4dCYtqd5RrupIIjv2V6EefTFcUxEZsrds8GZbySBjVg13IViDypkSd6uud3WM
  12.  
  13. # The default root user is named 'admin'
  14. root_username = gaian
  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
  22. root_password_sha2 = 5e884898da28047151d0e56f8dc6292773603d0d6aabbdd62a11ef721d1542d8
  23.  
  24. # The email address of the root user.
  25. # Default is empty
  26. root_email = "raghavenderreddy.bathini@gaiansolutions.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
  30. #root_timezone = UTC
  31.  
  32. # Set plugin directory here (relative or absolute)
  33. plugin_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.
  37. rest_listen_uri = http://192.168.25.224:12900/
  38. rest_listen_uri = http://192.168.25.224:12900/
  39.  
  40. # REST API transport address. Defaults to the value of rest_listen_uri. Exception: If rest_listen_uri
  41. # is set to a wildcard IP address (0.0.0.0) the first non-loopback IPv4 system address is used.
  42. # If set, this will be promoted in the cluster discovery APIs, so other nodes may try to connect on
  43. # this address and it is used to generate URLs addressing entities in the REST API. (see rest_listen_uri)
  44. # You will need to define this, if your Graylog server is running behind a HTTP proxy that is rewriting
  45. # the scheme, host name or URI.
  46. # This must not contain a wildcard address (0.0.0.0).
  47. rest_transport_uri = http://192.168.25.224:12900/
  48.  
  49. # Enable CORS headers for REST API. This is necessary for JS-clients accessing the server directly.
  50. # If these are disabled, modern browsers will not be able to retrieve resources from the server.
  51. # This is enabled by default. Uncomment the next line to disable it.
  52. #rest_enable_cors = false
  53.  
  54. # Enable GZIP support for REST API. This compresses API responses and therefore helps to reduce
  55. # overall round trip times. This is disabled by default. Uncomment the next line to enable it.
  56. #rest_enable_gzip = true
  57.  
  58. # Enable HTTPS support for the REST API. This secures the communication with the REST API with
  59. # TLS to prevent request forgery and eavesdropping. This is disabled by default. Uncomment the
  60. # next line to enable it.
  61. #rest_enable_tls = true
  62.  
  63. # The X.509 certificate chain file in PEM format to use for securing the REST API.
  64. #rest_tls_cert_file = /path/to/graylog.crt
  65.  
  66. # The PKCS#8 private key file in PEM format to use for securing the REST API.
  67. #rest_tls_key_file = /path/to/graylog.key
  68.  
  69. # The password to unlock the private key used for securing the REST API.
  70. #rest_tls_key_password = secret
  71.  
  72. # The maximum size of the HTTP request headers in bytes.
  73. #rest_max_header_size = 8192
  74.  
  75. # The maximal length of the initial HTTP/1.1 line in bytes.
  76.  
  77. # The maximal length of the initial HTTP/1.1 line in bytes.
  78. #rest_max_initial_line_length = 4096
  79.  
  80. # The size of the thread pool used exclusively for serving the REST API.
  81. #rest_thread_pool_size = 16
  82.  
  83. # Enable the embedded Graylog web interface.
  84. # Default: true
  85. #web_enable = false
  86.  
  87. # Web interface listen URI. It must not contain a path other than "/".
  88. web_listen_uri = http://192.168.25.224:9000/
  89.  
  90. # Web interface endpoint URI. This setting can be overriden on a per-request basis with the X-Graylog-Server-URL header.
  91. # Default: $rest_transport_uri
  92. web_endpoint_uri = http://192.168.25.224:9000/
  93.  
  94. # Enable CORS headers for the web interface. This is necessary for JS-clients accessing the server directly.
  95. # If these are disabled, modern browsers will not be able to retrieve resources from the server.
  96. #web_enable_cors = false
  97.  
  98. # Enable/disable GZIP support for the web interface. This compresses HTTP responses and therefore helps to reduce
  99. # overall round trip times. This is enabled by default. Uncomment the next line to disable it.
  100. #web_enable_gzip = false
  101.  
  102. # Enable HTTPS support for the web interface. This secures the communication of the web browser with the web interface
  103. # using TLS to prevent request forgery and eavesdropping.
  104. # This is disabled by default. Uncomment the next line to enable it and see the other related configuration settings.
  105. #web_enable_tls = true
  106.  
  107. # The X.509 certificate chain file in PEM format to use for securing the web interface.
  108. #web_tls_cert_file = /path/to/graylog-web.crt
  109.  
  110. # The PKCS#8 private key file in PEM format to use for securing the web interface.
  111. #web_tls_key_file = /path/to/graylog-web.key
  112.  
  113. # The password to unlock the private key used for securing the web interface.
  114. Type :quit<Enter> to exit Vim 73,0-1 14%
  115.  
  116. # The password to unlock the private key used for securing the web interface.
  117. #web_tls_key_password = secret
  118.  
  119. # The maximum size of the HTTP request headers in bytes.
  120. #web_max_header_size = 8192
  121.  
  122. # The maximal length of the initial HTTP/1.1 line in bytes.
  123. #web_max_initial_line_length = 4096
  124.  
  125. # The size of the thread pool used exclusively for serving the web interface.
  126. #web_thread_pool_size = 16
  127.  
  128. # Configuration file for the embedded Elasticsearch instance in Graylog.
  129. # Pay attention to the working directory of the server, maybe use an absolute path here.
  130. # Default: empty
  131. #elasticsearch_config_file = /etc/graylog/server/elasticsearch.yml
  132.  
  133. # Graylog will use multiple indices to store documents in. You can configured the strategy it uses to determine
  134. # when to rotate the currently active write index.
  135. # It supports multiple rotation strategies:
  136. # - "count" of messages per index, use elasticsearch_max_docs_per_index below to configure
  137. # - "size" per index, use elasticsearch_max_size_per_index below to configure
  138. # valid values are "count", "size" and "time", default is "count"
  139. #
  140. # ATTENTION: These settings have been moved to the database in 2.0. When you upgrade, make sure to set these
  141. # to your previous 1.x settings so they will be migrated to the database!
  142. rotation_strategy = count
  143.  
  144. # (Approximate) maximum number of documents in an Elasticsearch index before a new index
  145. # is being created, also see no_retention and elasticsearch_max_number_of_indices.
  146. # Configure this if you used 'rotation_strategy = count' above.
  147. #
  148. # ATTENTION: These settings have been moved to the database in 2.0. When you upgrade, make sure to set these
  149. # to your previous 1.x settings so they will be migrated to the database!
  150. elasticsearch_max_docs_per_index = 20000000
  151.  
  152. # (Approximate) maximum size in bytes per Elasticsearch index on disk before a new index is being created, also see
  153. 109,0-1 22%
  154.  
  155. # (Approximate) maximum size in bytes per Elasticsearch index on disk before a new index is being created, also see
  156. # no_retention and elasticsearch_max_number_of_indices. Default is 1GB.
  157. # Configure this if you used 'rotation_strategy = size' above.
  158. #
  159. # ATTENTION: These settings have been moved to the database in 2.0. When you upgrade, make sure to set these
  160. # to your previous 1.x settings so they will be migrated to the database!
  161. #elasticsearch_max_size_per_index = 1073741824
  162.  
  163. # (Approximate) maximum time before a new Elasticsearch index is being created, also see
  164. # no_retention and elasticsearch_max_number_of_indices. Default is 1 day.
  165. # Configure this if you used 'rotation_strategy = time' above.
  166. # Please note that this rotation period does not look at the time specified in the received messages, but is
  167. # using the real clock value to decide when to rotate the index!
  168. # Specify the time using a duration and a suffix indicating which unit you want:
  169. # 1w = 1 week
  170. # 1d = 1 day
  171. # 12h = 12 hours
  172. # Permitted suffixes are: d for day, h for hour, m for minute, s for second.
  173. #
  174. # ATTENTION: These settings have been moved to the database in 2.0. When you upgrade, make sure to set these
  175. # to your previous 1.x settings so they will be migrated to the database!
  176. #elasticsearch_max_time_per_index = 1d
  177.  
  178. # Graylog will use multiple indices to store documents in. You can configured the strategy it uses to determine
  179. # when to rotate the currently active write index.
  180. # It supports multiple rotation strategies:
  181. # - "count" of messages per index, use elasticsearch_max_docs_per_index below to configure
  182. # - "size" per index, use elasticsearch_max_size_per_index below to configure
  183. # valid values are "count", "size" and "time", default is "count"
  184. #
  185. # ATTENTION: These settings have been moved to the database in 2.0. When you upgrade, make sure to set these
  186. # to your previous 1.x settings so they will be migrated to the database!
  187. rotation_strategy = count
  188.  
  189. # (Approximate) maximum number of documents in an Elasticsearch index before a new index
  190. # is being created, also see no_retention and elasticsearch_max_number_of_indices.
  191. # Configure this if you used 'rotation_strategy = count' above.
  192. 145,0-1 29%
  193. # is being created, also see no_retention and elasticsearch_max_number_of_indices.
  194. # Configure this if you used 'rotation_strategy = count' above.
  195. #
  196. # ATTENTION: These settings have been moved to the database in 2.0. When you upgrade, make sure to set these
  197. # to your previous 1.x settings so they will be migrated to the database!
  198. elasticsearch_max_docs_per_index = 20000000
  199.  
  200. # (Approximate) maximum size in bytes per Elasticsearch index on disk before a new index is being created, also see
  201. # no_retention and elasticsearch_max_number_of_indices. Default is 1GB.
  202. # Configure this if you used 'rotation_strategy = size' above.
  203. #
  204. # ATTENTION: These settings have been moved to the database in 2.0. When you upgrade, make sure to set these
  205. # to your previous 1.x settings so they will be migrated to the database!
  206. #elasticsearch_max_size_per_index = 1073741824
  207.  
  208. # (Approximate) maximum time before a new Elasticsearch index is being created, also see
  209. # no_retention and elasticsearch_max_number_of_indices. Default is 1 day.
  210. # Configure this if you used 'rotation_strategy = time' above.
  211. # Please note that this rotation period does not look at the time specified in the received messages, but is
  212. # using the real clock value to decide when to rotate the index!
  213. # Specify the time using a duration and a suffix indicating which unit you want:
  214. # 1w = 1 week
  215. # 1d = 1 day
  216. # 12h = 12 hours
  217. # Permitted suffixes are: d for day, h for hour, m for minute, s for second.
  218. #
  219. # ATTENTION: These settings have been moved to the database in 2.0. When you upgrade, make sure to set these
  220. # to your previous 1.x settings so they will be migrated to the database!
  221. #elasticsearch_max_time_per_index = 1d
  222.  
  223. # Disable checking the version of Elasticsearch for being compatible with this Graylog release.
  224. # WARNING: Using Graylog with unsupported and untested versions of Elasticsearch may lead to data loss!
  225. #elasticsearch_disable_version_check = true
  226.  
  227. # Disable message retention on this node, i. e. disable Elasticsearch index rotation.
  228. #no_retention = false
  229.  
  230. # How many indices do you want to keep?
  231. 181,1 36%
  232.  
  233. # How many indices do you want to keep?
  234. #
  235. # ATTENTION: These settings have been moved to the database in 2.0. When you upgrade, make sure to set these
  236. # to your previous 1.x settings so they will be migrated to the database!
  237. elasticsearch_max_number_of_indices = 20
  238.  
  239. # Decide what happens with the oldest indices when the maximum number of indices is reached.
  240. # The following strategies are availble:
  241. # - delete # Deletes the index completely (Default)
  242. # - close # Closes the index and hides it from the system. Can be re-opened later.
  243. #
  244. # ATTENTION: These settings have been moved to the database in 2.0. When you upgrade, make sure to set these
  245. # to your previous 1.x settings so they will be migrated to the database!
  246. retention_strategy = delete
  247.  
  248. # How many indices do you want to keep?
  249. #
  250. # ATTENTION: These settings have been moved to the database in 2.0. When you upgrade, make sure to set these
  251. # to your previous 1.x settings so they will be migrated to the database!
  252. elasticsearch_max_number_of_indices = 20
  253.  
  254. # Decide what happens with the oldest indices when the maximum number of indices is reached.
  255. # The following strategies are availble:
  256. # - delete # Deletes the index completely (Default)
  257. # - close # Closes the index and hides it from the system. Can be re-opened later.
  258. #
  259. # ATTENTION: These settings have been moved to the database in 2.0. When you upgrade, make sure to set these
  260. # to your previous 1.x settings so they will be migrated to the database!
  261. retention_strategy = delete
  262.  
  263. # How many Elasticsearch shards and replicas should be used per index? Note that this only applies to newly created indices.
  264. elasticsearch_shards = 1
  265. elasticsearch_replicas = 0
  266.  
  267. # Prefix for all Elasticsearch indices and index aliases managed by Graylog.
  268. elasticsearch_index_prefix = graylog
  269.  
  270. 217,0-1 44%
  271. elasticsearch_index_prefix = graylog
  272.  
  273. # Name of the Elasticsearch index template used by Graylog to apply the mandatory index mapping.
  274. # # Default: graylog-internal
  275. #elasticsearch_template_name = graylog-internal
  276.  
  277. # Do you want to allow searches with leading wildcards? This can be extremely resource hungry and should only
  278. # be enabled with care. See also: https://www.graylog.org/documentation/general/queries/
  279. allow_leading_wildcard_searches = false
  280.  
  281. # Do you want to allow searches to be highlighted? Depending on the size of your messages this can be memory hungry and
  282. # should only be enabled after making sure your Elasticsearch cluster has enough memory.
  283. allow_highlighting = false
  284.  
  285. # settings to be passed to elasticsearch's client (overriding those in the provided elasticsearch_config_file)
  286. # all these
  287. # this must be the same as for your Elasticsearch cluster
  288. #elasticsearch_cluster_name = graylog
  289.  
  290. # The prefix being used to generate the Elasticsearch node name which makes it easier to identify the specific Graylog
  291. # server running the embedded Elasticsearch instance. The node name will be constructed by concatenating this prefix
  292. # and the Graylog node ID (see node_id_file), for example "graylog-17052010-1234-5678-abcd-1337cafebabe".
  293. # Default: graylog-
  294. #elasticsearch_node_name_prefix = graylog-
  295.  
  296. # A comma-separated list of Elasticsearch nodes which Graylog is using to connect to the Elasticsearch cluster,
  297. # see https://www.elastic.co/guide/en/elasticsearch/reference/2.3/modules-discovery-zen.html for details.
  298. # Default: 127.0.0.1
  299. #elasticsearch_discovery_zen_ping_unicast_hosts = 127.0.0.1:9300, 127.0.0.2:9500
  300.  
  301. # we don't want the Graylog server to store any data, or be master node
  302. #elasticsearch_node_master = false
  303. #elasticsearch_node_data = false
  304.  
  305. # use a different port if you run multiple Elasticsearch nodes on one machine
  306. #elasticsearch_transport_tcp_port = 9350
  307.  
  308. # we don't need to run the embedded HTTP server here
  309. 253,1 51%
  310.  
  311. # we don't need to run the embedded HTTP server here
  312. #elasticsearch_http_enabled = false
  313.  
  314. # Enable Elasticsearch multicast discovery. This requires the installation of an Elasticsearch plugin,
  315. # see https://www.elastic.co/guide/en/elasticsearch/plugins/2.3/discovery-multicast.html for details.
  316. # Default: false
  317. #elasticsearch_discovery_zen_ping_multicast_enabled = false
  318.  
  319. # Change the following setting if you are running into problems with timeouts during Elasticsearch cluster discovery.
  320. # The setting is specified in milliseconds, the default is 5000ms (5 seconds).
  321. #elasticsearch_cluster_discovery_timeout = 5000
  322.  
  323. # the following settings allow to change the bind addresses for the Elasticsearch client in Graylog
  324. # these settings are empty by default, letting Elasticsearch choose automatically,
  325. # override them here or in the 'elasticsearch_config_file' if you need to bind to a special address
  326. # refer to http://www.elasticsearch.org/guide/en/elasticsearch/reference/0.90/modules-network.html
  327. # for special values here
  328. #elasticsearch_network_host =
  329. #elasticsearch_network_bind_host =
  330. #elasticsearch_network_publish_host =
  331.  
  332. # The total amount of time discovery will look for other Elasticsearch nodes in the cluster
  333. # before giving up and declaring the current node master.
  334. #elasticsearch_discovery_initial_state_timeout = 3s
  335.  
  336. # Analyzer (tokenizer) to use for message and full_message field. The "standard" filter usually is a good idea.
  337. # All supported analyzers are: standard, simple, whitespace, stop, keyword, pattern, language, snowball, custom
  338. # Elasticsearch documentation: http://www.elasticsearch.org/guide/reference/index-modules/analysis/
  339. # Note that this setting only takes effect on newly created indices.
  340. elasticsearch_analyzer = standard
  341.  
  342. # Global request timeout for Elasticsearch requests (e. g. during search, index creation, or index time-range
  343. # calculations) based on a best-effort to restrict the runtime of Elasticsearch operations.
  344. # Default: 1m
  345. #elasticsearch_request_timeout = 1m
  346.  
  347. # Time interval for index range information cleanups. This setting defines how often stale index range information
  348. 289,0-1 58%
  349.  
  350. # Time interval for index range information cleanups. This setting defines how often stale index range information
  351. # is being purged from the database.
  352. # Default: 1h
  353. #index_ranges_cleanup_interval = 1h
  354.  
  355. # Batch size for the Elasticsearch output. This is the maximum (!) number of messages the Elasticsearch output
  356. # module will get at once and write to Elasticsearch in a batch call. If the configured batch size has not been
  357. # reached within output_flush_interval seconds, everything that is available will be flushed at once. Remember
  358. # that every outputbuffer processor manages its own batch and performs its own batch write calls.
  359. # ("outputbuffer_processors" variable)
  360. output_batch_size = 500
  361.  
  362. # Flush interval (in seconds) for the Elasticsearch output. This is the maximum amount of time between two
  363. # batches of messages written to Elasticsearch. It is only effective at all if your minimum number of messages
  364. # for this time period is less than output_batch_size * outputbuffer_processors.
  365. output_flush_interval = 1
  366.  
  367. # As stream outputs are loaded only on demand, an output which is failing to initialize will be tried over and
  368. # over again. To prevent this, the following configuration options define after how many faults an output will
  369. # not be tried again for an also configurable amount of seconds.
  370. output_fault_count_threshold = 5
  371. output_fault_penalty_seconds = 30
  372.  
  373. # The number of parallel running processors.
  374. # Raise this number if your buffers are filling up.
  375. processbuffer_processors = 5
  376. outputbuffer_processors = 3
  377.  
  378. #outputbuffer_processor_keep_alive_time = 5000
  379. #outputbuffer_processor_threads_core_pool_size = 3
  380. #outputbuffer_processor_threads_max_pool_size = 30
  381.  
  382. # UDP receive buffer size for all message inputs (e. g. SyslogUDPInput).
  383. #udp_recvbuffer_sizes = 1048576
  384.  
  385. # Wait strategy describing how buffer processors wait on a cursor sequence. (default: sleeping)
  386. # Possible types:
  387. 325,0-1 66%
  388. # Wait strategy describing how buffer processors wait on a cursor sequence. (default: sleeping)
  389. # Possible types:
  390. # - yielding
  391. # Compromise between performance and CPU usage.
  392. # - sleeping
  393. # Compromise between performance and CPU usage. Latency spikes can occur after quiet periods.
  394. # - blocking
  395. # High throughput, low latency, higher CPU usage.
  396. # - busy_spinning
  397. # Avoids syscalls which could introduce latency jitter. Best when threads can be bound to specific CPU cores.
  398. processor_wait_strategy = blocking
  399.  
  400. # Size of internal ring buffers. Raise this if raising outputbuffer_processors does not help anymore.
  401. # For optimum performance your LogMessage objects in the ring buffer should fit in your CPU L3 cache.
  402. # Must be a power of 2. (512, 1024, 2048, ...)
  403. ring_size = 65536
  404.  
  405. inputbuffer_ring_size = 65536
  406. inputbuffer_processors = 2
  407. inputbuffer_wait_strategy = blocking
  408.  
  409. # Enable the disk based message journal.
  410. message_journal_enabled = true
  411.  
  412. # The directory which will be used to store the message journal. The directory must me exclusively used by Graylog and
  413. # must not contain any other files than the ones created by Graylog itself.
  414. message_journal_dir = /var/lib/graylog-server/journal
  415.  
  416. # Journal hold messages before they could be written to Elasticsearch.
  417. # For a maximum of 12 hours or 5 GB whichever happens first.
  418. # During normal operation the journal will be smaller.
  419. #message_journal_max_age = 12h
  420. #message_journal_max_size = 5gb
  421.  
  422. #message_journal_flush_age = 1m
  423. #message_journal_flush_interval = 1000000
  424. #message_journal_segment_age = 1h
  425. #message_journal_segment_size = 100mb
  426. 361,1 73%
  427. #message_journal_segment_age = 1h
  428. #message_journal_segment_size = 100mb
  429.  
  430. # Number of threads used exclusively for dispatching internal events. Default is 2.
  431. #async_eventbus_processors = 2
  432.  
  433. # How many seconds to wait between marking node as DEAD for possible load balancers and starting the actual
  434. # shutdown process. Set to 0 if you have no status checking load balancers in front.
  435. lb_recognition_period_seconds = 3
  436.  
  437. # Every message is matched against the configured streams and it can happen that a stream contains rules which
  438. # take an unusual amount of time to run, for example if its using regular expressions that perform excessive backtracking.
  439. # This will impact the processing of the entire server. To keep such misbehaving stream rules from impacting other
  440. # streams, Graylog limits the execution time for each stream.
  441. # The default values are noted below, the timeout is in milliseconds.
  442. # If the stream matching for one stream took longer than the timeout value, and this happened more than "max_faults" times
  443. # that stream is disabled and a notification is shown in the web interface.
  444. #stream_processing_timeout = 2000
  445. #stream_processing_max_faults = 3
  446.  
  447. # Length of the interval in seconds in which the alert conditions for all streams should be checked
  448. # and alarms are being sent.
  449. #alert_check_interval = 60
  450.  
  451. # Since 0.21 the Graylog server supports pluggable output modules. This means a single message can be written to multiple
  452. # outputs. The next setting defines the timeout for a single output module, including the default output module where all
  453. # messages end up.
  454. #
  455. # Time in milliseconds to wait for all message outputs to finish writing a single message.
  456. #output_module_timeout = 10000
  457.  
  458. # Time in milliseconds after which a detected stale master node is being rechecked on startup.
  459. #stale_master_timeout = 2000
  460.  
  461. # Time in milliseconds which Graylog is waiting for all threads to stop on shutdown.
  462. #shutdown_timeout = 30000
  463.  
  464. # MongoDB connection string
  465. 397,1 80%
  466.  
  467. # MongoDB connection string
  468. # See http://docs.mongodb.org/manual/reference/connection-string/ for details
  469. mongodb_uri = mongodb://localhost/graylog
  470.  
  471. # Authenticate against the MongoDB server
  472. #mongodb_uri = mongodb://grayloguser:secret@localhost:27017/graylog
  473.  
  474. # Use a replica set instead of a single host
  475. #mongodb_uri = mongodb://grayloguser:secret@localhost:27017,localhost:27018,localhost:27019/graylog
  476.  
  477. # Increase this value according to the maximum connections your MongoDB server can handle from a single client
  478. # if you encounter MongoDB connection problems.
  479. mongodb_max_connections = 1000
  480.  
  481. # Number of threads allowed to be blocked by MongoDB connections multiplier. Default: 5
  482. # If mongodb_max_connections is 100, and mongodb_threads_allowed_to_block_multiplier is 5,
  483. # then 500 threads can block. More than that and an exception will be thrown.
  484. # http://api.mongodb.org/java/current/com/mongodb/MongoOptions.html#threadsAllowedToBlockForConnectionMultiplier
  485. mongodb_threads_allowed_to_block_multiplier = 5
  486.  
  487. # Drools Rule File (Use to rewrite incoming log messages)
  488. # See: https://www.graylog.org/documentation/general/rewriting/
  489. #rules_file = /etc/graylog/server/rules.drl
  490.  
  491. # Email transport
  492. transport_email_enabled = true
  493. transport_email_hostname = smtp.gmail.com
  494. transport_email_port = 465
  495. transport_email_use_auth = true
  496. transport_email_use_tls = true
  497. transport_email_use_ssl = true
  498. transport_email_auth_username =
  499. # Specify and uncomment this if you want to include links to the stream in your stream alert mails.
  500. # This should define the fully qualified base url to your web interface exactly the same way as it is accessed by your users.
  501. transport_email_web_interface_url = https://192.168.25.224:9000
  502.  
  503. # The default connect timeout for outgoing HTTP connections.
  504. # Values must be a positive duration (and between 1 and 2147483647 when converted to milliseconds).
  505. # Default: 5s
  506. #http_connect_timeout = 5s
  507.  
  508. # The default read timeout for outgoing HTTP connections.
  509. # Values must be a positive duration (and between 1 and 2147483647 when converted to milliseconds).
  510. # Default: 10s
  511. #http_read_timeout = 10s
  512.  
  513. # The default write timeout for outgoing HTTP connections.
  514. # Values must be a positive duration (and between 1 and 2147483647 when converted to milliseconds).
  515. # Default: 10s
  516. #http_write_timeout = 10s
  517.  
  518. # HTTP proxy for outgoing HTTP connections
  519. #http_proxy_uri =
  520.  
  521. # Disable the optimization of Elasticsearch indices after index cycling. This may take some load from Elasticsearch
  522. # on heavily used systems with large indices, but it will decrease search performance. The default is to optimize
  523. # cycled indices.
  524. #disable_index_optimization = true
  525.  
  526. # Optimize the index down to <= index_optimization_max_num_segments. A higher number may take some load from Elasticsearch
  527. # on heavily used systems with large indices, but it will decrease search performance. The default is 1.
  528. #index_optimization_max_num_segments = 1
  529.  
  530. # The threshold of the garbage collection runs. If GC runs take longer than this threshold, a system notification
  531. # will be generated to warn the administrator about possible problems with the system. Default is 1 second.
  532. #gc_warning_threshold = 1s
  533.  
  534. # Connection timeout for a configured LDAP server (e. g. ActiveDirectory) in milliseconds.
  535. #ldap_connection_timeout = 2000
  536. 469,0-1 95%
  537. # Connection timeout for a configured LDAP server (e. g. ActiveDirectory) in milliseconds.
  538. #ldap_connection_timeout = 2000
  539.  
  540. # Enable collection of Graylog-related metrics into MongoDB
  541. # WARNING: This will add *a lot* of data into your MongoDB database on a regular interval (1 second)!
  542. # DEPRECATED: This setting and the respective feature will be removed in a future version of Graylog.
  543. #enable_metrics_collection = false
  544.  
  545. # Disable the use of SIGAR for collecting system stats
  546. #disable_sigar = false
  547.  
  548. # The default cache time for dashboard widgets. (Default: 10 seconds, minimum: 1 second)
  549. #dashboard_widget_default_cache_time = 10s
  550.  
  551. # Automatically load content packs in "content_packs_dir" on the first start of Graylog.
  552. #content_packs_loader_enabled = true
  553.  
  554. # The directory which contains content packs which should be loaded on the first start of Graylog.
  555. content_packs_dir = /usr/share/graylog-server/contentpacks
  556.  
  557. # A comma-separated list of content packs (files in "content_packs_dir") which should be applied on
  558. # the first start of Graylog.
  559. # Default: empty
  560. content_packs_auto_load = grok-patterns.json
  561. ~
  562. ~
  563. ~
  564. ~
  565. ~
  566. ~
  567. ~
  568. ~
  569. ~
  570. ~
  571. ~
  572. ~
  573. ~
  574. ~
  575. 505,1 Bot
  576.  
  577. transport_email_auth_password =
  578. transport_email_subject_prefix = [test]
  579. #transport_email_from_email = graylog@example.com
  580.  
  581. # Specify and uncomment this if you want to include links to the stream in your stream alert mails.
  582. 433,0-1 88%
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement