|
|
|
|
|
|
by Mamady
4704 days ago
|
|
|
This sounds reallly interesting, but it feels very painful for reporting. Trying to run reports on this type of data for a dashboard seems out of the question. I understand adhoc research is done via command line, but if you wanted to have a dashboard which shows stats, how would you handle that? I assume you would have to import into a db of some sort to run queries regularly? |
|
|
Yes we've saved it mainly to look at it later. It's the lowest level of detail so I figure we can mine it later. To do anything useful with it it would have to be processed though I don't think it's that much.
> I understand adhoc research is done via command line, but if you wanted to have a dashboard which shows stats, how would you handle that?
We don't use those files for reporting. We have user stat reports (activity, actions, etc) generated and look at the numbers themselves but nothing I'd consider "pretty". All of those are generated from the audit trail data so it's already in a database. The ad-hoc reporting from the command line is if I want to trace something specific in detail. I've usually filtered it down to small enough set that grep/awk is more than enough and it only takes a couple seconds.