Noteworthy at Compose: The end of Elasticsearch 1.x and Telegraf updated
PublishedThis is your weekly summary of Compose news for those changes and updates which can make your life easier. In this edition, its the end for Elasticsearch 1.x, an update for the Telegraf add-on, a versioned response for the API. Also a look back at the past week's articles, including Scylla 2.0.3 in Compose.
Elasticsearch 1.x End of Support
We've reached that point where we have to say goodbye to Elasticsearch 1.x on Compose. It was five years ago when we added Elasticsearch to the Compose portfolio; it was also when we changed our name to Compose. We brought its replacement, Elasticsearch 2.4 to Compose in 2016 and since then, Elasticsearch 5.4 in 2017 and most recently, Elasticsearch 6 this year. With the last year's end of life for Elasticsearch 1.7.x, it's now time to close the book on Elasticsearch 1.x at Compose. We're getting in touch with all of the users and explaining how they can migrate to newer versions before the end of support date, April 15th.
Telegraf Add-on updated
Many Compose database deployments offer a Telegraf add-on which can ship metrics data to the Datadog or Librato services for analysis. We've just updated the add-on to its latest version which should improve its reliability and performance while offering up new metrics and events for some users. If you already use the Telegraf add-on, visiting the Add-ons page will give you to an opportunity to immediately update your Telegraf add-on in place. New users of the Telegraf add-on will, of course, get the latest version automatically.
You can find the current metrics gathered by the Telegraf add-on for MongoDB, Elasticsearch, PostgreSQL, RabbitMQ and Redis. RethinkDB is also supported but the plugin is currently undocumented.
Extended API Versioning
We've made a tiny change in the Compose API, but it's one that API users might like to make a note of for future-proofing their code. When you make an API query now, we return a Server:
header with a description of the currently configured version of the API at that endpoint. Right now, you'll see ComposeAPI/2016-07
. Future revisions will, of course, modify that string. If you want to quickly check the version, try
curl --head -X GET -H "Content-Type: application/json" 'https://api.compose.io/2016-07/'
from your command line to see all the returned headers including the new Server:
header.
Compose Articles
In the past week, we've updated Scylla, shown how to make on-demand TLS/SSL connections to Redis and rounded up the news from around the web:
- We announced the arrival of Scylla 2.0.3 with an article rather literally named Scylla 2.0.3: Now on Compose. More importantly, we talked about the new features like production counters for, well, counting but efficiently, and the preview of Materialized Views to help cleanly slice up your data into new, real, tables.
- Redis and TLS are a great combination, except when it comes to the redis-cli command. That's why we wrote How to stunnel to Redis on-demand with stunredis, a utility which makes making the connection really easy even if you have multiple Redis deployments.
- And we finished the week with our regular Friday NewsBits, where we looked at version 1.0 of the smart pager for PostgreSQL users, the latest update to MongoDB's developing Go driver, a change in version numbering for MySQL 8 and much more.
That's it for this week's Noteworthy at Compose. Onwards to next week!
Read more articles about Compose databases - use our Curated Collections Guide for articles on each database type. If you have any feedback about this or any other Compose article, drop the Compose Articles team a line at articles@compose.com. We're happy to hear from you.