Monitoring is available on Pro and Advanced plans. See osint.ly/pricing for current limits.
Daily operations
Review monitor health
Open Monitoring and scan active monitors, last run timestamps, and recent alert volume.
Triage new alerts
Prioritize alerts by severity and target criticality before updating workflow status.
Validate channel delivery
Confirm email and Discord webhook delivery for alerts generated in the last period.
Monitor configuration standards
| Field | Standard |
|---|---|
| Monitor name | Include case or client identifier + target |
| Frequency | Start daily, then increase only if investigation needs it |
| Type | Match target shape (Email Registration, Global Search, Module Query) |
| Ownership | Keep monitors inside the correct solo or team workspace |
Alert workflow
new
new
Initial state after alert creation. Requires triage.
investigating
investigating
Analyst is validating signal quality and impact.
resolved
resolved
Investigation action completed and no pending follow-up.
Failure patterns and actions
- No alerts expected
- No alerts but changes expected
- Channel delivery failed
- Confirm monitor is active
- Confirm target and type are valid
- Verify schedule frequency
- Check whether the underlying data source has new events
Capacity and cost hygiene
- Keep high-frequency monitors only for high-priority targets
- Review monitor count weekly against plan limits
- Use history and project context to avoid duplicate monitors
- Archive resolved investigations to keep alert queues actionable
Related resources
- Product support: osint.ly/support
- Community: osint.ly/community
- Sales/support for plan changes: osint.ly/support/sales
- Documentation hub: docs.osint.ly