alarm_analysis:data_retention
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
alarm_analysis:data_retention [2019/11/18 15:55] – su | alarm_analysis:data_retention [2023/12/29 13:42] (current) – su | ||
---|---|---|---|
Line 14: | Line 14: | ||
Source Alarm & Event (A&E) data arrives on the import flow and is stored for later processing. We call this the **A&E Raw Data Cache**. | Source Alarm & Event (A&E) data arrives on the import flow and is stored for later processing. We call this the **A&E Raw Data Cache**. | ||
- | Data is stored in monthly indices determined by date of arrival. This may be different to the date of the actual event record | + | Data is stored in monthly indices determined by date of arrival. This may be different to the date of the actual event record |
For an ongoing (near real-time) data flow, the monthly indices of raw data will be closely aligned with A&E event time. However, exceptions may occur. For example, importing a large historical backlog. | For an ongoing (near real-time) data flow, the monthly indices of raw data will be closely aligned with A&E event time. However, exceptions may occur. For example, importing a large historical backlog. |
alarm_analysis/data_retention.txt · Last modified: 2023/12/29 13:42 by su