maxmustermann/kibana
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
No description
312 commits 329 branches 211 tags 6.1 GiB
TypeScript 91.3%
JavaScript 7.7%
SCSS 0.3%
Shell 0.2%
CSS 0.2%
Other 0.1%
Find a file
Boaz Leskes 281bb79432 Do not move to end request when auto indenting
2014-02-11 10:33:46 +01:00
agent Add node role flags and whether node is master to node rendering 2014-02-05 13:04:51 +01:00
common Fixed build system after rename exporter dir to agent and other minor issues. 2014-01-22 18:20:25 +01:00
docs Documented marvel.agent.interval settings 2014-02-05 12:03:24 +01:00
kibana Indexing Rate Primaries chart should use primaries.indexing.index_total 2014-02-10 16:31:28 +01:00
sense Do not move to end request when auto indenting 2014-02-11 10:33:46 +01:00
tasks Change page titles to say marvel 2014-01-23 21:58:19 +01:00
.gitignore Initial version documentation 2014-01-28 12:52:16 +01:00
Gruntfile.js Fixed wrong kibanaRevision 2014-02-06 20:20:45 +01:00
index.html Added an index.html file to the root folder to redirect to kibana. Update build system, including a change to replace @@KIBANA_REVISION @@MARVEL_REVISION anywhere with their respective values. These are now part of a comment in the kibana config file and the base index.html 2014-01-22 11:09:04 +01:00
LICENSE.txt Removed CONTRIBUTING file and updated license 2014-01-27 21:30:23 +01:00
NOTICE.txt Initial working ExporingService, plugin + an ESExport implementation 2013-05-22 11:12:09 +02:00
package.json Version to 1.0.3-SNAP 2014-02-04 14:13:54 +01:00
README.md Updated readme file 2014-02-06 11:07:36 +01:00

README.md

Installing the last release of Marvel

The easiest way to play/get to know Marvel is to install the latest release version of it. To do so, just run the following command on every node on your cluster (restart node for it to have effect):

./bin/plugin -i elasticsearch/marvel/latest

Once done, open up the following url (assuming standard ES config): http://localhost:9200/_plugin/marvel . This will take you to the Overview Dashboard. Use Kibana's Load dashboard menu to navigate to the Cluster Pulse dashboard

Grunt build system (for running the UI from a code checkout)

This grunt-based build system handles Kibana development environment setup for Marvel as well as building, packaging and distribution of the Marvel plugin. Note that you must run grunt setup before any other tasks as this build system reuses parts of the Kibana build system that must be fetched

Installing

You will need node.js+npm and grunt. Node is available via brew, install grunt with the command below. Once grunt is installed you may run grunt tasks to setup your environment and build Marvel

npm install -g grunt npm install

Tasks

grunt setup

Run this first. It will download the right Kibana version to ./vendor/kibana, copies the appropriate config.js to the right place and make any symlinks needed for a proper marvel/kibana environment

grunt server

Starts a web server on http://127.0.0.1:5601 pointing at the kibana directory, while also serving custom marvel panels.

You can use grunt server --port=5601 --es_host=9200 to control the ports used for kibana and the elasticsearch port used.

grunt jshint

Lints code without building

grunt build

Merges kibana and marvel code, builds Kibana and the plugin (via mvn) and puts them in ./build.

grunt package

Zips and tar+gzips the build in build/packages. Includes grunt build

grunt release

Uploads created archives to download.elasticsearch.org/elasticsearch/marvel/marvel-VERSION.extention. You will need S3 credentials in .aws-config.json. Format as so:

{
  "key":"MY_KEY_HERE",
  "secret":"your/long/secret/string"
}

To upload the current archive as the "latest" release, use:

grunt release --latest