Re: Question about Logging Level

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 01/12/2017 09:12 AM, liuchang0812 wrote:
Hi, all

In our documentation, it says that:

         Ceph’s logging levels operate on a scale of 1 to 20, where 1
is terse and 20 is verbose.

http://docs.ceph.com/docs/master/rados/troubleshooting/log-and-debug/#subsystem-log-and-debug-settings


But, it seems that there are some logging levels 25 :


mds/MDBalancer.cc:276:  dout(25) << "=== got heartbeat " <<
m->get_beat() << " from " << m->get_source().num() << " " <<
m->get_load() << dendl;
mds/CInode.cc:4189:  dout(25) << __func__ << dendl;
mds/MDCache.cc:11656:    //dout(25) << "saw depth " << d << " " <<
*dir << dendl;
mds/MDCache.cc:11666:   //dout(25) << " saw sub " << **p << dendl;
mds/journal.cc:373:      dout(25) << "EMetaBlob::add_dir_context(" <<
dir << ")      maybe " <<


So, shoud we update our documentation, or update logging level to 20?

I've seen douts on levels as high as 35, so if this is really concerning, we could update docs to reflect the fact that level 20 is usually the most verbose, with some rare exceptions that may be useful for devs with deep knowledge of Ceph code or devs responsible for particular piece of code.

--
Piotr Dałek

--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux