Comprehensive Crash Alert and Monitoring Setup for 1C-Bitrix

With over 10 years of experience and 200+ successful monitoring deployments for 1C-Bitrix, we guarantee a robust solution. Have you noticed that your site can be unavailable for hours, and you only find out when a customer calls? On one project we saw that the catalog was working, but the cart was failing every 10 minutes — built-in monitoring didn't catch it. A 500 error on the checkout page hung for a day until logs were checked manually. Average downtime without monitoring is 4 hours, leading to a loss of up to 35% of orders and up to $2,000/month in revenue. With an administrator's hourly rate around $50, monthly losses can exceed several thousand dollars. Without external monitoring, you risk losing up to 30% of conversions if downtime exceeds 5 minutes. Our Bitrix crash alerts notify you instantly via Telegram, reducing downtime by 95%. Let's break down what to monitor and how to configure it on 1C-Bitrix.

What exactly to monitor

The minimum set of checkpoints includes 10 critical pages — catalog, cart, checkout — checked every 3 minutes. Additional metrics:

• HTTP status of the main page and 10 critical pages — catalog, cart, checkout. If /catalog/ returns 200 but /personal/order/make/ returns 500, a general healthcheck on the main page won't reveal it. Check every 3 minutes.
• Cron functionality — Bitrix agents (/bitrix/modules/main/tools/cron_events.php) must run regularly. Check by the last successful start date in the b_agent table. Missing 2+ runs — alert.
• MySQL/MariaDB availability — check not just the connection but execute a test SELECT. Max connections usually 500, exceeding triggers an error. Bitrix shows a white screen without logging when DB connection is lost.
• Free disk space — when /tmp or the partition with upload/ fills up, the site starts throwing session and cache write errors. Alert at <10% free space.
• Size of error.log — a sharp increase in /var/log/php-fpm/error.log or /bitrix/modules/main/tools/log.txt signals a problem before it becomes visible to users. Alert when exceeding 100 MB.

Bitrix built-in tools

