When we have WARC import errors, we should send them to Sentry so we have better telemetry and metrics about what is failing. For example, this run: https://github.com/edgi-govdata-archiving/web-monitoring-crawler/actions/runs/18421870440/job/52497363504 ``` No WARC records for seed: "https://marine.usgs.gov/coastalchangehazardsportal/" ``` Most of the work for this will be over in [`warc_import.py`](https://github.com/edgi-govdata-archiving/web-monitoring-processing/blob/main/web_monitoring/cli/warc_import.py) in the [-processing repo](https://github.com/edgi-govdata-archiving/web-monitoring-processing/), but we also need to set the `SENTRY_DSN` env var/secret here.
When we have WARC import errors, we should send them to Sentry so we have better telemetry and metrics about what is failing. For example, this run: https://github.com/edgi-govdata-archiving/web-monitoring-crawler/actions/runs/18421870440/job/52497363504
Most of the work for this will be over in
warc_import.pyin the -processing repo, but we also need to set theSENTRY_DSNenv var/secret here.