{"_id":"5745d43e5528582000dfb3f4","user":"5564f227f0f70f0d00a9ab20","version":{"_id":"573c99725c4c010e006caa57","project":"573c99725c4c010e006caa54","__v":3,"createdAt":"2016-05-18T16:33:54.264Z","releaseDate":"2016-05-18T16:33:54.264Z","categories":["573c99725c4c010e006caa58","5750c01651b4bb2b00178745","5751d0628e9ef90e0083eb06"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"__v":8,"category":{"_id":"573c99725c4c010e006caa58","version":"573c99725c4c010e006caa57","__v":0,"project":"573c99725c4c010e006caa54","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-05-18T16:33:54.308Z","from_sync":false,"order":9999,"slug":"documentation","title":"Data Forwarders"},"project":"573c99725c4c010e006caa54","updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-05-25T16:35:10.806Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":999,"body":"One powerful feature of [Meshblu](https://meshblu.readme.io/docs/getting-started) is the ability to forward any event that occurs in the system to any other service via a concept called *data forwarding*.  With a data forwarder, any message or configuration event a device is [subscribed](https://meshblu.readme.io/docs/subscriptions-2-0)  to can be automatically sent to a service to store data or translate Meshblu messages into a different system.\n\nWe have already created a number of data forwarders for common use cases, such as [Splunk](https://github.com/octoblu/data-forwarder-splunk), [Elasticsearch](https://github.com/octoblu/data-forwarder-elasticsearch), [MongoDB](https://github.com/octoblu/data-forwarder-mongodb), and the [Azure Service Bus](https://github.com/octoblu/data-forwarder-azure-service-bus). So if you want to use one of those, you're in luck! These can be used in the way described in [Creating via a Service](doc:creating-via-service)","excerpt":"Or: how to get your data out of Meshblu","slug":"what-are-meshblu-data-forwarders","type":"basic","title":"What They Are"}

What They Are

Or: how to get your data out of Meshblu

One powerful feature of [Meshblu](https://meshblu.readme.io/docs/getting-started) is the ability to forward any event that occurs in the system to any other service via a concept called *data forwarding*. With a data forwarder, any message or configuration event a device is [subscribed](https://meshblu.readme.io/docs/subscriptions-2-0) to can be automatically sent to a service to store data or translate Meshblu messages into a different system. We have already created a number of data forwarders for common use cases, such as [Splunk](https://github.com/octoblu/data-forwarder-splunk), [Elasticsearch](https://github.com/octoblu/data-forwarder-elasticsearch), [MongoDB](https://github.com/octoblu/data-forwarder-mongodb), and the [Azure Service Bus](https://github.com/octoblu/data-forwarder-azure-service-bus). So if you want to use one of those, you're in luck! These can be used in the way described in [Creating via a Service](doc:creating-via-service)