Hi Hari, Good idea, but does logstash handle intertwined logs, as per ...
21/Apr/2009:11:39:51 -0700] conn=11 fd=608 slot=608 connection from 207.1.153.51 to 192.18.122.139 [21/Apr/2009:11:39:51 -0700] conn=11 op=0 BIND dn="cn=Directory Manager" method=128 version=3 [21/Apr/2009:11:39:51 -0700] conn=11 op=0 RESULT err=0 tag=97 nentries=0 etime=0 [21/Apr/2009:11:39:51 -0700] conn=11 op=1 SRCH base="dc=example,dc=com" scope=2 filter="(mobile=+1 123 456-7890)" [21/Apr/2009:11:39:51 -0700] conn=12 fd=634 slot=634 connection from 207.1.153.51 to 192.18.122.139 [21/Apr/2009:11:39:51 -0700] conn=11 op=1 RESULT err=0 tag=101 nentries=1 etime=3 notes=U [21/Apr/2009:11:39:51 -0700] conn=12 op=0 BIND dn="cn=Directory Manager" method=128 version=3 [21/Apr/2009:11:39:51 -0700] conn=11 op=2 UNBIND [21/Apr/2009:11:39:51 -0700] conn=11 op=2 fd=608 closed - U1 [21/Apr/2009:11:39:51 -0700] conn=12 op=0 RESULT err=0 tag=97 nentries=0 etime=0 [21/Apr/2009:11:39:52 -0700] conn=12 op=1 SRCH base="dc=example,dc=com" scope=2 filter="(uid=bjensen)" [21/Apr/2009:11:39:52 -0700] conn=12 op=2 ABANDON targetop=1 msgid=2 nentries=0 etime=0 [21/Apr/2009:11:39:52 -0700] conn=13 fd=659 slot=659 connection from 207.1.153.51 to 192.18.122.139 [21/Apr/2009:11:39:52 -0700] conn=12 op=3 UNBIND [21/Apr/2009:11:39:52 -0700] conn=12 op=3 fd=634 closed - U1 [21/Apr/2009:11:39:52 -0700] conn=13 op=0 BIND dn="cn=Directory Manager" method=128 version=3 [21/Apr/2009:11:39:53 -0700] conn=13 op=0 RESULT err=0 tag=97 nentries=0 etime=0 [21/Apr/2009:11:39:55 -0700] conn=14 fd=700 slot=700 connection from 207.1.153.51 to 192.18.122.139 [21/Apr/2009:11:39:53 -0700] conn=13 op=1 EXT oid="2.16.840.1.113730.3.5.3" [21/Apr/2009:11:39:53 -0700] conn=13 op=1 RESULT err=0 tag=120 nentries=0 etime=0 [21/Apr/2009:11:39:53 -0700] conn=13 op=2 ADD dn="cn=Sat Apr 21 11:39:51 MET DST 2009, dc=example,dc=com" [21/Apr/2009:11:39:55 -0700] conn=14 op=0 BIND dn="" method=sasl version=3 mech=DIGEST-MD5 [21/Apr/2009:11:39:53 -0700] conn=13 op=2 RESULT err=0 tag=105 nentries=0 etime=0 csn=3b4c8cfb000000030000 or where there are multiple actions to record for one connection ... for example, one could do one connection/bind then multiple searches before unbinding or closing the session. Basically, I need to do this and at present I am thinking of possibly expanding logconv.pl to do this as it has extensive 'knowledge' of such logs. What I do author, I will submit back into the appropriate opensource project. Thanks Burn On Fri, 2015-07-03 at 18:31 +0000, Mailvaganam, Hari wrote: > If MMR - perhaps via log consolidation - e.g. ELK stack (grok filter)? > > Similar to https://discuss.elastic.co/t/how-filter-openldap-logs/2492. > ________________________________________ > From: [email protected] > [[email protected]] on behalf of Burn Alting > [[email protected]] > Sent: Friday, July 03, 2015 04:49 > To: [email protected] > Subject: [389-users] 389-ds access.log parsing - turning LDAP request type > into an audit event > > Has anyone authored code to parse a 389 Directory Server's access.log > file(s) with an aim of generating audit events based around the LDAP > request type. Basically, take the log sequence > > [21/Apr/2007:11:39:51 -0700] conn=11 fd=608 slot=608 connection from > 207.1.153.51 to 192.18.122.139 > [21/Apr/2007:11:39:51 -0700] conn=11 op=0 BIND dn="cn=Directory > Manager" method=128 version=3 > [21/Apr/2007:11:39:51 -0700] conn=11 op=0 RESULT err=0 tag=97 > nentries=0 etime=0 > [21/Apr/2007:11:39:51 -0700] conn=11 op=1 SRCH > base="dc=example,dc=com" scope=2 filter="(uid=bjensen)" > [21/Apr/2007:11:39:51 -0700] conn=11 op=1 RESULT err=0 tag=101 > nentries=1 etime=1000 notes=U > [21/Apr/2007:11:39:51 -0700] conn=11 op=2 UNBIND > [21/Apr/2007:11:39:51 -0700] conn=11 op=2 fd=608 closed - U1 > > And turn this into an audit event with > > a date/time (21/Apr/2007:11:39:51 -0700), a client location > (207.1.153.51), server location (192.18.122.139), a user (cn=Directory > Manager), an event (SRCH) and event metadata of (query - > base="dc=example,dc=com" scope=2 filter="(uid=bjensen)", result set size > - 1, timetaken = 1000 sec, etc) > > The logconv.pl script seems to do all sorts of analysis, but no event > representation. > > Thanks in advance > > -- > 389 users mailing list > [email protected] > https://admin.fedoraproject.org/mailman/listinfo/389-users -- 389 users mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/389-users
