comparison Kibana-external-config-patch @ 26:610835fb4209

external configuration for kibana
author Carl Byington <carl@five-ten-sg.com>
date Fri, 03 May 2013 08:04:08 -0700
parents
children
comparison
equal deleted inserted replaced
25:d058481276aa 26:610835fb4209
1 --- KibanaConfig.rb 2013-05-02 15:22:03.011877891 -0700
2 +++ KibanaConfig.new.rb 2013-05-02 15:26:57.419447970 -0700
3 @@ -3,26 +3,14 @@
4 # Your elastic search server(s). This may be set as an array for round robin
5 # load balancing
6 # Elasticsearch = ["elasticsearch1:9200","elasticsearch2:9200"]
7 - Elasticsearch = "localhost:9200"
8 + Elasticsearch = ENV['KIBANA_ES'] ? ENV['KIBANA_ES'] : "localhost:9200"
9
10 #Set the Net::HTTP read/open timeouts for the connection to the ES backend
11 ElasticsearchTimeout = 500
12
13 - # The port Kibana should listen on
14 - KibanaPort = 5601
15 -
16 - # The adress ip Kibana should listen on. Comment out or set to
17 - # 0.0.0.0 to listen on all interfaces.
18 - KibanaHost = '127.0.0.1'
19 -
20 - # Below is an example showing how to configure the same variables
21 - # using environment variables, which can be set in an init script
22 - # es_ip = ENV['ES_IP'] ? ENV['ES_IP'] : '127.0.0.1'
23 - # es_port = ENV['ES_PORT'] ? ENV['ES_PORT'] : 9200
24 - # Elasticsearch = "#{es_ip}:#{es_port}"
25 - # KibanaPort = ENV['KIBANA_PORT'] ? ENV['KIBANA_PORT'] : 5601
26 - # KibanaHost = ENV['KIBANA_HOST'] ? ENV['KIBANA_HOST'] : 'localhost'
27 -
28 + # The port and adress ip Kibana should listen on.
29 + KibanaPort = ENV['KIBANA_PORT'] ? ENV['KIBANA_PORT'] : 5601
30 + KibanaHost = ENV['KIBANA_HOST'] ? ENV['KIBANA_HOST'] : 'localhost'
31
32 # The record type as defined in your logstash configuration.
33 # Seperate multiple types with a comma, no spaces. Leave blank
34 @@ -44,19 +32,19 @@
35 # Do not use isoUtcDatetime or the "UTC:" prefix described in the above
36 # article, as timezone correction is already performed by the "Timezone"
37 # config variable.
38 - # Time_format = 'isoDateTime'
39 + # Time_format = 'isoDateTime'
40 Time_format = 'mm/dd HH:MM:ss'
41
42 # Change which fields are shown by default. Must be set as an array
43 # Default_fields = ['@fields.vhost','@fields.response','@fields.request']
44 Default_fields = ['@message']
45
46 - # If set to true, Kibana will use the Highlight feature of Elasticsearch to
47 + # If set to true, Kibana will use the Highlight feature of Elasticsearch to
48 # display highlighted search results
49 - Highlight_results = true
50 + Highlight_results = false
51
52 - # A field needs to be specified for the highlight feature. By default,
53 - # Elasticsearch doesn't allow highlighting on _all because the field has to
54 + # A field needs to be specified for the highlight feature. By default,
55 + # Elasticsearch doesn't allow highlighting on _all because the field has to
56 # be either stored or part of the _source field.
57 Highlighted_field = "@message"
58
59 @@ -99,18 +87,18 @@
60 # indexing
61 Smart_index = true
62
63 - # You can define your custom pattern here for index names if you
64 - # use something other than daily indexing. Pattern needs to have
65 - # date formatting like '%Y.%m.%d'. Will accept an array of smart
66 - # indexes.
67 - # Smart_index_pattern = ['logstash-web-%Y.%m.%d', 'logstash-mail-%Y.%m.%d']
68 + # You can define your custom pattern here for index names if you
69 + # use something other than daily indexing. Pattern needs to have
70 + # date formatting like '%Y.%m.%d'. Will accept an array of smart
71 + # indexes.
72 + # Smart_index_pattern = ['logstash-web-%Y.%m.%d', 'logstash-mail-%Y.%m.%d']
73 # Smart_index_pattern = 'logstash-%Y.%m.%d'
74 # here is an example of how to set the pattern using an environment variable
75 # Smart_index_pattern = ENV['SMART_INDEX'] ? ENV['SMART_INDEX'] : 'logstash-%Y.%m.%d'
76 Smart_index_pattern = 'logstash-%Y.%m.%d'
77 -
78 +
79 # Number of seconds between each index. 86400 = 1 day.
80 - Smart_index_step = 86400
81 + Smart_index_step = 86400
82
83 # ElasticSearch has a default limit on URL size for REST calls,
84 # so Kibana will fall back to _all if a search spans too many
85 @@ -120,7 +108,7 @@
86
87 # Elasticsearch has an internal mechanism called "faceting" for performing
88 # analysis that we use for the "Stats" and "Terms" modes. However, on large
89 - # data sets/queries facetting can cause ES to crash if there isn't enough
90 + # data sets/queries facetting can cause ES to crash if there isn't enough
91 # memory available. It is suggested that you limit the number of indices that
92 # Kibana will use for the "Stats" and "Terms" to prevent ES crashes. For very
93 # large data sets and undersized ES clusers, a limit of 1 is not unreasonable.