Pull Schedule and Exclusions¶
How often MetaMiner pulls each kind of metadata, and how to pause pulls during busy hours with "Do Not Disturb" windows.
How pulls are scheduled¶
Each enabled environment has its own pull cycle in the MetaMiner Server (MMS). A cycle collects only the object types that are due, and only objects that changed since the last cycle.
| What | Default interval | Where to change it |
|---|---|---|
| Basic object metadata (users, groups, folders, documents, universes, connections and so on) | 5 minutes per type | Not in MMA; see the note below |
| Web Intelligence deep processing | 5 minutes | Settings > Pull > Webi Metadata pull period |
| Universe deep processing | 5 minutes | Settings > Pull > Universe Metadata pull period (min) |
| New, imported and deleted object scan | 15 minutes | Not configurable in MMA |
| Audit events | 20 minutes | Settings > Audit > Audit pull delay |
| Server metrics | 300 seconds | Not configurable in MMA |
| Web Intelligence real-time metrics | 3 seconds | Settings > Pull > Webi RTM pull period |
| Folder security (rights) | Every 30 minutes | Not configurable in MMA |
The first pull of a new environment reads everything and can take hours on large systems. Later cycles are incremental.
Per-type intervals
Per-type intervals for basic metadata are stored with each environment in config.json. Change them only with Infolytik Support.
Do Not Disturb windows¶
A "Do Not Disturb" window pauses pulling of one pull type for an environment during a daily time range, for example during nightly batch scheduling or backups.
Image of the Advanced tab of the environment dialog with Documents (basic) selected, Do Not Disturb enabled from 01:00 to 05:00
../../images/admin/bo-environment-do-not-disturb.png
| Field | What it does |
|---|---|
| Pull types: | List of pull types, for example Users, Groups, Folders, Documents (basic), Universes (basic), Webi (BI4), UNX (deep), UNV (deep), Crystal Reports (deep), CMS Sessions, plus Connectivity Check |
| Enable "Do Not Disturb" period | Turns the window on for the selected pull type |
| MetaMiner Server time zone: | The time zone the window is evaluated in (MMS local time) |
| From: | Start time (hour and minute) |
| End by: | Time to give an end time, or Hours to give a duration |
| To/After: | End time, or duration in hours and minutes |
| Apply for all pull types | Copies the current window to every pull type |
Connectivity Check is special: a window on it suppresses connection-failure notification emails for the environment during that time.
Steps¶
- Select the environment in BI Environments and click Edit.
- Open the Advanced tab.
- Select a pull type in Pull types:.
- Check Enable "Do Not Disturb" period.
- Set From: and, with End by: Time, set To/After:.
- Optional: click Apply for all pull types.
- Click Apply.
End time after start time
With End by: Time the end must be later than the start on the same day; MMA shows "The end time should be after the start time." otherwise.
TODO: verify windows that cross midnight and the Hours option
Confirm with QA how a window that crosses midnight should be entered (Hours duration or two settings) and that End by: Hours is honoured by both the pull engine and the notification suppression.
Verify¶
- During the window,
server.logshows no pull activity for the paused type on that environment. - The next cycle after the window catches up on changes made during it.