Flows
What are flows?
Flows are batch jobs that move and transform data. Collectively, they constitute the Data pipeline part of the Monitorfish architecture.
Each batch job is written as a Prefect flow which typically extracts data (from external sources and / or from tables in the Monitorfish database), processes the data and loads it back into a table of the Monitorfish database.
Flows are composed of tasks typically written as python pure functions. The UI (restricted access) enables administrators to view each flow as a diagram of its constituent tasks, to monitor their execution, see the logs and debug in case any flow run fails…
Overview of flows in Monitorfish
Flow that imports administrative areas :
Flows that import repositories (species, gears, infractions…) :
Flows that import and perform a check-up on regulations data :
Flows that perform computations that are internal to Monitorfish (alerts, fishing detection…):
Flows that contribute to maintaining an up-to-date last_positions table :
List of flows
- Activity visualizations
- Administrative areas
- Anchorages
- Beacons
- Control anteriority
- Control units
- Controls
- Controls open data
- Current segments
- Distribute pnos
- Districts
- Email actions to units
- Enrich logbook
- Enrich positions
- Facade areas
- FAO areas
- Fishing gears
- Foreign fmcs
- Infractions
- Last Positions
- Logbook
- Missions
- Missing dep alerts
- Missing FAR alerts
- Missing trip numbers
- Notify beacon malfunctions
- Ports
- Position alerts
- Recompute controls segments
- Refresh materialized view
- Regulations check-up
- Regulations
- Risk factor
- Scrape Legipeche
- Species groups
- Species
- Suspicions of under declaration alerts
- Update beacon malfunctions
- Validate pending alerts
- Vessels
- Vessel profiles