Scraping Failure Alerts: Email and Telegram Notifications

Scraping Failure Alerts: Why and When?

Parser went down at night — by morning data is stale and no one knows why. We've seen this in 80% of projects where monitoring was limited to logs. An alert system solves it: the right person gets a notification about a parsing failure the moment it occurs — via Telegram or email, with enough context for diagnosis. Without such notifications, an engineer spends hours hunting for the cause while client data remains outdated.

Automatic alerts aren't a luxury; they're a necessity for any scraping pipeline. Lack of monitoring leads to data loss and reputational risk. For example, a change in the target site's structure can go unnoticed for days until an empty result piles up. Our turnkey implementation — from design to deployment — lets you quickly add alerts to any parser on any stack, saving up to 10 hours of troubleshooting per month.

Which Events Require an Alert?

Not every error is a failure. A single timeout is normal — the worker will retry. The alert system triggers on:

• Task exhausted all retries (moved to DLQ or failed finally)
• Worker crashed (process crash, OOM)
• Error rate exceeded threshold in the last 15 minutes (e.g. >20%)
• Scraping a site didn't finish within expected time (watchdog timeout)
• Page structure changed — parser returns empty data

Which Notification Channel: Telegram or Email?

We usually recommend Telegram for P1-level alerts (site down) and email for less urgent events. In our experience, a hybrid scheme cuts engineer response time by 3–4x.

Why Telegram Is Best for Critical Failures?

Telegram messages arrive 10–30 times faster than email via SMTP and aren't subject to spam filters. In our projects, the time from failure to alert receipt via Telegram never exceeds 2 seconds. For tasks where every second of downtime costs money, Telegram is the only choice. According to the Telegram Bot API documentation, messages are delivered almost instantly.

Telegram: Bot Setup and Alert Sending

Example code for sending notification via Telegram Bot API:

import httpx
import textwrap

async def send_telegram_alert(bot_token: str, chat_id: str, event: dict):
    text = textwrap.dedent(f"""
        🔴 <b>Parsing Failure</b>

        <b>Site:</b> {event['site_name']}
        <b>URL:</b> <code>{event['url']}</code>
        <b>Error:</b> {event['error_type']}
        <b>Message:</b> <code>{event['error_message'][:300]}</code>
        <b>Attempts:</b> {event['attempts']}
        <b>Time:</b> {event['timestamp']}
    """).strip()

    async with httpx.AsyncClient() as client:
        await client.post(
            f"https://api.telegram.org/bot{bot_token}/sendMessage",
            json={"chat_id": chat_id, "text": text, "parse_mode": "HTML"},
            timeout=10,
        )

Email: SMTP and SendGrid Setup

For email, you can use SMTP (smtplib with TLS) or SendGrid for better deliverability. Example with SendGrid:

from sendgrid import SendGridAPIClient
from sendgrid.helpers.mail import Mail

def send_email_alert(to_email: str, event: dict):
    message = Mail(
        from_email='[email protected]',
        to_emails=to_email,
        subject=f"[Scraping] Failure: {event['site_name']}",
        html_content=render_alert_template(event),
    )
    sg = SendGridAPIClient(api_key=SENDGRID_API_KEY)
    sg.send(message)

How Deduplication Prevents Alert Spam?

Without deduplication, a mass failure (proxy provider down) would trigger 500 emails per minute. The solution is grouping by key with a cooldown. One alert per error type per 30 minutes is a reasonable balance between informativeness and noise. In our practice, this reduces notifications by 95% while preserving critical information.

def should_send_alert(site_id: int, error_type: str, cooldown_minutes: int = 30) -> bool:
    key = f"alert_sent:{site_id}:{error_type}"
    if redis.exists(key):
        return False
    redis.setex(key, cooldown_minutes * 60, "1")
    return True

Example configuration with Redis:

import redis
import os

r = redis.Redis.from_url(os.environ["REDIS_URL"])
COOLDOWN = 30  # minutes

def should_send_alert(site_id, error_type):
    key = f"alert_sent:{site_id}:{error_type}"
    if r.exists(key):
        return False
    r.setex(key, COOLDOWN * 60, "1")
    return True

