# Logstash JDBC Input vs ElasticSearch JDBC Importer **URL:** \ **Category:** Elasticsearch\ **Created:** [March 7, 2017, 9:21pm UTC](https://discuss.elastic.co/t/logstash-jdbc-input-vs-elasticsearch-jdbc-importer/77727 "2017-03-07T21:21:37Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![matt40413](https://avatars.discourse-cdn.com/v4/letter/m/f04885/32.png) [@matt40413](https://discuss.elastic.co/u/matt40413)\ **Post date:** [March 7, 2017, 9:21pm UTC](https://discuss.elastic.co/t/logstash-jdbc-input-vs-elasticsearch-jdbc-importer/77727/1 "2017-03-07T21:21:37Z")
So I got a working example working using a Postgres Database and Logstash/ElasticSearch and Kibana. It's basic....but it works. Im very new to this, so I don't think I truly understand what Logstash does vs ElasticSearch (Kibana seems understandable enough). However I came across this: [https://github.com/jprante/elasticsearch-jdbc](https://github.com/jprante/elasticsearch-jdbc) and im not entirely sure what the difference is....besides not using logstash and it not being an official plugin? Im basically wanting to just display sensor data (from a weather sensor database on Postgres) to be searchable within some "Fancy" kibana visualizations. Is there a better tool? Thanks! ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [March 7, 2017, 10:45pm UTC](https://discuss.elastic.co/t/logstash-jdbc-input-vs-elasticsearch-jdbc-importer/77727/2 "2017-03-07T22:45:37Z")
Thanks for the interest in my JDBC importer project. > [@matt40413](#): > > However I came across this: [GitHub - jprante/elasticsearch-jdbc: JDBC importer for Elasticsearch](https://github.com/jprante/elasticsearch-jdbc) and im not entirely sure what the difference is....besides not using logstash and it not being an official plugin? The JDBC importer is one of my personal spare time projects since 2012. The standalone Java application (once it was a plugin for Elasticsearch, or a "river" to be precise, which is now obsolete) is useful to generate JSON documents from SQL relational table data, and index them into Elasticsearch. It comes with open source JDBC drivers out of the box (e.g. PostgresQL JDBC), but supports also other proprietary JDBC drivers. I hope I can find time to update the JDBC importer to Elasticsearch 5 soon, because in the last six months, I had to take a break. It's mostly used as a starting point to kick off customized Java application developments for pushing JDBC data to Elasticsearch, as you can see by the 550 forks. Logstash is part of the commercially supported Elastic stack for processing data from log sources, transforming them, and indexing them into Elasticsearch. It's written in JRuby and offers a JDBC connector, besides many other connectors. ---
**Author:** ![matt40413](https://avatars.discourse-cdn.com/v4/letter/m/f04885/32.png) [@matt40413](https://discuss.elastic.co/u/matt40413)\ **Post date:** [March 8, 2017, 2:16pm UTC](https://discuss.elastic.co/t/logstash-jdbc-input-vs-elasticsearch-jdbc-importer/77727/3 "2017-03-08T14:16:14Z")
Is there really any advantage (or disadvantage) to one over the other? Right now im using the Logstash JDBC Plugin. Which seems to index things into ElasticSearch...I guess the rivers (deprecated) or your JDBC Importer just skips the Logstash step? I guess the only positive I see to using the Logstash JDBC plugin is that it's an officially supported item. At least for my case. Unless theirs another item out there that would work better, im basically just wanting to pull some basic data from a Postgres database to be searchable/viewable on a Kibana instance dashboard. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 5, 2017, 2:16pm UTC](https://discuss.elastic.co/t/logstash-jdbc-input-vs-elasticsearch-jdbc-importer/77727/4 "2017-04-05T14:16:13Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.