According to official documentation (https://dev.1c-bitrix.ru/learning/course/index.php?COURSE_ID=43&LESSON_ID=2180), the monitoring module (if available) is configured under Settings → Monitoring. It can check site availability via HTTP, track agents, and send email notifications. Limitations: only works when PHP is alive, does not check external dependencies, and does not integrate with messengers without customization.

More useful is the Event Log (b_event_log). Via the CEventLog::Add() API you can log custom events, and through admin filters you can configure notifications for specific severity levels.

Why external monitoring is more reliable than built-in?

Bitrix's built-in monitoring checks the site from inside — if PHP or DB goes down, it won't trigger. An external service polls the site from the outside and sees problems that are not visible on the server. For example, during a DDoS attack (https://en.wikipedia.org/wiki/Denial-of-service_attack) or router block, built-in monitoring may show 200 while real users see a timeout.

For small projects, we integrate UptimeRobot Bitrix monitoring with 5-minute checks + Healthchecks.io for cron. For medium and large — Prometheus with blackbox_exporter for HTTP probes and node_exporter for server metrics. Prometheus scales 10x faster than Zabbix on hundreds of hosts.

How to implement a healthcheck endpoint?

Create a file /healthcheck.php in the site root that checks key subsystems:

• DB connection via $DB->Query("SELECT 1")
• Memcached/Redis availability via CBitrixCache
• Write access to the temporary directory (checks disk is not full)
• License key presence (check CModule::IncludeModule('main'))

If all checks pass — return HTTP 200 with body OK. Any failure — HTTP 503 with error description. External monitoring calls this endpoint once a minute and reacts to non-200 status. Execution time should not exceed 200 ms, otherwise monitoring may consider the endpoint unreachable.

<?php
require($_SERVER['DOCUMENT_ROOT'].'/bitrix/modules/main/include/prolog_before.php');
$status = 200;
$errors = [];
if (!$DB->Query("SELECT 1")) { $errors[] = 'DB'; $status = 503; }
if (!is_writable($_SERVER['DOCUMENT_ROOT'].'/upload/')) { $errors[] = 'Disk'; $status = 503; }
http_response_code($status);
echo $status == 200 ? 'OK' : implode(',', $errors);

How to integrate Telegram notifications?

For Bitrix24 there is a built-in integration with webhooks. For sites on 1C-Bitrix, the easiest way is to send alerts via Telegram Bot API directly from the error handler. In init.php, register a custom handler via set_exception_handler() that sends a POST request to api.telegram.org/bot{TOKEN}/sendMessage on critical errors. Do not send every error — use throttling: no more than one message per 5 minutes for each error type. Otherwise, during a mass failure, Telegram will block the bot for spam.

Typical mistakes when setting up monitoring

• 50% of setups check only the main page — other pages may be unavailable, as in the cart case.
• 40% of projects have no cron configured — agents do not execute, site caches slowly.
• Monitoring from inside — it won't work when PHP fails.
• Alerts too frequent (every minute) — after an hour they start to be ignored. An interval of 3-5 minutes is optimal.
• Site downtime during peak hours can cost tens of thousands of rubles — do not skimp on monitoring.

What's included in the work

1. Audit of current infrastructure and identification of bottlenecks with log analysis.
2. Development of a healthcheck endpoint with an individual set of checks (up to 20 metrics).
3. Configuration of external monitoring (UptimeRobot, Prometheus, or equivalent) with a polling frequency of 1-5 minutes.
4. Integration of alerts into Telegram, email, Slack with throttling.
5. Operational documentation and training for your team (2 hours).
6. Support for one month after launch with threshold adjustments.

With 10+ years of Bitrix experience and certified specialists, we guarantee a full SLA. The cost is calculated individually after analysis of the technical specifications. Budget savings can reach tens of thousands of rubles per month through automation. Get a consultation for your project — we will select the optimal solution. Contact us for a monitoring audit and receive a report with recommendations.

What Professional 1C-Bitrix Installation Includes

We start by checking innodb_buffer_pool_size. The default MySQL value (128 MB) is a death sentence for an online store with a catalog of 10,000+ items. We set 70–80% of available RAM on a dedicated server, 50% on VPS. This single setting speeds up the site by 2–3 times compared to the default. We'll assess your project in one day — get a consultation. Contact us to order turnkey installation with performance guarantee.

How to Choose Hosting and Edition for 1C-Bitrix Installation?

BitrixVM is a virtual machine with a pre-installed stack: nginx + Apache, PHP-FPM, MySQL/MariaDB, Sphinx, Push server. For VPS — the best start. Everything is already configured for Bitrix, including OPcache, log rotation, and firewall. Management via web panel on port 8890. Bitrix documentation recommends starting with BitrixVM for predictable performance.

VPS/VDS is the sweet spot. Minimum configuration for a medium online store: 2 vCPU, 4 GB RAM, SSD. Optimal: 4 vCPU, 8 GB RAM. OS: Ubuntu 22.04 or Debian 12. If not BitrixVM, we configure the stack manually for the task. Virtual hosting — only for business cards and landing pages. Requirements: PHP 8.0+, MySQL 5.7+ / MariaDB 10.0+, 512 MB RAM, .htaccess. 1C-Bitrix hosting partners guarantee compatibility. Dedicated server — for highload. Typical architecture: web server separate, database separate, Redis/Memcached separate. For Enterprise edition — web cluster with load balancer. Cloud (Yandex Cloud, VK Cloud, Selectel) — when load spikes: sales, seasonal peaks. Autoscaling via Managed Kubernetes or simple VM vertical scaling.

Choosing the edition is equally important. A common mistake: choosing "Small Business" for a store that grows to B2B with wholesale prices and three warehouses in six months. Upgrading to "Business" — pay the difference, data is not lost, but it's better to plan ahead. Our specialists select the edition for current tasks and with room for growth. For example, the "Business" license (about 35,000 RUB) pays off through multi-warehouse and 1C exchange, while the wrong choice can lead to a loss of up to 30,000 RUB monthly on excess resources.

What Server Settings Are Critical for 1C-Bitrix?

Web Server and PHP

nginx as reverse proxy + Apache (mod_php) or nginx + PHP-FPM directly. The second option saves memory — Apache is not needed. But some Bitrix modules use .htaccess, so for compatibility we sometimes keep Apache. nginx configuration: fastcgi_read_timeout 300 — for long operations (1C import), client_max_body_size 1024m — large file uploads. Block access to .settings.php, .settings_extra.php, bitrix/.settings.php — they contain database passwords. Rewrite rules from urlrewrite.php — Bitrix generates them, but with nginx + PHP-FPM they need to be duplicated. PHP 8.0–8.2 with extensions: mbstring, curl, gd, xml, json, opcache, redis/memcached. Key php.ini settings: opcache.memory_consumption=256, opcache.max_accelerated_files=20000, max_execution_time=300, memory_limit=512M, upload_max_filesize=100M, post_max_size=128M.

Database and Caching

MySQL/MariaDB. Key my.cnf parameters: innodb_buffer_pool_size — 70–80% RAM, innodb_log_file_size=256M, tmp_table_size=256M, max_heap_table_size=256M, thread_pool_size — number of CPU cores. Encoding utf8mb4 mandatory, otherwise emoji and special characters break. Redis is preferable to Memcached for Bitrix — supports persistent connections and is more reliable. In production, Redis handles concurrent writes three times faster than Memcached under typical load. Configure in .settings_extra.php:

'cache' => ['value' => ['type' => ['class_name' => '\\Bitrix\\Main\\Data\\CacheEngineRedis']]]
'session' => ['value' => ['mode' => 'default', 'handlers' => ['general' => ['type' => 'redis']]]]

sudo apt install redis-server
sudo systemctl enable redis

SSL, Email, and Cron

SSL — Let's Encrypt via certbot in 90% of cases. Redirect HTTP → HTTPS (301), HSTS, TLS 1.2/1.3, OCSP Stapling. In Bitrix, switch to HTTPS in the main module settings. Email: abandon mail() — connect SMTP (Yandex.Mail for domain, Mail.ru for Business). Be sure to configure SPF, DKIM, DMARC. Without SPF, emails go to spam. Test deliverability via mail-tester.com — score 9+/10. Cron: Bitrix agents switch to system cron — * * * * * /usr/bin/php /var/www/bitrix/modules/main/tools/cron_events.php. Schedule 1C exchange (15–60 min), search reindex, backups (mysqldump + rsync, rotation 7+4), temporary file cleanup.

Security and Administration

File system: owner www-data, directories 755, files 644, upload 775. nginx blocks access to configuration files. Enable Bitrix Proactive Protection — WAF, activity control (block after 5 failed attempts), kernel integrity check. For admin panel: two-factor authentication via Google Authenticator or OTP, restrict access by IP via nginx for paranoid.

How Long Does 1C-Bitrix Installation and Configuration Take?

Post-Installation Checklist

1. Performance Monitor (/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
2. System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
3. Security Scanner — check for typical vulnerabilities.
4. PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
5. Test 1C exchange — if integration is planned, verify CommerceML exchange before launch.

Additionally, check software versions, caching settings, cron operation, SSL certificate, SPF/DKIM/DMARC, access rights, delete default users and pages. For projects with 54-FZ, ensure fiscalization is configured via OFD provider.

Deliverables

• Fully configured server for 1C-Bitrix with MySQL, PHP, nginx optimization.
• Installed and activated license of the required edition.
• SSL certificate, email settings, cron and backups.
• Documentation: all configuration parameters, access credentials, cron tasks.
• Content manager training: how to log into admin panel, add products, upload images.
• Post-installation support for 30 days — consultations on settings.

Why Trust Professionals with Installation?

Incorrect installation means lost time and money. We've seen projects where a store on "Start" couldn't handle 50 visitors because innodb_buffer_pool_size wasn't configured. After migrating to VPS with correct configuration, the site "flew". Incorrect configuration can cost 30,000 RUB monthly due to excessive resource consumption. You get a ready-made architecture that scales. Order turnkey 1C-Bitrix installation — get a reliable platform for business growth. Contact us for a free consultation: we'll calculate the cost and time for your project. Over 7 years of experience, 120+ Bitrix projects implemented, including highload stores with million-item catalogs. Get in touch — we'll help configure Bitrix for your project.