How to Set Up Telegram Notifications in 15 Minutes?

1. Create a bot via @BotFather and get the token.
2. Determine chat_id (use @userinfobot).
3. Integrate the send_telegram_alert function into your parser.
4. Trigger it on failure events.
5. Test sending.

Implementation Process: From Analysis to Deployment

• Design alert scheme (channels, thresholds, cooldown).
• Develop notification code (Telegram bot / SendGrid / SMTP).
• Implement deduplication with Redis or in-memory.
• Integrate with your parser (webhook or API).
• Documentation and team training.
• Support for 2 weeks after delivery.

Timeline and Cost

Basic solution (Telegram + email with deduplication) — from 1 to 2 business days. If integration with existing monitoring or custom rules is needed — up to 5 business days. Cost is calculated individually based on complexity: contact us for a free project estimate.

Experience and Guarantees

We've built monitoring systems for projects with 10 million requests per day. Over 5 years of experience in scraping and 50+ successful implementations ensure that alerts won't miss a critical failure. Order an alert system implementation — and always stay informed about your scraping status.

Backend Development Services: Laravel, Node.js, Go, Django, PostgreSQL

On a production server at 3:14 AM, the Laravel Jobs queue stopped processing. 40,000 unprocessed jobs in Redis. Cause: worker crashed due to a memory leak in one of the Jobs (leak via a static variable in an Eloquent observer), supervisor didn't restart it because of misconfigured stopwaitsecs. This is not a hypothetical scenario — it's Tuesday. We analyzed such an incident on a project with 500 RPS load: diagnosis took 4 hours, fix — 20 minutes. So you don't lose money on downtime, we offer backend development services with a focus on production-grade reliability. We'll assess your project in 2 days.

Backend is what works when no one is watching. Or doesn't work. We guarantee you'll have the first option.

How do we ensure production-grade reliability from day one?

What we do correctly from day one

Service Layer over Fat Controllers. Controller receives HTTP request, validates it via Form Request, passes data to Service, returns response. Business logic in Service, not Controller. This sounds trivial, but most legacy projects have controllers with 500 lines and SQL queries inside.

Repository Pattern we use cautiously. If you just wrap Model::where(...) in a repository method — that's boilerplate without benefit. Repository is justified when: you need to abstract from the data source (DB + cache + external API) or when query logic is complex enough to isolate.

Jobs, Events, Listeners. Everything that can be async — make async. Sending email, PDF generation, external API sync, aggregate recalculation — into Queue. Laravel Horizon for queue monitoring in Redis: see throughput, failed jobs, processing time per queue.

How Octane handles high load

Laravel Octane with RoadRunner or Swoole keeps the app in memory between requests — removes bootstrap overhead (config loading, class autoloading) on each HTTP request. Gain: 3–8x on synthetic benchmarks, 2–4x on real applications. Important: no state between requests in static variables — that leads to exactly the incidents from the beginning. We use this in projects with >1000 RPS.

What to do about N+1 queries

N+1 is the most common cause of slow pages in Laravel apps. Standard story: page worked fine on dev with 10 records, on production with 10,000 — 8-second load.

Laravel Debugbar in dev environment shows the number of queries per page. More than 20 queries per page — signal for audit.

Model::preventLazyLoading(! app()->isProduction());

Telescope for profiling in staging: logs all queries, jobs, mail, notifications with time detail. Numbers: after implementing eager loading, page load time drops from 8s to 0.3s — 27 times faster.

PostgreSQL: indexes that are actually needed

PostgreSQL 14+ is the primary DB on all projects. We use PgBouncer + PostgreSQL combination. 10+ years experience, more than 50 backend projects, 5 years on the market.

How PostgreSQL helps avoid slow queries

Composite indexes for frequent WHERE + ORDER BY. If you have WHERE user_id = ? AND status = ? ORDER BY created_at DESC — you need (user_id, status, created_at DESC). A separate index on (user_id) doesn't help much with sorting.

Partial indexes. If 95% of queries go with WHERE status = 'active':

CREATE INDEX idx_orders_active ON orders (created_at DESC)
WHERE status = 'active';

The index is small, fast, covers the main load.

