# \[ANNOUNCEMENT\] retsbeat released

**URL:** <https://discuss.elastic.co/t/announcement-retsbeat-released/59545>\
**Category:** Community Ecosystem\
**Created:** [September 1, 2016, 11:38am UTC](https://discuss.elastic.co/t/announcement-retsbeat-released/59545 "2016-09-01T11:38:18Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![val](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/val/32/138203_2.png) [@val](https://discuss.elastic.co/u/val)\
**Post date:** [September 1, 2016, 11:38am UTC](https://discuss.elastic.co/t/announcement-retsbeat-released/59545/1 "2016-09-01T11:38:18Z")

</div>

The [Real Estate Transaction Standard](http://www.reso.org/specifications/) (RETS) is used in the real estate industry to facilitate the exchange of data among real estate actors such as agents, brokers, owners and many more, over the HTTP protocol. « retsbeat » is a new community beat which aims at facilitating the gathering of metrics and insights from [Multiple Listing Service](https://en.wikipedia.org/wiki/Multiple_listing_service) (MLS) servers supporting the RETS specification.

The main idea of retsbeat is to periodically query a list of pre-configured MLS servers for the count of resources (Properties, Agents, Contacts, Open houses, etc) and their status (Active, Sold, Pending, Contingent, Expired, Withdrawn, etc). retsbeat also supports any kind of custom RETS queries, it will send them and collect the counts of matching records. A quick glance at a [sample retsbeat document](https://github.com/consulthys/retsbeat/blob/master/examples/retsbeat.json) gives an idea of what kind of data can be collected by retsbeat.

We're still working on more features and goodies but the current implementation already allows to build some nice dashboards which provide helpful insights into your RETS data.

retsbeat can be found here:

> **[consulthys/retsbeat](https://github.com/consulthys/retsbeat)**
>
> retsbeat - Simple beat to gather statistics from remote MLS RETS servers

PS: This beat leverages the [gorets](https://github.com/jpfielding/gorets) library by JP Fielding. Kudos JP for providing such an excellent RETS client in Go!

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [September 1, 2016, 9:18pm UTC](https://discuss.elastic.co/t/announcement-retsbeat-released/59545/2 "2016-09-01T21:18:09Z")

</div>

Wow, this is such an awesomely unusual use case. Never thought I'd see realestate use cases popping up 😃

---

<div class="post-metadata">

**Author:** ![val](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/val/32/138203_2.png) [@val](https://discuss.elastic.co/u/val)\
**Post date:** [September 1, 2016, 9:25pm UTC](https://discuss.elastic.co/t/announcement-retsbeat-released/59545/3 "2016-09-01T21:25:42Z")

</div>

You'd be surprised 😉  
I've been using Elasticsearch in the context of real estate since 2012 and ES 0.20.5

---

<div class="post-metadata">

**Author:** ![monica](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/monica/32/3696_2.png) [@monica](https://discuss.elastic.co/u/monica)\
**Post date:** [September 1, 2016, 10:44pm UTC](https://discuss.elastic.co/t/announcement-retsbeat-released/59545/4 "2016-09-01T22:44:07Z")

</div>

It's nice to see another unusual use case that a simple Beat can solve. Thank you for developing so many interesting Beats.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 9:47pm UTC](https://discuss.elastic.co/t/announcement-retsbeat-released/59545/5 "2017-07-05T21:47:02Z")

</div>

Closed on July 5, 2017, 9:47pm UTC


