简体繁体 English

是否存在允许跨平台错误记录和跟踪多个应用程序的任何工具？

[英]Do any tools exist that allow cross platform error logging and tracking for multiple applications?

原文 2012-02-13 16:54:54 3 2 java/ .net/ error-handling/ cross-platform

Our development team hosts many different applications both .Net and Java based. 我们的开发团队拥有许多不同的应用程序，包括.Net和Java。 Currently, we handle our error logging with Log4J and use emails to alert the development team when problems arise. 目前，我们使用Log4J处理错误日志记录，并在出现问题时使用电子邮件向开发团队发出警报。 Currently, we get thousands of alerts a day and it's becoming a little tedious to maintain. 目前，我们每天都会收到数千条警报，维护起来变得有点乏味。

We've been discussing creating a central dashboard for all our apps. 我们一直在讨论为我们所有的应用程序创建一个中央仪表板。 The ideal tool would track errors, warnings, info etc. over the life of an application (it doesn't necessarily need to be db driven). 理想的工具可以在应用程序的整个生命周期中跟踪错误，警告，信息等（它不一定需要由数据库驱动）。 The idea is that the data can be viewed on a dashboard, drillable to specific errors with the capability of alerting via emal when triggers and or thresholds are met. 我们的想法是，可以在仪表板上查看数据，可以根据具体错误进行查看，并具有在满足触发和/或阈值时通过emal发出警报的能力。

Elmah is good for .Net but we need a tool that could also work for Java EE? Elmah对.Net很有用，但是我们需要一个可以用于Java EE的工具吗？ What is the best way to go about this? 最好的方法是什么？ Should we: 我们应该吗：

Just use Elmah for the .Net apps and find something similar for Java and build our own dashboard to create a united look & feel? 只需将Elmah用于.Net应用程序并找到类似于Java的内容并构建我们自己的仪表板以创建统一的外观和感觉？

OR 要么

Is there a tool that already exists that we can leverage to do this cross platform? 是否存在我们可以利用的工具来实现这个跨平台？

I've tried looking in Sourceforge but it's difficult to describe what I'm looking for. 我已经尝试过查看Sourceforge，但很难描述我在寻找什么。

2 个解决方案

I don't think you have a logging problem, I think that you have an integration problem, no matter if it is logging, or any other area your root issue is the same... How do I make my completely different components talk to each other? 我认为你没有日志记录问题，我认为你有一个集成问题，无论是日志记录，还是任何其他领域你的root问题是相同的......我如何使我完全不同的组件与彼此？

There is a lot of approaches, but probably the easiest to implement for different technologies is Web services or REST... You will probably need to have a central logger that you need to implement independently, and then build a Web service/REST interface to which you are going to have to connect to... 有很多方法，但可能最容易实现的不同技术是Web服务或REST ...您可能需要一个中央记录器，您需要独立实现，然后构建一个Web服务/ REST接口你将不得不连接到...

Maybe a different line of investigation for you is to see if there is a logging product out in the market that takes web service calls... If that's the case, you only need to change your components to make a service call every time. 对您来说，可能有一个不同的调查方向是查看市场上是否有一个记录产品需要进行Web服务调用......如果是这种情况，您只需要更改组件以便每次都进行服务调用。

Something else that you need to consider is that your remote logging should never superseed your local logging, that's it do both, the reason is very simple, remote calls can fail, so code as if they will fail. 您需要考虑的其他事情是您的远程日志记录永远不应该取代您的本地日志记录，它就是两者兼而有之，原因很简单，远程调用可能会失败，因此代码就好像它们会失败一样。

We have been using http://www.exceptional.io/ for error tracking for some time now: it's cheap and extremely simple. 我们一直在使用http://www.exceptional.io/进行错误跟踪：它既便宜又简单。

To report errors you just post a json document to its endpoint. 要报告错误，您只需将json文档发布到其端点。