How to load Office 365 data into Elasticsearch via Logstash



Introducing a simple method to load Office 365 data using the ETL module Logstash of the full-text search service Elasticsearch and the CData JDBC driver.

Elasticsearch is a popular distributed full-text search engine. By centrally storing data, you can perform ultra-fast searches, fine-tuning relevance, and powerful analytics with ease. Elasticsearch has a pipeline tool for loading data called "Logstash". You can use CData JDBC Drivers to easily import data from any data source into Elasticsearch for search and analysis.

This article explains how to use the CData JDBC Driver for Office 365 to load data from Office 365 into Elasticsearch via Logstash.

Using CData JDBC Driver for Office 365 with Elasticsearch Logstash

  • Install the CData JDBC Driver for Office 365 on the machine where Logstash is running.
  • The JDBC Driver will be installed at the following path (the year part, e.g. 20XX, will vary depending on the product version you are using). You will use this path later. Place this .jar file (and the .lic file if it's a licensed version) in Logstash.
    C:\Program Files\CData\CData JDBC Driver for Office365 20XX\lib\cdata.jdbc.office365.jar
  • Next, install the JDBC Input Plugin, which connects Logstash to the CData JDBC driver. The JDBC Plugin comes by default with the latest version of Logstash, but depending on the version, you may need to add it.
    https://www.elastic.co/guide/en/logstash/5.4/plugins-inputs-jdbc.html
  • Move the CData JDBC Driver’s .jar file and .lic file to Logstash's "/logstash-core/lib/jars/".

Sending Office 365 data to Elasticsearch with Logstash

Now, let's create a configuration file for Logstash to transfer Office 365 data to Elasticsearch.

  • Write the process to retrieve Office 365 data in the logstash.conf file, which defines data processing in Logstash. The input will be JDBC, and the output will be Elasticsearch. The data loading job is set to run at 30-second intervals.
  • Set the CData JDBC Driver's .jar file as the JDBC driver library, configure the class name, and set the connection properties to Office 365 in the form of a JDBC URL. The JDBC URL allows detailed configuration, so please refer to the product documentation for more specifics.
  • Office 365 uses the OAuth authentication standard. To authenticate requests, obtain the OAuthClientId, OAuthClientSecret, and OAuthCallbackURL by registering an app with Office 365. See the "Getting Started" chapter of the help documentation for a guide to using OAuth.

Executing data movement with Logstash

Now let's run Logstash using the created "logstash.conf" file.

    logstash-7.8.0\bin\logstash -f logstash.conf

A log indicating success will appear. This means the Office 365 data has been loaded into Elasticsearch.

For example, let's view the data transferred to Elasticsearch in Kibana.

    GET office365_table/_search
    {
        "query": {
            "match_all": {}
        }
    }
Querying the Office 365 data loaded into Elasticsearch

We have confirmed that the data is stored in Elasticsearch.

Confirming the Office 365 data loaded into Elasticsearch

By using the CData JDBC Driver for Office 365 with Logstash, it functions as a Office 365 connector, making it easy to load data into Elasticsearch. Please try the 30-day free trial.

Ready to get started?

Download a free trial of the Office 365 Driver to get started:

 Download Now

Learn more:

Office 365 Icon Office 365 JDBC Driver

The Office 365 Data Provider gives developers the power to easily connect Java/J2EE applications to Office 365 data including Outlook Mail, Contact, Calendar, Files, and more!