什么是基于 Coldfusion 的优秀错误跟踪软件？
我正在寻找一种可以轻松或自动向其系统发送冷融合错误消息的工具。
然后我可以使用基于网络的界面来管理优先级、跟踪谁修复了什么等等。
但我想用它来帮助我们更好地处理错误，同时也向我的同事展示错误跟踪系统的重要性。
系统要求：Apache、Windows、Coldfusion 8 Standard、Sql Server 2005。
财务要求：免费或开源
目标或目的：鼓励我的同事想要并使用错误跟踪系统。
这样重写是否更有意义？
谢谢克雷格
What I am looking for is a tool that easily or automatically sends coldfusion error messages to their system.
Then I can use the web-based interface, to manage priorities, track who fixed what and so forth.
But I want to use this to help us deal with errors better, but also to show the importance of a bug tracking system to my fellow works.
System Requirements: Apache, Windows, Coldfusion 8 Standard, Sql Server 2005.
Financial Requirements: Free or Open Source
Goal Or Purpose: To encourage my fellow workers to want and use a bug tracking system.
Does this re-write make more sense?
Thanks
Craig
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（9）
Wiki 有一个问题跟踪软件列表，也许这个列表可以提供帮助。
http://en.wikipedia.org/wiki/Comparison_of_issue_tracking_systems
您也许可以找到托管服务并使用电子邮件或 Web 服务通过 onError 创建票证。话虽如此，可以使用用于驱动内容的相同数据库为您的网站创建一个简单的问题跟踪应用程序。 2 或 3 个表将负责数据存储，并且您已经在使用 CF，因此应用程序层已经存在。
HTH。
Wiki has a list of issue tracking software, maybe this list could help.
http://en.wikipedia.org/wiki/Comparison_of_issue_tracking_systems
You may be able to find a hosted service and use either email or web services to create the ticket using onError. With that said, a simple issue tracking app could be created for your site using the same DB used to drive the content. 2 or 3 tables would take care of the data storage and you're already using CF so the application layer is already there.
HTH.
几年来，我仅通过电子邮件大量使用这种类型的设置，最近 3 年使用错误跟踪软件。
我必须说，错误跟踪软件让我的生活变得更加平静。没有任何东西被留下、被遗忘或从裂缝中溜走。很容易找到错误的趋势，并记住错误发生的“所有时间”。
我们的设置是这样的：
1) Coldfusion + 具有错误报告功能的适当框架 - 您使用什么并不重要。我广泛使用 Fusebox，现在正在过渡到 ColdBox。除了 Mach-II、FW/1、Model-Glue 等之外，两者都非常有能力。您必须在其中找到的关键部分是它们捕获“onError”的能力，通常在应用程序 CFC 中。
2) 自定义 OnError 脚本 - 无论何时发生错误，您都希望捕获有关该错误的最大数量的信息并将其通过电子邮件发送出去。我们所做的是，当发生错误时，我们会注销用户并显示消息“哎呀，请重新登录”。在注销之前，应用程序会捕获错误并将其通过电子邮件发送给 Fogbugz。除此之外，在顶部我们还包括了 IP 地址、正在使用的浏览器等的 CGI 变量。随着时间的推移，您会发现需要添加的内容。
3) Fogbugz 中的路由。 Fogbugz 的 2 个用户版本是免费的，并在线托管。提交错误有两种主要方式。一种是一次发送一封电子邮件。因此，如果错误发生 2000 次，您会收到 2000 封电子邮件和 2000 个案例。将它们链接在一起并不总是最好的，等等。它们有一个名为 BugzScout 的功能，它本质上是一个 HTTP 地址，您可以使用 cfform 向其发送表单，其中包含您将放入电子邮件中的所有相同信息。有很多关于这方面的文档，也是我一直想了解的内容。几周前，我第一次遇到了 2000 封电子邮件的情况，所以我将切换到这种情况。
希望有帮助。分享您最终做了什么以及为什么这样做，以便我们大家也可以学习！
I have been heavily using this type of a setup for several years by email only, and the last 3 years with a Bug Tracking Software.
I must say, the bug tracking software has made my life so much more peaceful. Nothing is left, forgotten, or slips through the cracks. It's easy to find trends in errors, and remember "all the times" it happened.
Our setup is like this:
1) Coldfusion + Appropriate framework with error reporting - It doesn't matter what you use. I have used Fusebox extensively and am making the transition to ColdBox. Both are very capable, in addition to Mach-II, FW/1, Model-Glue, etc. The key part you have to find in them is their ability to catch "onError", usualy in the application CFC.
2) Custom OnError Script - Wherever an error occurs, you want to capture the maximum amount of information about that error and email it in. What we do is, when an error occurs, we log the user out with a message of "oops, log in again". Before logging them out, the application captures the error and emails it to Fogbugz. Along with it, at the top we include the CGI variables for the IP address, browser being used, etc. Over time you will find the things you need to add.
3) Routing in Fogbugz. A 2 user version of Fogbugz is free, and hosted online. There are two main ways to submit bugs. One is to email one in at a time. So if an error happens 2000 times, you get 2000 emails, and 2000 cases. Not always the best to link them together, etc. They have a feature called BugzScout, which is essentially an HTTP address that you do a form post to with cfform with all of the same information you would have put into the email. There's plenty of documentation on this and something I've always wanted to get around to. I had a scenario of 2000 emails for the first time happen a few weeks ago so I'll be switching over to this.
Hope that helps. Share what you ended up doing and why so we all can learn too!
我很惊讶没有人提到 LighthousePro (http://lighthousepro.riaforge.org)。开源 - 100% 免费 - 和 ColdFusion。作为作者，我还是有点偏见。 :)
I'm surprised no one mentioned LighthousePro (http://lighthousepro.riaforge.org). Open source - 100% free - and ColdFusion. As the author I'm a bit biased though. :)
很难回答这个问题，不知道有哪些限制？您有安装任何东西的权限吗？此外，大多数错误跟踪系统都需要某种数据库支持。
我有一个建议。您可以建立一个基本的错误跟踪系统，该系统只允许人们创建票证，并允许您/其他人关闭它。
这里提到了更多基于 Windows 的工具
适用于 Windows 的优秀开源错误跟踪/问题跟踪软件
有什么理由特别要冷融合吗？
Hard question to answer not knowing what kind of restrictions are there? Do you have any permissions to install anything? Also most bug-tracking systems require some kind of database support.
I have a suggestion. You can put in place a basic bug-tracking system, that just allows people to create tickets, and allows you/someone else to close it.
More Windows based tools are mentioned here
Good open-source bug tracking / issue tracking sofware for Windows
Any reason why coldfusion specifically?
我真的很喜欢 Stack Overflow 制作者的 Fogbugz。对于一位用户来说，它的价格相当合理。我手动输入一些错误，并通过电子邮件发送其他错误。
I really like Fogbugz from the makers of Stack Overflow. For one user it's quite reasonably priced. I enter some bugs manually and have others emailed in.
许多错误跟踪软件将公开用于向其中输入数据的 SOAP 方法。
例如，我们使用 Axosoft 的 OnTime，它公开了我在应用程序中使用的一些 WSDL 页面。有人告诉我 Jira 也这么做了。
A lot of bug tracking software will expose SOAP methods for entering data into them.
For example, we used Axosoft's OnTime and that exposed some WSDL pages that I consumed in my application. I was told that Jira did as well.
CF411 列表中有一些： 用 CFML 编写的错误跟踪/缺陷跟踪/故障单/帮助台工具< /a>
There are few in CF411 list: Bug Tracking/Defect Tracking/Trouble Ticket/Help Desk Tools Written in CFML
我们使用 HopToad。还有另一个名为 LightHouse 的错误跟踪应用程序，它与 HopToad 集成，因此您可以轻松地从传入异常。 HopToad 有一个 API，其中有很多客户端，您需要基于 CF 的 API：
http:// github.com/timblair/coldfusion-hoptoad-notifier
即使您不使用 HopToad 并且最终使用不同的服务或推出自己的服务，如果您需要编写自己的 API 客户端，您也可以利用代码或模式上述 HopToad 客户端的 (s)。
We use HopToad. There is another bug-tracking app called LightHouse that integrates with HopToad so you can easily create a [bug] ticket from an incoming exception. HopToad has an API of which there are many clients, you want the CF based one:
http://github.com/timblair/coldfusion-hoptoad-notifier
Even if you dont use HopToad and you end up using a different service or roll your own, if you needed to write your own API client you could leverage the code or pattern(s) of the above HopToad client.
每个人都提供了很多很好的信息，我真的很感谢大家所付出的努力。但不是我正在寻找的答案。这也许意味着，我想要的东西还不存在。
所以我可能必须推出自己的解决方案...或者可能与另一个现有的应用程序集成...
谢谢大家。
A lot of good information from everyone, and I really do appreciate the efforts given. But not the answer i was looking for. Which maybe means, that what i want does not exist, yet.
So i may have to roll my own solution...Or maybe integrate with another existing app...
Thank You all.