作者：晨光微露36 | 来源：互联网 | 2023-05-19 07:39
FFmpeghasseveralloglevels(see-loglevel).Theseare,inorder:quiet,panic,fatal,error,warni
FFmpeg has several loglevels (see -loglevel). These are, in order: quiet, panic, fatal, error, warning, info, verbose and debug.
FFmpeg有几个日志级别(参见-loglevel)。它们依次为:静默、恐慌、致命、错误、警告、信息、冗长和调试。
But the documentation is not very verbose with explaining their meanings.
但是文档并没有详细地解释它们的含义。
It's true that all names are self-documenting enough so they give some intuitive sense for when to use them. But when in doubt, from the user as well as the developer's perspective, in decision situations, it would help to have a clear definition of each level.
的确，所有的名字都是自我记录的，所以它们给了我们一些直观的感觉，什么时候使用它们。但是，当用户和开发人员有疑问时，在决策情况下，对每个层次都有一个清晰的定义是有帮助的。
I would like to know which one is for what purpose, in order to know when to use them. I couldn't find any more hints on this. Especially on the difference between panic, fatal, error and info, verbose, debug.
我想知道哪一个是为了什么目的，以便知道什么时候使用它们。我找不到更多的线索了。特别是在惊慌、致命、错误和信息、冗长、调试之间的区别。
I think I've found the code for these but I still don't know their exact purposeful 'boundaries'. Is there an explanation on this, (perhaps outside the ffmpeg project)?
我想我已经找到了它们的密码，但我仍然不知道它们确切的“界限”。对此有什么解释吗(可能在ffmpeg项目之外)?
1 个解决方案
8
Often the definitions of RFC 5424 (syslog protocol) are used. Wikipedia defines this severity levels like this:
通常使用RFC 5424 (syslog协议)的定义。维基百科对严重程度的定义如下:
Panic System is unusable. A "panic" condition usually affecting multiple apps/servers/sites. At this level it would usually notify all tech staff on call.
恐慌系统无法使用。“恐慌”状态通常会影响多个应用程序/服务器/站点。在这个级别上，它通常会通知所有技术人员随时待命。
Alert Action must be taken immediately. Should be corrected immediately, therefore notify staff who can fix the problem. An example would be the loss of a primary ISP connection.
必须立即采取警报行动。应立即纠正，因此通知员工谁可以解决问题。一个例子是丢失一个主要的ISP连接。
Critical Critical conditions. Should be corrected immediately, but indicates failure in a primary system, an example is a loss of a backup ISP connection.
关键的关键条件。应该立即纠正，但是在主系统中表示故障，一个示例是备份ISP连接的丢失。
Error Error conditions. Non-urgent failures, these should be relayed to developers or admins; each item must be resolved within a given time.
错误错误条件。非紧急故障，应转送给开发人员或管理员;每个项目必须在给定的时间内解决。
Warning Warning conditions. Warning messages, not an error, but indication that an error will occur if action is not taken, e.g. file system 85% full - each item must be resolved within a given time.
警告警告条件。警告消息，不是错误，而是表示如果不采取行动将发生错误，例如文件系统85%已满——每个项目必须在给定的时间内解决。
Notice Normal but significant condition. Events that are unusual but not error conditions - might be summarized in an email to developers or admins to spot potential problems - no immediate action required.
注意正常但重要的情况。不寻常但不出错的事件——可能会在电子邮件中总结为开发人员或管理员发现潜在问题——不需要立即采取行动。
Informational Informational messages. Normal operational messages - may be harvested for reporting, measuring throughput, etc. - no action required.
信息信息消息。正常的操作消息——可以收集来报告、测量吞吐量等——不需要任何操作。
Debug Debug-level messages. Info useful to developers for debugging the application, not useful during operations.
调试级的调试信息。信息对开发人员有用，用于调试应用程序，在操作过程中没有用处。
http://en.wikipedia.org/wiki/Syslog#Severity_levels
http://en.wikipedia.org/wiki/Syslog Severity_levels
This are some common levels and there definition. FFmpeg does not make use of all of them and names some differently. But it will give you a clou...
这是一些常见的层次和定义。FFmpeg并没有使用它们，也没有使用不同的名称。但它会给你一个提示……
京公网安备 11010802041100号