You’re going to need the following before you begin:
- An ObjectRocket for Elasticsearch (2.x) instance in one of the following data centers:
- US-East (IAD)
- US-West (SJC)
- US-Chicago (ORD)
- US-Dallas (DFW)
- EU-London (LON)
- Your Elasticsearch/Kibana ACLs and Users configured
- Make sure you add your ACLs (IP address whitelisting) and have created either an Admin or Kibana-only user – otherwise you won’t be able to access your Kibana interface to check out the sample Twitter dashboard.
- To add ACLs or Users, do so by clicking the instance name in the Instances interface to configure your Elasticsearch instance (Note: make sure to add a Kibana ACL as well!)
- A Twitter developer application created: https://apps.twitter.com/
Create a new Twitter App¶
- Create New App
- Fill in App Details (you can skip Callback URL).
- Keep your Consumer Key and Consumer Secret handy.
- Create an Access Token.
- Keep your OAuth Token and OAuth Secret handy.
Create and configure Twitter connector¶
- When in the Connectors interface, click the Add Connector button (don’t forget to create an Elasticsearch 2.x instance first!)
- Select the Twitter connector.
- Name your connector, include your Consumer Key, Consumer Secret, Access Token, and Access Secret.
- Enter a Twitter keyword you want to search for and collect (or multiple keywords, comma separated), and click Test API to validate.
- After Test API is successful, select the Target Datastore Selection button.
- Choose your target Elasticsearch cluster, and either leverage an existing index or create a new one by selecting the Create New Index checkbox and naming your index.
- Click the Kibana Dashboard link to access Kibana and view the sample Twitter dashboard (Make sure you add your ACLs (IP address whitelisting) and have created either an Admin or Kibana-only user – otherwise you won’t be able to access Kibana)
- Kibana may ask you to “Configure an index pattern” – if so, click the index name on the left-hand side and proceed.