+353 87 1272938 email@example.com
Siren Join is the Siren Solutions plugin for Elasticsearch which allows high efficiency joins across data in elasticsearch In practice, it extends Elasticsearch with capabilities to handle interconnected networks of complexly structured documents.
Kibi is a “friendly fork” of Kibana, born from our excitement for Kibana and our desire to deliver the power and flexibility of Kibana and Elasticsearch to use cases involving complex/interconnected knowledge. To work its magic, Kibi makes strong use of the Siren Join Plugins capabilities.
Siren Solutions is committed to track the latest developments of Kibana so to offer the very latest Kibana/Elasticsearch features enhanced with the Siren Plugin/Kibi capabilities for Data Intelligence.
Other features available upon request :
Kibi removes none of the features of Kibana, so we think of it as a no brainer replacement.
Be aware, however, that Kibi tabbed interface cannot be disabled at the moment so you might want to consider this.
Kibi is a “Kept in Sync” Fork: we tracks, the latest Kibana deployment and we’re committed to do so in the future, so you get all the good stuff in there, worry not.
Unlike Kibana however Kibi versions are not “locked in” to a specific Elasticsearch version. In other words. Kibi 4.4.1 – for example, will work also on later Elasticsearch (at the time of this writing Elasticsearch 2.3.3). So, given a few days after each release, you can expect Kibi to be able to run always on the latest available Elasticsearch.
In legal terms, the combination of Siren join and Kibi is very similar to that of MongoDB (AGPL) with its Drivers (Apache). (people use and may extend the drivers, so they wont be affected by the AGPL in dowstream applications)
Here is how we mean it in practice and ask you to respect this:
However notice that if you intend to
No. Kibi supports for External Data sources such as typically SQL and generic REST sources.
Kibi can query these sources on the fly at user navigation to create special filters or special “external query” aggregators (e.g. to use in visualizations).
Generally speaking, you have to load all the data that will intend perform search and complex analytics must be loaded. But you do not need to materialize or import auxiliary data e.g. that is only used for visualizations or to create filters.
Not necessarily. Logstash (which we use in our fully worked out example) is a very handy tool for loading data into Elasticsearch/Siren 2.0 – thus in Kibi, but it is not the only choice.
ETL can be performed in many ways, e.g. by custom scripts or by using ETL/data workflow/messaging tools found such as Talend, CloverETL, Kafka etc.
Kibi Enterprise Edition is the commercial offering of Kibi. Its flexibly licenced and has many additional features please see here
If you want to access a SQL database through a JDBC driver, you need to load JDBC bindings before starting Kibi.
Edit “config/kibi.yml” and add the following line:
In order to connect to SQL database through JDBC, native JAVA bindings are needed. Although Kibi ships native JAVA bindings for MacOS, Linux, and Windows, it may happen that the version of some native library dependency is too old/recent. To go around this, you can compile the bindings on your machine:
# Check that you are running the correct node version
# install required version of node (you can check it in package.json)
# we recommend to use nvm - node version manager
$ cat package.json | grep node
$ nvm install 4.4.7
$ nvm alias default 4.4.7
$ node -v
# Remove the JDBC node module
$ rm -rf node_modules/jdbc
# Recompile the JDBC node module
$ npm install firstname.lastname@example.org
# Verify the version of the JDBC module in package.json
$ cat node_modules/jdbc/package.json | grep version
# uninstall node if not needed anymore
$ nvm uninstall 4.4.7
If you have issues starting or accessing Kibi, make sure that you have read access to the following files:
This assumes that you unziped the Kibi distribution to “/opt/kibi“.