At the moment I have been helping a student with their higher education thesis. As part of
this we need to understand realistic work loads from 389-ds servers in production.
To assist, I would like to ask if anyone is able to or willing to volunteer to submit
sanitised content of their access logs to us for this. We can potentially also use these
for 389-ds for benchmarking and simulation in the future.
An example of the sanitised log output is below. All DN's are replaced with UUID's
that are randomly generated so that no data can be reversed from the content of the access
log. The script uses a combination of filter and basedn uniqueness, and nentries to make a
virtual tree, and then substitute in extra data as required. All rtimes are relative times
of "when" the event occured relative to the start of the log, so we also do not
see information about the time of accesses.
This data will likely be used in a public setting, so assume that it will be released if
provided. Of course I encourage you to review the content of the sanitisation script, and
the sanitised output so that you are comfortable to run this tool. It's worth noting
the tool will likely use a lot of RAM, so you should NOT run it on your production server
- rather you should copy the production access log to another machine and process it
1 hour to 24 hours of processed output from a production server would help a lot!
Please send the output as a response to this mail, or directly to me ( wbrown at suse dot
python3 access_pattern_extract.py /path/to/log/access /path/to/output.json
Senior Software Engineer, 389 Directory Server
SUSE Labs, Australia
Show replies by date