diff options
author | liyin <liyin11@huawei.com> | 2017-07-17 17:45:38 +0800 |
---|---|---|
committer | liyin <liyin11@huawei.com> | 2017-07-17 17:45:38 +0800 |
commit | 75f99aaeadada56dfc974746cd83fec275133a3c (patch) | |
tree | f916a3b19140a0e938205a94197e20c151df0113 /docker/bottleneck-compose/kibana/config | |
parent | b26f701ab2327497b0e44f548ea18e24b1e6b0d9 (diff) |
Bug fix of Bottlenecks can't use CLI
JIRA: BOTTLENECK-171
Bug fix of Bottlenecks can't use CLI to start test.
Some docker-compose function delete to fit elk docker support.
After this patch you could use bottlenecks testcase run
posca_factor_ping to start this test.
you also need to put the rc file to bottlenecks docker.
Change-Id: I340e31185a499c81f9595a902df89d8f0ddf0cd3
Signed-off-by: liyin <liyin11@huawei.com>
Diffstat (limited to 'docker/bottleneck-compose/kibana/config')
-rw-r--r-- | docker/bottleneck-compose/kibana/config/kibana.yml | 76 |
1 files changed, 0 insertions, 76 deletions
diff --git a/docker/bottleneck-compose/kibana/config/kibana.yml b/docker/bottleneck-compose/kibana/config/kibana.yml deleted file mode 100644 index 820c7767..00000000 --- a/docker/bottleneck-compose/kibana/config/kibana.yml +++ /dev/null @@ -1,76 +0,0 @@ -# Kibana is served by a back end server. This controls which port to use. -port: 5601 - -# The host to bind the server to. -host: "0.0.0.0" - -# The Elasticsearch instance to use for all your queries. -elasticsearch_url: "http://elasticsearch:9200" - -# preserve_elasticsearch_host true will send the hostname specified in `elasticsearch`. If you set it to false, -# then the host you use to connect to *this* Kibana instance will be sent. -elasticsearch_preserve_host: true - -# Kibana uses an index in Elasticsearch to store saved searches, visualizations -# and dashboards. It will create a new index if it doesn't already exist. -kibana_index: ".kibana" - -# If your Elasticsearch is protected with basic auth, this is the user credentials -# used by the Kibana server to perform maintence on the kibana_index at statup. Your Kibana -# users will still need to authenticate with Elasticsearch (which is proxied thorugh -# the Kibana server) -# kibana_elasticsearch_username: user -# kibana_elasticsearch_password: pass - -# If your Elasticsearch requires client certificate and key -# kibana_elasticsearch_client_crt: /path/to/your/client.crt -# kibana_elasticsearch_client_key: /path/to/your/client.key - -# If you need to provide a CA certificate for your Elasticsarech instance, put -# the path of the pem file here. -# ca: /path/to/your/CA.pem - -# The default application to load. -default_app_id: "discover" - -# Time in milliseconds to wait for elasticsearch to respond to pings, defaults to -# request_timeout setting -# ping_timeout: 1500 - -# Time in milliseconds to wait for responses from the back end or elasticsearch. -# This must be > 0 -request_timeout: 300000 - -# Time in milliseconds for Elasticsearch to wait for responses from shards. -# Set to 0 to disable. -shard_timeout: 0 - -# Time in milliseconds to wait for Elasticsearch at Kibana startup before retrying -# startup_timeout: 5000 - -# Set to false to have a complete disregard for the validity of the SSL -# certificate. -verify_ssl: true - -# SSL for outgoing requests from the Kibana Server (PEM formatted) -# ssl_key_file: /path/to/your/server.key -# ssl_cert_file: /path/to/your/server.crt - -# Set the path to where you would like the process id file to be created. -# pid_file: /var/run/kibana.pid - -# If you would like to send the log output to a file you can set the path below. -# This will also turn off the STDOUT log output. -# log_file: ./kibana.log -# Plugins that are included in the build, and no longer found in the plugins/ folder -bundled_plugin_ids: - - plugins/dashboard/index - - plugins/discover/index - - plugins/doc/index - - plugins/kibana/index - - plugins/markdown_vis/index - - plugins/metric_vis/index - - plugins/settings/index - - plugins/table_vis/index - - plugins/vis_types/index - - plugins/visualize/index |