| Summary: | RFE, high res log timestamps. | ||
|---|---|---|---|
| Product: | Red Hat Directory Server | Reporter: | wibrown <wibrown> |
| Component: | Documentation | Assignee: | Petr Bokoc <pbokoc> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Viktor Ashirov <vashirov> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 10.0 | CC: | mmuehlfe, nhosoi, nkinder, pbokoc, rhel-docs, rmeggins, wibrown |
| Target Milestone: | DS10.1 | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Feature: Increase accuracy of log timestamps by default. Logs change from:
[21/Mar/2016:12:00:59 +1000] conn=1 op=0 BIND dn="cn=Directory Manager" method=128 version=3
to
[21/Mar/2016:12:00:59.061886080 +1000] conn=1 op=0 BIND dn="cn=Directory Manager" method=128 version=3
This can be optionally disabled with nsslapd-logging-hr-timestamps-enabled: false in cn=config
Reason: Allows for detailed analysis of events in the directory server. External log systems can correctly rebuild and interleave logs from directory server.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-11-21 13:42:56 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
wibrown@redhat.com
2016-03-21 01:50:05 UTC
(In reply to wibrown from comment #0) > A new feature for high res log timestamps has been added for 1.3.5. This > will need documenting. > > Additionally, this adds a new configuration parameter > nsslapd-logging-hr-timestamps-enabled to cn=config to enable or disable the > use of these timestamps. > > Additional information: > https://fedorahosted.org/389/ticket/47982 I think we need to specify which doc needs to be updated. The config param is to be in Doc - config-command-file-reference. Also, we need to change the screen shot of this Viewing Log Files in the administration guide. https://access.redhat.com/documentation/en-US/Red_Hat_Directory_Server/10/html/Administration_Guide/Viewing_Log_Files.html Do you think there could be some more places to change? https://access.redhat.com/documentation/en-US/Red_Hat_Directory_Server/10/html/Administration_Guide/logconv-example.html We need to add way to disable the HR log timestamps in the logging section of maybe the admin guide somewhere. Viewing log files in the performance tuning guide also may need updating. Probably something in the release notes too. (In reply to wibrown from comment #2) > https://access.redhat.com/documentation/en-US/Red_Hat_Directory_Server/10/ > html/Administration_Guide/logconv-example.html > > > We need to add way to disable the HR log timestamps in the logging section > of maybe the admin guide somewhere. > > Viewing log files in the performance tuning guide also may need updating. > > Probably something in the release notes too. Thanks, William! Regarding the release notes, could you put your input to the "Doc Text:" box in this bug? https://bugzilla.redhat.com/show_bug.cgi?id=1273549 No need to be detailed. Just, if you could add items to be added, I'd greatly appreciate it. Thanks, in advance! Will, in the doc text you're saying that it can be disabled by setting "nsslapd-logging-hr-timestamps-enabled: false", implying that valid values are true|false. At the same time, I took a look at patches in the upstream ticket and those imply that valid values are on|off, which would be consistent with many other attributes too - but then again I'm just guessing. So, is that a mistake in the doc text, or are valid values really true|false? Thanks, Petr According to the code I wrote, it looks like the only valid value for enabling is "on". Anything else is treated as "disabled, false, off" etc. Sorry, forgot to set a needinfo. Will, can you please take a look and let me know if everything in c#8 is correct? The update for Directory Server 10.1 is now available on the Customer Portal. |