I’m obsessed with the idea of using nested colour coded blocks to represent subscriptions, clients, and checks. Anyone know if another piece of software does something along these lines? I like the idea of human readable UTC stamps, perhaps iso8601.
I think a Sensu extension, “event-history-graphite”, would be useful for many.
On Thu, May 23, 2013 at 3:47 PM, Matt firstname.lastname@example.org wrote:
I’d second UI work on the dashboard, a view of current history of checks passing and failing. Clients and checks grouped by subscription. Epoch conversion to UTC datestamp
Embedded checking of graphite values for notifying handlers would be cool. i.e for values sensu doesn’t see, but it might gather and send to graphite as a metric. I know there are other tools that do this, but having this in one place is nice.
On 23 May 2013 23:33, “portertech” email@example.com wrote:
I believe UI & documentation improvements are the logical next step. I would love to see sensu-dashboard adopt an “overview” visualization, one that utilizes the Sensu client execution history functionality, that was recently added by Jeremy Carrol. The UI currently suffers from many small bugs, these can probably be remedied without much pain.
On Sunday, 7 April 2013 11:51:40 UTC-7, Joe Miller wrote:
Sensu has been in the pre-1.0 stage for over a year now, and while there’s still cool new features coming with every point release, I wanted to ping the community and start a discussion about what a “Sensu 1.0” looks like.
The new sensu-dev list seems like a great place to start this conversation. So after talking to Sean I figured now is as good a time as any to give this a shot.
A few things that I had in mind when I picture a Sensu 1.0 are:
- Revocation support for SSL (rabbitmq). Right now we recommend single certificates and fast re-key/deployment via your CM tool because RabbitMQ lacks a simple revocation mechanism for SSL. There may be some possible ways we could accomplish this without requiring rabbitmq modifications, such as building our own module in erlang and exporting a ‘verify_fun’ function and coercing rabbit to load that. Or, perhaps there’s other ways.
- Jeremy Carroll had some thoughts on things that he feels would be important in pushing Sensu adoption further such as feature parity in the UI with other systems. If he’s on this list, I’d ask him to speak up.
- Finalized API/interface for extensions is probably a key 1.0 feature so that folks are more confident that they will not have to refactor their extensions
- **100% doc coverage =) **At least for all the core features.
Anything else? throw ideas out here, let’s see what sticks!