ELTRACT MONITOR
The web changes. Your selected data should be able to change with it.
ElTract Monitor connects a project to a repeatable schedule so selected public sources can be revisited and compared. The product supports monitor creation, schedules, manual runs, run history, detected changes, notifications and Web Memory context when the crawl runtime is deployed.
CAPABILITIES
What ElTract does here
Monitor a project
Create a monitor against an existing project instead of building a separate tracking script for the same source.
Manual, hourly, daily and weekly schedules
Choose the schedule modes currently exposed by the product and set the relevant timezone or expression.
Run history
Inspect monitor runs and the collection history behind each change rather than receiving an unexplained alert.
Detected changes
Review change events and connect them to Web Memory and notification context.
Manual run
Trigger a monitor run directly when you need a fresh comparison outside the normal schedule.
WORKFLOW
From input to working data
- Choose a collection project
Monitoring starts from a project whose source and fields are already defined.
- Set a supported schedule
Use manual, hourly, daily or weekly scheduling and the relevant timezone.
- Run the public source again
The crawl worker executes the collection work and persists monitor/run state.
- Review what changed
Inspect detected changes, history and notifications, then connect important events to Automate if configured.
WHY ELTRACT
Keep the data connected to the work
Selected data can stay current
A useful record does not have to become stale immediately after its first extraction.
Changes remain traceable
Monitor runs and Web Memory preserve context around the change instead of replacing the old value silently.
Monitoring can feed actions
Meaningful monitor events can become Automate triggers when that runtime is configured.
CURRENT BOUNDARIES
What not to assume
ElTract states availability directly so buyers do not have to infer capabilities from vague product language.
- Scheduled monitoring and change detection require `eltract-crawl-worker.service`, Redis and the crawl database contract to be healthy.
- The current product exposes manual, hourly, daily and weekly scheduling. Custom cron is not presented as a generally available schedule mode.
- Monitoring follows the same public-web boundary as Collect; authenticated crawler browser sessions are not currently available.
THE WEB, STRUCTURED.