How Redline Builds Reports

How does Redline build the reports?

Redline parses data from three reports that GWCheck builds for it.

• gwaudit.log
• mbstat.log
• gwstat.log

gwaudit.log

For each user, Redline begins by finding "audit report for", parses the data, and ends with "processing complete"

The end of the users section is determined by "job log summary"

The end of the log is determined by "overall processing time"

One thing to watch out for is if the log is built badly if a user does not have a "processing complete" section the next user(s) will overwrite their data.

mbstat.log

For each user, Redline begins by finding "task log", parses the data, and ends with "processing complete". When Redline finds the end of the life it stops.

Some sections will be prime users, which are users that have access to a shared a document through a public folder with a user providing the document on a different PO.

gwstat.log

For each user, Redline begins by finding "task log", parses the data, and ends with "processing complete". When Redline finds the end of the life it stops.

This article was originally published in the GWAVA knowledgebase as article ID 2740.