Monit: http://mmonit.com/monit/ For both internal & external monitoring: apache, nginx, mongrel, mysql, sphinx, delayed_job, postfix, CPU, etc Whenever a process goes down, its will try to bring it up. If it is not able to start a process it will notify us.
Cloudkick: https://www.cloudkick.com/ For both internal & external. We are in the process of evaluating this tool. It supports rackspace, ec2, slicehost, etc. If you use more than one cloud services, this tool might help you.
Logwatch: http://linuxcommand.org/man_pages/logwatch8.html - Sends daily report about whats happening in a server. Like new packages installed, list of cron tasks running, authentication failures, etc.
The rails error management landscape has changed a lot since this question was first posted. But this thread came up when I was doing google searches for airbrake alternatives.
Several new companies have started offering error monitoring services for rails. The one we like at work is Honeybadger.io. Paper trail is also a nice service in this space.
Another option for error tracking and monitoring in Rails is Raygun, at http://raygun.io - it's got the usual complement of features like intelligent email notifications and error grouping, but adds nice organisation support for multiple devs and integration in GitHub, Fogbugz, YouTrack etc. It's also got Hipchat notifications so when an exception occurs your team sees it in your chat room.
One wonderful way to get updates about your application is to use Exception Notification.
This allows you to get emails based on exceptions that take place in your app. It won't be a solution to all of your information desires, but if someone tries to access a non-existent page, you could get information about what they tried to access, how they got there, etc.
Hoptaud and Exception Notification are good, Heroku has another addons to use like StillAlive.
FogBugz and LightHouseApp may also help you, Lighthouse is free for open-source.
If you want to get involved deeply in Rails errors and notifications read The Rails 3 Way book's first chapter and /environment folder's content.
The best way is still BDD and TDD. Work out all redirections, add nice 404 page, use all stages for development (devel, test, hopefully staging and QA too, and only finally production), then get notifications and always check logfiles before going for production. HTH
发布评论
评论（5）
这些是我们用于监控的工具：
Monit：http://mmonit.com/monit/< br>
对于内部和外部外部监控：apache、nginx、mongrel、mysql、sphinx、delayed_job、postfix、CPU等
每当一个进程出现故障时，它都会尝试将其恢复。如果它无法启动进程，它会通知我们。
Cloudkick：https://www.cloudkick.com/
对于内部和外部外部的。我们正在评估这个工具。它支持rackspace、ec2、slicehost等。如果您使用多个云服务，这个工具可能会对您有所帮助。
警报网格：http://alert-grid.com/
用于监控我们的 cron 任务。
异常通知：
错误应用程序：http://errorapp.com/ - 免费
Airbrake(hoptoad) http://airbrakeapp.com/pages/home
日志监视：
http://linuxcommand.org/man_pages/logwatch8.html - 发送有关服务器中发生的情况的每日报告。例如安装的新软件包、正在运行的 cron 任务列表、身份验证失败等。
入侵检测：
http://www.ossec.net/
These are the tools we use for monitoring:
Monit: http://mmonit.com/monit/
For both internal & external monitoring: apache, nginx, mongrel, mysql, sphinx, delayed_job, postfix, CPU, etc
Whenever a process goes down, its will try to bring it up. If it is not able to start a process it will notify us.
Cloudkick: https://www.cloudkick.com/
For both internal & external. We are in the process of evaluating this tool. It supports rackspace, ec2, slicehost, etc. If you use more than one cloud services, this tool might help you.
Alert Grid: http://alert-grid.com/
For monitoring our cron tasks.
Exception Notification:
Error App: http://errorapp.com/ - Its free
Airbrake(hoptoad) http://airbrakeapp.com/pages/home
Logwatch:
http://linuxcommand.org/man_pages/logwatch8.html - Sends daily report about whats happening in a server. Like new packages installed, list of cron tasks running, authentication failures, etc.
Intrusion Detection:
http://www.ossec.net/
自从这个问题首次发布以来，Rails 错误管理环境已经发生了很大变化。但是当我在谷歌搜索减速板替代品时出现了这个帖子。
几家新公司已经开始提供铁路错误监控服务。我们在工作中喜欢的是 Honeybadger.io。 Paper Trail 在这个领域也是一项不错的服务。
The rails error management landscape has changed a lot since this question was first posted. But this thread came up when I was doing google searches for airbrake alternatives.
Several new companies have started offering error monitoring services for rails. The one we like at work is Honeybadger.io. Paper trail is also a nice service in this space.
Rails 中错误跟踪和监控的另一个选项是 Raygun，位于 http://raygun.io - 它具有常见的功能补充，例如智能电子邮件通知和错误分组，但增加了对多个开发人员的良好组织支持以及 GitHub、Fogbugz、YouTrack 等中的集成。它还具有 Hipchat 通知，因此当发生异常时，您的团队可以在您的帐户中看到它聊天 房间。
在项目中安装并设置 ruby gem (https://rubygems.org/gems/raygun4ruby)也很快。
Another option for error tracking and monitoring in Rails is Raygun, at http://raygun.io - it's got the usual complement of features like intelligent email notifications and error grouping, but adds nice organisation support for multiple devs and integration in GitHub, Fogbugz, YouTrack etc. It's also got Hipchat notifications so when an exception occurs your team sees it in your chat room.
Installing and setting up the ruby gem (https://rubygems.org/gems/raygun4ruby) into your project's pretty quick, too.
获取应用程序更新的一种好方法是使用异常通知。
这使您可以根据应用程序中发生的异常情况获取电子邮件。它不会是满足您所有信息需求的解决方案，但如果有人尝试访问不存在的页面，您可以获得有关他们尝试访问的内容、他们如何到达那里等的信息。
One wonderful way to get updates about your application is to use Exception Notification.
This allows you to get emails based on exceptions that take place in your app. It won't be a solution to all of your information desires, but if someone tries to access a non-existent page, you could get information about what they tried to access, how they got there, etc.
Hoptaud 和异常通知都很好，Heroku 还有另一个插件可以使用，比如 StillAlive。
FogBugz 和 LightHouseApp 也可能对你有帮助，Lighthouse 是免费开源的。
如果您想深入了解 Rails 错误和通知，请阅读 The Rails 3 Way 书的第一章和 /environment 文件夹的内容。
最好的方式仍然是BDD和TDD。制定所有重定向，添加漂亮的 404 页面，使用开发的所有阶段（开发、测试，希望也能进行登台和 QA，最后只有生产），然后获取通知并在投入生产之前始终检查日志文件。华泰
Hoptaud and Exception Notification are good, Heroku has another addons to use like StillAlive.
FogBugz and LightHouseApp may also help you, Lighthouse is free for open-source.
If you want to get involved deeply in Rails errors and notifications read The Rails 3 Way book's first chapter and /environment folder's content.
The best way is still BDD and TDD. Work out all redirections, add nice 404 page, use all stages for development (devel, test, hopefully staging and QA too, and only finally production), then get notifications and always check logfiles before going for production. HTH