sensu comparison

sensucomparison.md

#Sensu Enterprise ##Main Features

• Packaged install using Yum
• Includes plugins for sending alerts via API/email/https
• Includes Contact Routing
• Enterprise Supports, 4 Levels from 9-5/M-F to 24/7

##Enterprise vs Core (Open Source Version) Feature Comparison ###TurnKey

• Enterprise: Simple Setup, less than a day install time
• Core: Complex Setup, can take a long time and can be complicated to install

###Integrations

• Enterprise: Multiple Integrations with third-party tools & services
  • Supports integration with ITSM
    • Create/Rresolve incidents
    • On-call rotation scheduling
  • Storing time series data (metrics)
  • Relaying events
  • Deregistering sensu-clients for terminated nodes
  • Notifying contacts via:
    • Email (SMTP - Send emial)
    • Slack (API - Send notification to channel)
    • IRC (HTTPS - Send notification to channel)
    • Hipchat (API - Send notification to room)
    • PagerDuty (Service Key - Create and Resolve Incidents)
    • Flapjack (API - Send results)
    • Graphite (TCP - Send metric data)
    • Librato (HTTP - Check metric data)
    • EC2 (Remove Server from Sensu, if EC2 Instance is deleted)
    • Chef (Remove Server from Sensu, if Chef Node is no longer registered to Chef Master)
• Core: Not Included

###Metric Router

• Enterprise: Includes additional mutators, enabling third-party integrations and q proprietary intermediate format that has been optimized for portability. Also supports metrics in the following specifications:
  • Nagios perfdata
  • Graphite (plaintext)
  • OpenTSDB
  • Metrics 2.0 (wire)
• Core: Includes baseic mutators for transforming events to json, Ruby, Hash, or extracting check output

###Contact Routing

• Enterprise: You can send alerts to specific teams and/or individuals based on the alert, reducing the overall mean time to repair (MTTR)
• Core: Not Included