GIN indexes for JSONB and arrays. @> operator without GIN index — seq scan. With index — fast even on millions of rows.

GIN for full-text search. to_tsvector + GIN instead of LIKE '%query%'. LIKE without index is always seq scan. With pg_trgm extension and gin_trgm_ops — supports LIKE with index, useful for CRM search by partial match.

Connection pooling: why it's more important than it seems

Rails, Laravel, Django open a new connection to PostgreSQL for each PHP/Python process. With 100 workers — 100 connections. PostgreSQL starts degrading from 200–300 active connections — overhead on connection management becomes significant.

PgBouncer — connection pooler in front of PostgreSQL. Transaction pooling mode: connection to PostgreSQL is occupied only during a transaction, returned to pool between requests. 1000 application workers → 20–50 actual connections to PostgreSQL. This reduces latency by 40% and hosting costs by 30%.

Node.js with Fastify: when it's better than Laravel

Node.js is justified for:

• Realtime: WebSocket servers, Server-Sent Events, chat, live updates
• Streaming: large files, video, streaming data
• High I/O concurrency: many parallel requests to external APIs without heavy business logic
• Serverless: Lambda/Cloud Functions — Node.js starts faster than PHP

Fastify over Express: 2–3 times faster on benchmarks, built-in JSON Schema validation, better TypeScript support, plugin architecture.

Typical realtime architecture: Laravel — core business logic and REST API. Node.js + Socket.io or ws — WebSocket server. Laravel publishes events to Redis Pub/Sub, Node.js subscribes and broadcasts to clients. This separation allows scaling the WebSocket server independently of the main app.

Go: microservices and high load

Go we use for:

• High-load microservices (>10,000 RPS)
• Background workers with strict latency requirements
• DevOps tools and CLI
• gRPC services in microservice architecture

Goroutines — thousands of times cheaper than OS threads. 10,000 concurrent connections on Go is normal on one server.

But Go is not a silver bullet. Development is slower than Laravel: more boilerplate, no ORM at Eloquent level, error handling with if err != nil everywhere. Justified only when performance is a real requirement, not an assumption.

Django and Python backend

Django with DRF (Django REST Framework) — for tasks where Python is needed: ML pipelines, data processing, integrations with AI tools.

Celery for background tasks — similar to Laravel Queue but more complex to configure. Celery Beat for cron tasks.

Django ORM vs raw SQL: ORM is convenient for CRUD. For analytical queries with multiple JOINs, window functions, and CTEs — connection.execute() with raw SQL is more readable and predictable.

Redis: not just cache

Redis in our projects plays multiple roles:

Redis Cluster for horizontal scaling. Sentinel for automatic failover on standalone setups.

Deployment and infrastructure

Docker + docker-compose — standard for local development and production. Each service in a container: PHP-FPM/Octane, Nginx, PostgreSQL, Redis, Queue Worker, Scheduler.

CI/CD via GitHub Actions:

1. Run tests (PHPUnit / Pest, Vitest, Playwright)
2. Build Docker image
3. Push to Container Registry
4. Deploy: docker pull → docker-compose up -d on server, or Kubernetes rolling update

Zero-downtime deploy for Laravel: php artisan down --secret=TOKEN is not needed with proper configuration. Strategy: new container starts next to the old one, Nginx switches traffic after health check, old container stops.

Monitoring: Sentry for exception tracking with alerting in Slack/Telegram. Grafana + Prometheus (or Grafana Cloud) for metrics: CPU, memory, request rate, queue depth, database connection count. Alerts on: error rate > 1%, p99 latency > 2s, queue depth > 1000 jobs.

What's included in turnkey work

• Architecture design (API documentation, DB schema, service diagram)
• Implementation according to agreed specification with code review
• CI/CD, monitoring, alerting setup
• Load testing (k6, wrk) with report
• Handover of source code, access, deployment instructions
• Training of customer's team (2-3 sessions)
• Warranty support for 1 month after delivery

Timeline benchmarks

Pricing is calculated individually after analyzing load, integrations, and business logic. Contact us for a free audit of your current backend — get an optimization plan in 2 days. Request a consultation.