Audit¶
Reference for the Audit page of Preferences > Settings..., which controls how MetaMiner collects BusinessObjects audit data.
Audit collection also needs an Audit database configured on each environment; see Audit and CMS Databases.
Image of the Settings dialog, Audit page, with Audit Pull Settings and Audit User Exclusion
../../images/admin/settings-audit.png
Audit Pull Settings¶
| Field | Default | Range | What it does | Config key |
|---|---|---|---|---|
| Pull Audit Data | On | - | Turns audit collection on for all environments that have an Audit database | cms.pull.extendedaudit |
| Audit # days history to pull: | 550 | 30 - 90000 | How far back the first audit pull starts when the MetaMiner Database (MMDB) has no audit data yet | audit.days.ago |
| Audit pull delay: | 20 | 5 - 5000 | Minutes between audit pulls | cms.pull.audit.delay |
| Audit DB Connection pull size: | 5 | 4 - 30 | Maximum connections MetaMiner opens to each Audit database | audit.cfg.max.pool.size |
History depth and MMDB size
A large audit history can be very large. Do not set Audit # days history to pull far back unless the MMDB is sized for it. See Sizing and Capacity.
After the first pull MetaMiner reads only new events, and periodically re-reads recent days to pick up events that arrived late in the Audit database.
Audit User Exclusion¶
| Field | Default | What it does | Config key |
|---|---|---|---|
| Exclusion list | Empty | Audit actions by these BusinessObjects users are not used for the "Action by" column in the MMC CMS Explorer, so it shows end-user activity instead of administrator or service-account activity | audit.username.exclusions |
Enter user names separated by commas, without spaces, for example Administrator,mmadmin. Single quotes around each name are optional. The account MetaMiner uses for each environment is always excluded.