summaryrefslogtreecommitdiff
path: root/templates/config.js.erb
diff options
context:
space:
mode:
Diffstat (limited to 'templates/config.js.erb')
-rw-r--r--templates/config.js.erb80
1 files changed, 80 insertions, 0 deletions
diff --git a/templates/config.js.erb b/templates/config.js.erb
new file mode 100644
index 0000000..411ffa9
--- /dev/null
+++ b/templates/config.js.erb
@@ -0,0 +1,80 @@
1/** @scratch /configuration/config.js/1
2 *
3 * == Configuration
4 * config.js is where you will find the core Kibana configuration. This file contains parameter that
5 * must be set before kibana is run for the first time.
6 */
7define(['settings'],
8function (Settings) {
9 "use strict";
10
11 /** @scratch /configuration/config.js/2
12 *
13 * === Parameters
14 */
15 return new Settings({
16
17 /** @scratch /configuration/config.js/5
18 *
19 * ==== elasticsearch
20 *
21 * The URL to your elasticsearch server. You almost certainly don't
22 * want +http://localhost:9200+ here. Even if Kibana and Elasticsearch are on
23 * the same host. By default this will attempt to reach ES at the same host you have
24 * kibana installed on. You probably want to set it to the FQDN of your
25 * elasticsearch host
26 *
27 * Note: this can also be an object if you want to pass options to the http client. For example:
28 *
29 * +elasticsearch: {server: "http://localhost:9200", withCredentials: true}+
30 *
31 */
32 elasticsearch: "http://"+window.location.hostname+":80"+"<%= @elasticsearch_prefix %>",
33
34 /** @scratch /configuration/config.js/5
35 *
36 * ==== default_route
37 *
38 * This is the default landing page when you don't specify a dashboard to load. You can specify
39 * files, scripts or saved dashboards here. For example, if you had saved a dashboard called
40 * `WebLogs' to elasticsearch you might use:
41 *
42 * default_route: '/dashboard/elasticsearch/WebLogs',
43 */
44 default_route : '/dashboard/file/logstash.json',
45
46 /** @scratch /configuration/config.js/5
47 *
48 * ==== kibana-int
49 *
50 * The default ES index to use for storing Kibana specific object
51 * such as stored dashboards
52 */
53 kibana_index: "kibana-int",
54
55 /** @scratch /configuration/config.js/5
56 *
57 * ==== panel_name
58 *
59 * An array of panel modules available. Panels will only be loaded when they are defined in the
60 * dashboard, but this list is used in the "add panel" interface.
61 */
62 panel_names: [
63 'histogram',
64 'map',
65 'goal',
66 'table',
67 'filtering',
68 'timepicker',
69 'text',
70 'hits',
71 'column',
72 'trends',
73 'bettermap',
74 'query',
75 'terms',
76 'stats',
77 'sparklines'
78 ]
79 });
80});