Hello,
Is it possible to get sssd to log millisecond timestamps? It only logs to the second and that makes it difficult correlate the flow through various logs while tracking a (potential) performance issue.
thanks
=G=?
On (05/09/17 20:47), Galen Johnson wrote:
Hello,
Is it possible to get sssd to log millisecond timestamps? It only logs to the second and that makes it difficult correlate the flow through various logs while tracking a (potential) performance issue.
Sure.
man sssd.conf -> debug_microseconds
LS
wow...no wonder I missed it...I was looking for milli :-).
thanks
=G=
________________________________________ From: Lukas Slebodnik lslebodn@redhat.com Sent: Wednesday, September 6, 2017 1:37 AM To: End-user discussions about the System Security Services Daemon Subject: [SSSD-users] Re: millisecond time stamps
EXTERNAL
On (05/09/17 20:47), Galen Johnson wrote:
Hello,
Is it possible to get sssd to log millisecond timestamps? It only logs to the second and that makes it difficult correlate the flow through various logs while tracking a (potential) performance issue.
Sure.
man sssd.conf -> debug_microseconds
LS _______________________________________________ sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org
I'm not seeing a change in my logs...I added the following to the [sssd] section
debug_microseconds = true
Also, I don't suppose that there is any way to include a transaction id to make it easier to trace interleaved log messages on a busy system?
=G=
________________________________________ From: Galen Johnson Sent: Wednesday, September 6, 2017 9:27 AM To: End-user discussions about the System Security Services Daemon Subject: Re: [SSSD-users] Re: millisecond time stamps
wow...no wonder I missed it...I was looking for milli :-).
thanks
=G=
________________________________________ From: Lukas Slebodnik lslebodn@redhat.com Sent: Wednesday, September 6, 2017 1:37 AM To: End-user discussions about the System Security Services Daemon Subject: [SSSD-users] Re: millisecond time stamps
EXTERNAL
On (05/09/17 20:47), Galen Johnson wrote:
Hello,
Is it possible to get sssd to log millisecond timestamps? It only logs to the second and that makes it difficult correlate the flow through various logs while tracking a (potential) performance issue.
Sure.
man sssd.conf -> debug_microseconds
LS _______________________________________________ sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org
On 09/06/2017 03:35 PM, Galen Johnson wrote:
I'm not seeing a change in my logs...I added the following to the [sssd] section
debug_microseconds = true
You need to add it to all appropriate sections (same as debug_level) and restart SSSD. Having it in just [sssd] section will affect only the sssd monitor logs.
Also, I don't suppose that there is any way to include a transaction id to make it easier to trace interleaved log messages on a busy system?
I think there is no such way.
=G=
From: Galen Johnson Sent: Wednesday, September 6, 2017 9:27 AM To: End-user discussions about the System Security Services Daemon Subject: Re: [SSSD-users] Re: millisecond time stamps
wow...no wonder I missed it...I was looking for milli :-).
thanks
=G=
From: Lukas Slebodnik lslebodn@redhat.com Sent: Wednesday, September 6, 2017 1:37 AM To: End-user discussions about the System Security Services Daemon Subject: [SSSD-users] Re: millisecond time stamps
EXTERNAL
On (05/09/17 20:47), Galen Johnson wrote:
Hello,
Is it possible to get sssd to log millisecond timestamps? It only logs to the second and that makes it difficult correlate the flow through various logs while tracking a (potential) performance issue.
Sure.
man sssd.conf -> debug_microseconds
LS _______________________________________________ sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org _______________________________________________ sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org
Thanks. I figured it out right after I sent the email (isn't that usually the case? :-/)
As for the transaction id, where can I put in a feature request? It would be invaluable for debugging busy systems.
thanks
=G=
________________________________________ From: Michal Židek mzidek@redhat.com Sent: Wednesday, September 6, 2017 9:50 AM To: sssd-users@lists.fedorahosted.org Subject: [SSSD-users] Re: millisecond time stamps
EXTERNAL
On 09/06/2017 03:35 PM, Galen Johnson wrote:
I'm not seeing a change in my logs...I added the following to the [sssd] section
debug_microseconds = true
You need to add it to all appropriate sections (same as debug_level) and restart SSSD. Having it in just [sssd] section will affect only the sssd monitor logs.
Also, I don't suppose that there is any way to include a transaction id to make it easier to trace interleaved log messages on a busy system?
I think there is no such way.
=G=
From: Galen Johnson Sent: Wednesday, September 6, 2017 9:27 AM To: End-user discussions about the System Security Services Daemon Subject: Re: [SSSD-users] Re: millisecond time stamps
wow...no wonder I missed it...I was looking for milli :-).
thanks
=G=
From: Lukas Slebodnik lslebodn@redhat.com Sent: Wednesday, September 6, 2017 1:37 AM To: End-user discussions about the System Security Services Daemon Subject: [SSSD-users] Re: millisecond time stamps
EXTERNAL
On (05/09/17 20:47), Galen Johnson wrote:
Hello,
Is it possible to get sssd to log millisecond timestamps? It only logs to the second and that makes it difficult correlate the flow through various logs while tracking a (potential) performance issue.
Sure.
man sssd.conf -> debug_microseconds
LS _______________________________________________ sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org _______________________________________________ sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org
_______________________________________________ sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org
On 09/06/2017 03:55 PM, Galen Johnson wrote:
Thanks. I figured it out right after I sent the email (isn't that usually the case? :-/)
As for the transaction id, where can I put in a feature request? It would be invaluable for debugging busy systems.
RFEs and bugs can be reported as Pagure issues: https://pagure.io/SSSD/sssd/issues
thanks
=G=
From: Michal Židek mzidek@redhat.com Sent: Wednesday, September 6, 2017 9:50 AM To: sssd-users@lists.fedorahosted.org Subject: [SSSD-users] Re: millisecond time stamps
EXTERNAL
On 09/06/2017 03:35 PM, Galen Johnson wrote:
I'm not seeing a change in my logs...I added the following to the [sssd] section
debug_microseconds = true
You need to add it to all appropriate sections (same as debug_level) and restart SSSD. Having it in just [sssd] section will affect only the sssd monitor logs.
Also, I don't suppose that there is any way to include a transaction id to make it easier to trace interleaved log messages on a busy system?
I think there is no such way.
=G=
From: Galen Johnson Sent: Wednesday, September 6, 2017 9:27 AM To: End-user discussions about the System Security Services Daemon Subject: Re: [SSSD-users] Re: millisecond time stamps
wow...no wonder I missed it...I was looking for milli :-).
thanks
=G=
From: Lukas Slebodnik lslebodn@redhat.com Sent: Wednesday, September 6, 2017 1:37 AM To: End-user discussions about the System Security Services Daemon Subject: [SSSD-users] Re: millisecond time stamps
EXTERNAL
On (05/09/17 20:47), Galen Johnson wrote:
Hello,
Is it possible to get sssd to log millisecond timestamps? It only logs to the second and that makes it difficult correlate the flow through various logs while tracking a (potential) performance issue.
Sure.
man sssd.conf -> debug_microseconds
LS _______________________________________________ sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org _______________________________________________ sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org
sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org _______________________________________________ sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org
Either I'm doing something wrong or the site is having issues. I'm assuming I have to login/register to open an issue but clicking on "Login" returns "discoveryfailure" regardless of browser.
thanks
=G=
________________________________________ From: Michal Židek mzidek@redhat.com Sent: Wednesday, September 6, 2017 10:10 AM To: sssd-users@lists.fedorahosted.org Subject: [SSSD-users] Re: millisecond time stamps
EXTERNAL
On 09/06/2017 03:55 PM, Galen Johnson wrote:
Thanks. I figured it out right after I sent the email (isn't that usually the case? :-/)
As for the transaction id, where can I put in a feature request? It would be invaluable for debugging busy systems.
RFEs and bugs can be reported as Pagure issues: https://pagure.io/SSSD/sssd/issues
thanks
=G=
From: Michal Židek mzidek@redhat.com Sent: Wednesday, September 6, 2017 9:50 AM To: sssd-users@lists.fedorahosted.org Subject: [SSSD-users] Re: millisecond time stamps
EXTERNAL
On 09/06/2017 03:35 PM, Galen Johnson wrote:
I'm not seeing a change in my logs...I added the following to the [sssd] section
debug_microseconds = true
You need to add it to all appropriate sections (same as debug_level) and restart SSSD. Having it in just [sssd] section will affect only the sssd monitor logs.
Also, I don't suppose that there is any way to include a transaction id to make it easier to trace interleaved log messages on a busy system?
I think there is no such way.
=G=
From: Galen Johnson Sent: Wednesday, September 6, 2017 9:27 AM To: End-user discussions about the System Security Services Daemon Subject: Re: [SSSD-users] Re: millisecond time stamps
wow...no wonder I missed it...I was looking for milli :-).
thanks
=G=
From: Lukas Slebodnik lslebodn@redhat.com Sent: Wednesday, September 6, 2017 1:37 AM To: End-user discussions about the System Security Services Daemon Subject: [SSSD-users] Re: millisecond time stamps
EXTERNAL
On (05/09/17 20:47), Galen Johnson wrote:
Hello,
Is it possible to get sssd to log millisecond timestamps? It only logs to the second and that makes it difficult correlate the flow through various logs while tracking a (potential) performance issue.
Sure.
man sssd.conf -> debug_microseconds
LS _______________________________________________ sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org _______________________________________________ sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org
sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org _______________________________________________ sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org
_______________________________________________ sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org
On 09/06/2017 04:30 PM, Galen Johnson wrote:
Either I'm doing something wrong or the site is having issues. I'm assuming I have to login/register to open an issue but clicking on "Login" returns "discoveryfailure" regardless of browser.
It is the same for me. The site is having issues now. Hopefully not for long.
thanks
=G=
From: Michal Židek mzidek@redhat.com Sent: Wednesday, September 6, 2017 10:10 AM To: sssd-users@lists.fedorahosted.org Subject: [SSSD-users] Re: millisecond time stamps
EXTERNAL
On 09/06/2017 03:55 PM, Galen Johnson wrote:
Thanks. I figured it out right after I sent the email (isn't that usually the case? :-/)
As for the transaction id, where can I put in a feature request? It would be invaluable for debugging busy systems.
RFEs and bugs can be reported as Pagure issues: https://pagure.io/SSSD/sssd/issues
thanks
=G=
From: Michal Židek mzidek@redhat.com Sent: Wednesday, September 6, 2017 9:50 AM To: sssd-users@lists.fedorahosted.org Subject: [SSSD-users] Re: millisecond time stamps
EXTERNAL
On 09/06/2017 03:35 PM, Galen Johnson wrote:
I'm not seeing a change in my logs...I added the following to the [sssd] section
debug_microseconds = true
You need to add it to all appropriate sections (same as debug_level) and restart SSSD. Having it in just [sssd] section will affect only the sssd monitor logs.
Also, I don't suppose that there is any way to include a transaction id to make it easier to trace interleaved log messages on a busy system?
I think there is no such way.
=G=
From: Galen Johnson Sent: Wednesday, September 6, 2017 9:27 AM To: End-user discussions about the System Security Services Daemon Subject: Re: [SSSD-users] Re: millisecond time stamps
wow...no wonder I missed it...I was looking for milli :-).
thanks
=G=
From: Lukas Slebodnik lslebodn@redhat.com Sent: Wednesday, September 6, 2017 1:37 AM To: End-user discussions about the System Security Services Daemon Subject: [SSSD-users] Re: millisecond time stamps
EXTERNAL
On (05/09/17 20:47), Galen Johnson wrote:
Hello,
Is it possible to get sssd to log millisecond timestamps? It only logs to the second and that makes it difficult correlate the flow through various logs while tracking a (potential) performance issue.
Sure.
man sssd.conf -> debug_microseconds
LS _______________________________________________ sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org _______________________________________________ sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org
sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org _______________________________________________ sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org
sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org _______________________________________________ sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org
I agree and I was pondering this for a long time but I could never think of a reasonable way that wouldn’t be too intrusive.
The only way I could think of was to have a structure that would be used as a parent context of tevent requests inside SSSD and internally track request nesting.
But yes, please go ahead and file the ticket, just please note this is not a totally trivial request.
On 6 Sep 2017, at 15:55, Galen Johnson Galen.Johnson@sas.com wrote:
Thanks. I figured it out right after I sent the email (isn't that usually the case? :-/)
As for the transaction id, where can I put in a feature request? It would be invaluable for debugging busy systems.
thanks
=G=
From: Michal Židek mzidek@redhat.com Sent: Wednesday, September 6, 2017 9:50 AM To: sssd-users@lists.fedorahosted.org Subject: [SSSD-users] Re: millisecond time stamps
EXTERNAL
On 09/06/2017 03:35 PM, Galen Johnson wrote:
I'm not seeing a change in my logs...I added the following to the [sssd] section
debug_microseconds = true
You need to add it to all appropriate sections (same as debug_level) and restart SSSD. Having it in just [sssd] section will affect only the sssd monitor logs.
Also, I don't suppose that there is any way to include a transaction id to make it easier to trace interleaved log messages on a busy system?
I think there is no such way.
=G=
From: Galen Johnson Sent: Wednesday, September 6, 2017 9:27 AM To: End-user discussions about the System Security Services Daemon Subject: Re: [SSSD-users] Re: millisecond time stamps
wow...no wonder I missed it...I was looking for milli :-).
thanks
=G=
From: Lukas Slebodnik lslebodn@redhat.com Sent: Wednesday, September 6, 2017 1:37 AM To: End-user discussions about the System Security Services Daemon Subject: [SSSD-users] Re: millisecond time stamps
EXTERNAL
On (05/09/17 20:47), Galen Johnson wrote:
Hello,
Is it possible to get sssd to log millisecond timestamps? It only logs to the second and that makes it difficult correlate the flow through various logs while tracking a (potential) performance issue.
Sure.
man sssd.conf -> debug_microseconds
LS _______________________________________________ sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org _______________________________________________ sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org
sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org _______________________________________________ sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org
I've never been fortunate enough to ask for anything that ended up being trivial :-).
=G= ________________________________________ From: Jakub Hrozek jhrozek@redhat.com Sent: Wednesday, September 6, 2017 2:44 PM To: End-user discussions about the System Security Services Daemon Subject: [SSSD-users] Re: millisecond time stamps
EXTERNAL
I agree and I was pondering this for a long time but I could never think of a reasonable way that wouldn’t be too intrusive.
The only way I could think of was to have a structure that would be used as a parent context of tevent requests inside SSSD and internally track request nesting.
But yes, please go ahead and file the ticket, just please note this is not a totally trivial request.
On 6 Sep 2017, at 15:55, Galen Johnson Galen.Johnson@sas.com wrote:
Thanks. I figured it out right after I sent the email (isn't that usually the case? :-/)
As for the transaction id, where can I put in a feature request? It would be invaluable for debugging busy systems.
thanks
=G=
From: Michal Židek mzidek@redhat.com Sent: Wednesday, September 6, 2017 9:50 AM To: sssd-users@lists.fedorahosted.org Subject: [SSSD-users] Re: millisecond time stamps
EXTERNAL
On 09/06/2017 03:35 PM, Galen Johnson wrote:
I'm not seeing a change in my logs...I added the following to the [sssd] section
debug_microseconds = true
You need to add it to all appropriate sections (same as debug_level) and restart SSSD. Having it in just [sssd] section will affect only the sssd monitor logs.
Also, I don't suppose that there is any way to include a transaction id to make it easier to trace interleaved log messages on a busy system?
I think there is no such way.
=G=
From: Galen Johnson Sent: Wednesday, September 6, 2017 9:27 AM To: End-user discussions about the System Security Services Daemon Subject: Re: [SSSD-users] Re: millisecond time stamps
wow...no wonder I missed it...I was looking for milli :-).
thanks
=G=
From: Lukas Slebodnik lslebodn@redhat.com Sent: Wednesday, September 6, 2017 1:37 AM To: End-user discussions about the System Security Services Daemon Subject: [SSSD-users] Re: millisecond time stamps
EXTERNAL
On (05/09/17 20:47), Galen Johnson wrote:
Hello,
Is it possible to get sssd to log millisecond timestamps? It only logs to the second and that makes it difficult correlate the flow through various logs while tracking a (potential) performance issue.
Sure.
man sssd.conf -> debug_microseconds
LS _______________________________________________ sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org _______________________________________________ sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org
sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org _______________________________________________ sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org
_______________________________________________ sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org
Opened #3506 (https://pagure.io/SSSD/sssd/issue/3506).
thanks
=G=
________________________________________ From: Jakub Hrozek jhrozek@redhat.com Sent: Wednesday, September 6, 2017 2:44 PM To: End-user discussions about the System Security Services Daemon Subject: [SSSD-users] Re: millisecond time stamps
EXTERNAL
I agree and I was pondering this for a long time but I could never think of a reasonable way that wouldn’t be too intrusive.
The only way I could think of was to have a structure that would be used as a parent context of tevent requests inside SSSD and internally track request nesting.
But yes, please go ahead and file the ticket, just please note this is not a totally trivial request.
On 6 Sep 2017, at 15:55, Galen Johnson Galen.Johnson@sas.com wrote:
Thanks. I figured it out right after I sent the email (isn't that usually the case? :-/)
As for the transaction id, where can I put in a feature request? It would be invaluable for debugging busy systems.
thanks
=G=
From: Michal Židek mzidek@redhat.com Sent: Wednesday, September 6, 2017 9:50 AM To: sssd-users@lists.fedorahosted.org Subject: [SSSD-users] Re: millisecond time stamps
EXTERNAL
On 09/06/2017 03:35 PM, Galen Johnson wrote:
I'm not seeing a change in my logs...I added the following to the [sssd] section
debug_microseconds = true
You need to add it to all appropriate sections (same as debug_level) and restart SSSD. Having it in just [sssd] section will affect only the sssd monitor logs.
Also, I don't suppose that there is any way to include a transaction id to make it easier to trace interleaved log messages on a busy system?
I think there is no such way.
=G=
From: Galen Johnson Sent: Wednesday, September 6, 2017 9:27 AM To: End-user discussions about the System Security Services Daemon Subject: Re: [SSSD-users] Re: millisecond time stamps
wow...no wonder I missed it...I was looking for milli :-).
thanks
=G=
From: Lukas Slebodnik lslebodn@redhat.com Sent: Wednesday, September 6, 2017 1:37 AM To: End-user discussions about the System Security Services Daemon Subject: [SSSD-users] Re: millisecond time stamps
EXTERNAL
On (05/09/17 20:47), Galen Johnson wrote:
Hello,
Is it possible to get sssd to log millisecond timestamps? It only logs to the second and that makes it difficult correlate the flow through various logs while tracking a (potential) performance issue.
Sure.
man sssd.conf -> debug_microseconds
LS _______________________________________________ sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org _______________________________________________ sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org
sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org _______________________________________________ sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org
_______________________________________________ sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-leave@lists.fedorahosted.org
sssd-users@lists.fedorahosted.org
-
Galen Johnson -
Jakub Hrozek -
Lukas Slebodnik -
Michal Židek