Heartbeat Routes

[colinrymer]

Currently custom heartbeats are accessible via /ops/heartbeat/[custom_heartbeat]. Since custom heartbeats are a resource, I propose that we follow RESTful conventions and update the route to /ops/heartbeats/[custom_heartbeat] as this will also allow us to use /ops/heartbeats as an index of all the custom heartbeats, while still allowing /ops/heartbeat to return a simple 200 OK result.

[databyte]

Good idea. The only custom one I know of is for Zutron and Riak so that shouldn't be too hard for Infra to change for us this one time.

[armondhonore]

Is this just for web or for all IDG?

Thanks

Armond Honore
Manager of Integrations & Web Services
Primedia
ahonore@primedia.com

From: David Sommers <notifications@github.commailto:notifications@github.com>
Reply-To: primedia/ops <reply@reply.github.commailto:reply@reply.github.com>
Date: Friday, December 7, 2012 11:48 AM
To: primedia/ops <ops@noreply.github.commailto:ops@noreply.github.com>
Subject: Re: [ops] Heartbeat Routes (#1)

Good idea. The only custom one I know of is for Zutron and Riak so that shouldn't be too hard for Infra to change for us this one time.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-11136940.

[colinrymer]

This would be for anyone using the ops gem.

[databyte]

If it's a RubyGems compatible app, you can reuse this gem. For other langs, you'd have to build a compatible library to include. It's a simple Sinatra app that mounts to Rack to handle /ops/version, /ops/heartbeat and more.