What is a Connector?

Updated on Wednesday, 10 April, 2013 - 16:17

Connectors allow you to choose where to send the data generated by your live streams or your queries against the Historics archive. We currently have:

Connector Status Throughput limit per delivery
HTTP live 20 MB
CouchDB beta 5MB
DynamoDB beta

Variable, based on your configuration.

 

Amazon generally limits users to 5MB but you can contact them to discuss your account and potentially increase your usage.

ElasticSearch beta 20MB
FTP beta 20 MB
Google BigQuery beta 20MB
MongoDB beta 10 MB
Precog beta 10MB
Redis beta 20MB
S3 beta 20 MB
SFTP beta 20 MB
Splunk Storm REST beta 10MB
Splunk Storm beta 20MB
Splunk Storm Enterprise beta 10MB
Zoomdata beta 10MB

DynamoDB and S3 are part of Amazon Web Services. You have to set up delivery points for other connectors on your own servers, or you can lease servers from a number of hosting companies. If you do not want a long-term comittment, Amazon Web Services offer EC2 cloud servers that you can use for that purpose.

How do I set up a connector?

Each connector has its own set of parameters. For example, for FTP, you would specify a username, password, and directory whereas for HTTP you would need to specify parameters such as the URL of the endpoint your data will go to.

To get started with Push, prepare all the parameters you'll need to use with the connector you've chosen; make sure you have all of the passwords, keys, and so on, ready. Then, hit the /push/create endpoint. It requires a hash (if you're running a stream) or a Playback id (if you're running a query against Historics data).

To learn more, read our Push introduction and Push API step-by-step guide. Then, follow the instructions published on each connector's page (see the table at the top of this page for links).

What format do you use for the data ?

We deliver data to you in JSON format. JSON is a sreamlined, lightweight format that is easy to parse and easy for humans to interpret. Free resources such as jsonlint.com exist to format raw JSON to make it as human-readable as possible. If you're new to this format, take a look at our Understanding JSON page to get started.