kibana job from logsearch/204.0.0
              Github source:
              6b05207d or
              master branch
            
Properties¶
kibana¶
  
  
    
default_app_id¶The default application to load.
- Default
discover
elasticsearch¶
host¶IP address of elasticsearch master to send elasticsearch requests to
- Default
127.0.0.1
port¶Port of elasticsearch master to send elasticsearch requests to
- Default
"9200"
env¶a list of arbitrary key-value pairs to be passed on as process environment variables. eg: FOO: 123
- Default
[]
host¶This setting specifies the IP address of the back end server.
- Default
0.0.0.0
kibana_index¶Kibana uses an index in Elasticsearch to store saved searches, visualizations and dashboards
- Default
.kibana
memory_limit¶Configure the GC in nodejs to treat this number as the available memory for this process. The value is in the form of % of VM memory.
- Default
75
plugins¶a list of key-value pairs of plugins. e.b. Kibana-auth: /var/vcap/packagaes/kibana/kibana-auth
- Default
[]
port¶Kibana is served by a back end server. This controls which port to use.
- Default
5601
request_timeout¶Time in milliseconds to wait for responses from the back end or elasticsearch. This must be > 0
- Default
300000
shard_timeout¶Time in milliseconds for Elasticsearch to wait for responses from shards. Set to 0 to disable
- Default
30000
wait_for_templates¶A list of index templates that need to be present in ElasticSearch before the process starts
- Default
[]
Templates¶
            Templates are rendered and placed onto corresponding
            instances during the deployment process. This job's templates
            will be placed into /var/vcap/jobs/kibana/ directory
            (learn more).
          
- bin/kibana_ctl(from- bin/kibana_ctl)
- bin/monit_debugger(from- bin/monit_debugger)
- config/kibana.conf(from- config/kibana.conf.erb)
- data/properties.sh(from- data/properties.sh.erb)
- helpers/ctl_setup.sh(from- helpers/ctl_setup.sh)
- helpers/ctl_utils.sh(from- helpers/ctl_utils.sh)
Packages¶
            Packages are compiled and placed onto corresponding
            instances during the deployment process. Packages will be
            placed into /var/vcap/packages/ directory.