#47533 logconv: some stats do not work across server restarts
Closed: wontfix Opened by rmeggins.

logconv keeps most stats in hashes keyed on connid,opid. These are not unique - the server resets conn=1 upon restart. logconv needs to keep unique stats across restarts.


0001-logconv-some-stats-do-not-work-across-server-restart.patch
0001-logconv-some-stats-do-not-work-across-server-restart.patch

Nice! Ack.

I've been wondering about our unindexed search report. I see a lot of reported unindexed searches with a etime of zero. Should/can these be ignored if the etime is < 1 ? I have a access log from a customer that has 1500 unindexed searches, but most of them are etime of 0. It just kills the scripts performance, for what appears to be harmless unindexed searches.

2nd ack.

It's not an issue at all, but some time we have a chance, it'd be nice if we remove "./" from the Examples since logconv.pl is now in /bin, and replace "/logs/" with something like "/path/to/logs/"?
{{{
print " Examples:\n\n";

print "         ./logconv.pl -s 10 -V /logs/access*\n\n";
print "         ./logconv.pl --rootDN cn=dm /logs/access*\n\n";
print "         ./logconv.pl --sizeLimit 50 -ibgju /logs/access*\n\n";
print "         ./logconv.pl -S \"\[28/Mar/2002:13:14:22 -0800\]\" --endTime \"\[28/Mar/2002:13:50:05 -0800\]\" -e /logs/access*\n\n";
print "         ./logconv.pl -m log-minute-stats-csv.out /logs/access*\n\n";
print "         ./logconv.pl -B ANONYMOUS /logs/access*\n\n";
print "         ./logconv.pl -B \"uid=mreynolds,dc=example,dc=com\" /logs/access*\n\n";

}}}

I wouldn't want to ignore unindexed searches by default - even though the etime is 0, it's still causing possibly unnecessary load. Perhaps another flag like -T unindexedEtimeMin

You could use this new version of logconv.pl with the -U flag - this gives you a quicker summary report of unindexed searches.

To ssh://git.fedorahosted.org/git/389/ds.git
65aa3e0..92ac8f4 master -> master
commit 92ac8f48c1e5a8a049f4cfd1912fd570c628408f
Author: Rich Megginson rmeggins@redhat.com
Date: Fri Sep 27 11:08:29 2013 -0600

Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1013165

To ssh://git.fedorahosted.org/git/389/ds.git
fbece32..313dd8e 389-ds-base-1.2.11 -> 389-ds-base-1.2.11
commit 313dd8ecf483bda7dad774afba7d624275ab6ba1
Author: Rich Megginson rmeggins@redhat.com
Date: Fri Sep 27 11:08:29 2013 -0600

To ssh://git.fedorahosted.org/git/389/ds.git
c96eaa0..9103b3e 389-ds-base-1.3.0 -> 389-ds-base-1.3.0
commit 9103b3e3812fd2cd05f281729e017c46f1c841e5
Author: Rich Megginson rmeggins@redhat.com
Date: Fri Sep 27 11:08:29 2013 -0600

To ssh://git.fedorahosted.org/git/389/ds.git
ff9a292..e38685b 389-ds-base-1.3.1 -> 389-ds-base-1.3.1
commit e38685be139c2420cc969499324405a30203122a
Author: Rich Megginson rmeggins@redhat.com
Date: Fri Sep 27 11:08:29 2013 -0600

Metadata Update from @rmeggins:
- Issue assigned to rmeggins
- Issue set to the milestone: 1.2.11.24

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/870

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)

Metadata