Sure it is. Just work out your logparser query to get only the events you want from the appropriate event log, that would be something along the lines of this if your messages are in the Application log;
LogParser "SELECT * FROM Application WHERE SourceName='BLAH' AND EventType = 8 AND EventCategoryName = 'BLAHBLAH'" -i:evt
Play around with this until you have refined this and got only the events in which you are interested, then you can adapt the query I gave you to look something like this;
select extract_token(EXTRACT_TOKEN( Message, -1, 'user' ),1,' ') as User,
trim(extract_token(EXTRACT_TOKEN( Message, -1, 'on printer' ),0,'on port ')) as Printer,
count(*) as Documents,
sum(to_int(extract_token(EXTRACT_TOKEN( Message, -1, ':' ),1,' '))) as Pages
from EventLog
where SourceName='BLAH'
and EventType = 8
and EventCategoryName = 'BLAHBLAH'
group by User, Printer
and run it like this;
logparser file:print.sql -i:evt
Obviously replace the bolded portions with your own criteria. You may not need to use more than one criteria if your logging application is definitive enough.
When you have got this right, then you can play with the output format options to insert this straight into a text report, CSV, XML, datagrid, database or whatever takes your fancy.