So we *could* strip them out for syslog, but we’d have still paid the cost of generating them, and as you can see we have much higher precision than that syslog output, plus it’s a “real” time stamp instead of just depending on what happened when transmitting a log message over the network to the syslog server. :)
-Greg
On Sat, Mar 17, 2018 at 7:27 AM Marc Roos <M.Roos@xxxxxxxxxxxxxxxxx> wrote:
I have no logging options configured in ceph.conf, yet I get syslog
entries like these
Mar 16 23:55:42 c01 ceph-osd: 2018-03-16 23:55:42.535796 7f2f5c53a700 -1
osd.0 pg_epoch: 18949 pg[17.21( v 18949'4044827
(18949'4043279,18949'4044827] local-lis/les=18910/18911 n=3125
ec=3636/3636 lis/c 18910/18910 les/c/f 18911/18912/0 18910/18910/18910)
[13,0,9] r=1 lpr=18910 luod=0'0 crt=18949'4044827 lcod 18949'4044826
active] _scan_snaps no head for
17:846274ce:::rbd_data.239f5274b0dc51.0000000000001d75:39 (have MIN)
Mar 16 23:55:42 c01 ceph-osd: 2018-03-16 23:55:42.535823 7f2f5c53a700 -1
osd.0 pg_epoch: 18949 pg[17.21( v 18949'4044827
(18949'4043279,18949'4044827] local-lis/les=18910/18911 n=3125
ec=3636/3636 lis/c 18910/18910 les/c/f 18911/18912/0 18910/18910/18910)
[13,0,9] r=1 lpr=18910 luod=0'0 crt=18949'4044827 lcod 18949'4044826
active] _scan_snaps no head for
17:846274ce:::rbd_data.239f5274b0dc51.0000000000001d75:26 (have MIN)
Should the date/timestamp not be omitted here? We already have this from
syslog server?
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
