Valid from 3.1 to 3.2
The documentation below is valid from Datafari v3.1.0 to v3.2
By default, aside from Kibana, Elasticsearch and Logstash are automatically configured by Datafari on the first start, to fit with your installation directory and be ready to run.
If for some reasons (like an architecture decision), you move one or more of these components to a different place than the installation directory of Datafari, you must modify the ELK environment parameters located in [DATAFARI_HOME]/elk/scripts/set-elk-env.sh and maybe also the [DATAFARI_HOME]/elk/scripts/start-elk.sh and [DATAFARI_HOME]/elk/scripts/stop-elk.sh scripts.
The first time you run Datafari, go to the admin UI and to the 'ELK Configuration' page (Statistics/ELK Configuration). You will find this UI:
Let us go through the 3 options:
- "ON/OFF" button : Should ELK start when Datafari is running ? (Note that if you swich it ON, it will immediately start ELK)
Kibana URI : The URI to reach Kibana. By default it is http://localhost:5601
Monitoring User : This parameter should only be filled if you use ACLs for search. In that case, enter here the user used to crawl the files. Otherwise, ELK won't be able to generate statistics on the corpus.
Once you have started ELK (be aware that the average time for ELK to be 100% operational is approx. 15 seconds on a "standard" PC), click on any statistic tab ('Usage Statistics', 'Corpus Statistics' or 'Corpus Over Time Statistics'), you will now see the corresponding dashboard:
