blocks|key|1699692|text|我过去采取的最简单的方法是使用log4net。这样您就可以在配置文件中配置日志记录。如果您需要将其转到数据库，请将其设置为这样。如果您希望在发生重大错误时收到通知，请这样设置。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1699693|至于对日志进行排序，这实际上取决于您想要采取的方法，以及您计划进行多少日志记录。通常我会登录到一个纯文本文件，因为我不会在我的应用程序中启用大量的日志记录。所以解析它们并不是什么大问题。|1699694|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

The easiest approach I've taken in the past is using log4net. That way you can configure the logging in the config file. If you need it to go to a database, set it up as such. If you want to be notified when a major error occurs, set it up that way.

As far as sorting through the logs, it really depends on the approach you want to take, and how much you plan on logging. Normally I log to a flat text file as I don't enable a lot of logging in my applications. So parsing through them isn't a big deal.

blocks|key|399163|text|除非你想写一个用于教育目的的系统，否则老实说，我认为你最好还是坚持使用log4net或nlog。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|399164|此外，您最好研究这些系统的代码，而不是编写自己的代码。|399165|关于你的问题，我会坚持使用文本文件，并在将消息发送到磁盘之前对消息进行缓冲。|399166|entityMap|0|LINK|mutability|MUTABLE|url|http://logging.apache.org/log4net/index.html|1|http://www.nlog-project.org/^0|Z|7|0|17|4|1|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]|$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]]]

Unless you want to write a system for education purposes, I honestly think that you'd be best off sticking with <a href="http://logging.apache.org/log4net/index.html" rel="nofollow noreferrer">log4net</a> or <a href="http://www.nlog-project.org/" rel="nofollow noreferrer">nlog</a>.

And further, you would probably be better off studying the code to those systems instead of writing your own.

As to your question, I would stick to a text file and buffer the messages before spitting them to disk.

blocks|key|1671647|text|为什么要费心发明轮子？您可以查看MS+enterprise+library+Logging+Block。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1671648|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Why bother inventing wheel? you can check MS enterprise library Logging Block.

blocks|key|1697706|text|绝对不是xml。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1697707|对于xml，您将需要读取它，解析它，添加任何东西，然后再次生成整个xml，并将其写回硬盘。每次你记录一些东西的时候。|1697708|当然，除非您手动将节点附加到xml文件中，否则将失去xml的大部分优势。|1697709|致命错误的警告-只要能帮助你在应用程序崩溃时调试它-那些我会存储在txt文件中的日志。为每个条目追加一行。|1697710|通过这种方式，您还可以要求您的用户查看它(如果您通过电话帮助他)。|1697711|如果它不是一个元日志，比如上面提到的，换句话说，如果它是与程序本身有关的任何东西，你可能需要分析-保持在数据库上。|1697712|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

definitely not xml. 

with xml, you will need to read it all, parse it, add whatever, then generate the whole xml again, and write it back to hard disk. every single time you log something.

unless of course you append the nodes to the xml file manually, in which way you loose most of xml advantages.

warnings to fatal errors - whatever will help you to debug the application if it crashes - those logs i would store in a txt file.
append a new line for every entry.

this way you can also ask from your user to check it out (if you assist him via the phone).

if it's not a meta log, such as mentioned above, in other words, if it's anything related to the program itself you may need to analyze - keep on the db.

blocks|key|399111|text|关于文件和数据库，这取决于你的选择。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|399112|文件日志提供了更好的性能，但也带来了访问的痛苦。|399113|如果日志很少提供信息(例如，应用程序崩溃，您需要知道原因)，那么最好将日志存储在文件中。|399114|如果您想要访问这些日志，分析它们，等等，您应该将它们存储在数据库中。|399115|.net真的不是我喜欢的领域，但是有很多理由说明为什么应该使用框架的日志记录类。|399116|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

Regarding file vs database, it's up to you to choose.

File logs give greater performance but with pain of access.

If the logs are there just to rarely provide information (e.g. the app crashes and you need to know why), you're better off storing the logs in a file.

If you want to give access to those logs, analyze them, etc, you should store them in a database.

.net is really not my zone, but there are lots of reasons why you should use the framework's logging classes.

blocks|key|399225|text|对于我的应用程序，我选择了写入db。(对我来说)以这种方式阅读日志更容易。然而，我不会像一些人那样疯狂地记录日志，我只记录我需要记录的东西，而不记录其他东西。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|399226|不久前我给了log4net一个机会，但我一点也不喜欢它。仅仅给数据库写信和发送电子邮件就是一大堆垃圾。我最终编写了一个自定义日志记录类，整个过程大约有200行，只花了几个小时。它工作得很好，我没有另一个依赖，而且它可以很容易地改变。|399227|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

For my apps I have chosen to write to db. Its easier (for me) to read the logs this way. However I do not go log crazy as some people do, I only log what I need to log and nothing else.

I gave log4net a shot not to long ago and did not like it at all. It was a whole lot of junk to just write to a db and send an email. I ended up writing a custom logging class and it was a whole ~200 lines and took just a few hours. It works great, I don't have another dependency, and it can be easily changed.

