Canary Weekly #2

Hey, we made it to #2!

Rackspace sponsorship!! #

I’m very excited and humbled to announce that Rackspace has offered to sponsor canary.io development by generously providing us with hosting services. This has allowed us to expand our pool of sensord instances into new areas.

Special thanks to Jesse Noller and to Kyle Kelley for making all of this possible.

watch.canary.io #

Within a few hours after the canary.io project was announced, Jeremy Green began developing a dashboard to help people make sense of the raw data.

I’m happy to say that we are now hosting this under the canary.io domain, found at watch.canary.io.

Core services vision document #

As noted in the previous issue of Canary Weekly, it was clear that I needed to write up a document describing the goal of the core services of Canary - the inner foundation upon which the other services (or your own) can be built.

That document lives here if anyone is interested in reading it.

api.canary.io is now spread across multiple geographic regions #

The canaryd processes that power api.canary.io are now spread across multiple regions (DFW, IAD and SYD) to help provide higher availability and ensure that the core services remain online in the event of failure in two of the other regions.

When visiting api.canary.io, clients will be directed to the closest healthy region. This is our first step in this direction, and I’m interested to share what we learn as time goes on. For those who are interested, we are achieving this with Amazon’s Route 53.

Hat tips #

Big thanks to Karl Kirch for providing several pull requests, helping improve the general code quality of both canaryd and sensord.

What’s next? #

The coming week will still likely focus around closing out any operational concerns mentioned in this issue, bringing us closer to giving the components a proper 1.0.0 release and ultimately allowing us to spend more time on the product and user experience.