blocks|key|1697766|text|如果您正在处理ASP.NET，ELMAH是另一个很好的日志记录工具。这显然是微软的Scott+Hanselman+uses所说的。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1697767|不过，它确实需要一些additional+code才能使用ASP.NET+MVC的HandleError属性。|1697768|entityMap|0|LINK|mutability|MUTABLE|url|http://code.google.com/p/elmah/|1|http://www.hanselman.com/blog/ELMAHErrorLoggingModulesAndHandlersForASPNETAndMVCToo.aspx|2|https://stackoverflow.com/questions/766610/how-to-get-elmah-to-work-with-asp-net-mvc-handleerror-attribute/779961#779961^0|F|5|0|1L|4|1|0|A|F|2|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]|$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]]|C|$]]|$1|F|3|-4|5|6|7|12|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]|P|$5|I|J|K|C|$L|Q]]]]

If you're dealing with ASP.NET, <a href="http://code.google.com/p/elmah/" rel="nofollow noreferrer">ELMAH</a> is another good logging tool. It's apparently what Microsoft's Scott Hanselman <a href="http://www.hanselman.com/blog/ELMAHErrorLoggingModulesAndHandlersForASPNETAndMVCToo.aspx" rel="nofollow noreferrer">uses</a>.

It does need some <a href="https://stackoverflow.com/questions/766610/how-to-get-elmah-to-work-with-asp-net-mvc-handleerror-attribute/779961#779961">additional code</a> to get it to work with ASP.NET MVC's HandleError attribute, though.

blocks|key|1671770|text|NLog和log4net都提供了丰富的日志记录API，但都不能解决管理和分析日志文件中的所有数据所面临的挑战。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1671771|如果你愿意考虑一个商业工具，看看GIBRLATAR+-它可以与NLog和log4net一起工作，还可以收集有用的performance+metrics。最重要的是，GIBRALTAR+provides+great+tools+for+managing+and+analyzing+logs。|offset|length|1671772|entityMap|0|LINK|mutability|MUTABLE|url|http://www.gibraltarsoftware.com/enter/gibraltar-for-logging.aspx|1|http://www.gibraltarsoftware.com/See/NLog.aspx|2|http://www.gibraltarsoftware.com/See/Collecting-and-Managing-Log4Net-data.aspx|3|http://www.gibraltarsoftware.com/See/Performance-Monitoring.aspx|4|http://www.gibraltarsoftware.com/See/Default.aspx^0|0|G|9|0|V|4|1|10|7|2|1K|J|3|2A|1Q|4|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]|$D|10|E|11|1|12]|$D|13|E|14|1|15]|$D|16|E|17|1|18]|$D|19|E|1A|1|1B]]|A|$]]|$1|F|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]|N|$5|I|J|K|A|$L|O]]|P|$5|I|J|K|A|$L|Q]]|R|$5|I|J|K|A|$L|S]]|T|$5|I|J|K|A|$L|U]]]]

NLog and log4net both provide a rich logging API but neither addresses the challanges you face managing and analyzing all the data in your log files. 

If you're willing to consider a commerical tool, take a look at <a href="http://www.gibraltarsoftware.com/enter/gibraltar-for-logging.aspx" rel="nofollow noreferrer">GIBRLATAR</a> - it works with <a href="http://www.gibraltarsoftware.com/See/NLog.aspx" rel="nofollow noreferrer">NLog</a> and <a href="http://www.gibraltarsoftware.com/See/Collecting-and-Managing-Log4Net-data.aspx" rel="nofollow noreferrer">log4net</a> and also collects useful <a href="http://www.gibraltarsoftware.com/See/Performance-Monitoring.aspx" rel="nofollow noreferrer">performance metrics</a>. Most importantly, <a href="http://www.gibraltarsoftware.com/See/Default.aspx" rel="nofollow noreferrer">GIBRALTAR provides great tools for managing and analyzing logs</a>.

I was reading the following article:
<a href="http://odetocode.com/articles/294.aspx" rel="nofollow noreferrer">http://odetocode.com/articles/294.aspx</a>

This article raised me a lot of question regarding logs.
(I don’t know if I should have made this in separated questions… but I don’t want to spam stackoverflow.com with questions of mine)

The 1st one is if I should store it in a .txt, or .xml file… or even in a table inside the database.
Probably saving in the .txt will be better regarding performance. But when someone needs to find something the .txt file, it may become a pain in the... neck.
So… which one should I use, and why?

The second one, is there any specific class to deal with “log” thing?
I have read several threads about this subject, and I didn’t find the answers to my questions.

Thanks in advance.

C# Creating a log system

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我正在读下面这篇文章：这篇文章给我提出了很多关于日志的问题。(我不知道我是否应该在单独的问题…中提出这个问题但我不想用我的问题来给stackoverflow.com发垃圾邮件)第一个问题是，我是否应该将其存储在.txt或.xml文件…中或者甚至在数据库内的表中。也许保存在.txt中会对性能有更好的影响。但是当有人需要在.txt文件中找到一些东西时，这可能会成为一个痛苦的……脖子。所以…我应该使用哪

问C#创建日志系统
EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问C#创建日志系统EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问C#创建日志系统
EN