Professional Monitoring Setup for 1C-Bitrix

Recently, a client approached us with a catalog of 150,000 items. Pages loaded in 8 seconds, but load testing showed nothing—the problem only appeared under real traffic. It turned out that slow SQL queries accumulated over a week, and the system degraded gradually. Monitoring caught the trend in time, and we optimized the queries in one day. Without continuous metric collection, you learn about the problem from the user, not from the system.

According to Bitrix Benchmark, 60% of projects have suboptimal SQL queries that go unnoticed until a crash.

Why Continuous Monitoring Is More Effective Than One-Time Measurements

A one-time load test is a photo; continuous monitoring is high-definition video. A one-time measurement captures the state at the moment of the test but does not show trends. Continuous monitoring allows you to see: a 200% increase in SQL query time over a month, a 2 GB weekly increase in Redis memory consumption, or PHP-FPM approaching saturation. Only with history can you distinguish a random spike from systemic degradation. For example, on one project, we noticed a 15% increase in 5xx errors over a week—it turned out that a module update caused a memory leak in Redis. Monitoring caught it 2 days before the first complaints.

Problems We Solve

• Hidden degradation: response time increases by 300% over two weeks due to non-optimal queries. Without monitoring—only customer complaints.
• PHP-FPM overflow: active processes > 85% max_children—the site starts to slow down, and you don't know if it's time to expand the pool.
• Redis memory leak: memory consumption grows by 2 GB per week after a module update. Monitoring detects the leak before Redis starts evicting keys.
• MySQL slow queries: 10+ slow queries per minute—indexes and query structure require review.

How We Set Up Monitoring: Stack and Configs

We deploy Prometheus with exporters on target servers. For a typical project, we use:

• node_exporter — system metrics (CPU, RAM, disk, network)
• mysqld_exporter — MySQL/MariaDB metrics (slow queries, InnoDB, connection pool)
• php-fpm_exporter — PHP-FPM metrics from /fpm-status
• redis_exporter — Redis metrics (memory, hit rate, connected clients)

To get PHP-FPM status, add to the pool config:

pm.status_path = /fpm-status

In nginx:

location /fpm-status {
    allow 127.0.0.1;
    deny all;
    fastcgi_pass unix:/run/php/php8.1-fpm.sock;
    include fastcgi_params;
    fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
}

The /fpm-status endpoint shows active/idle/waiting processes. If active processes is close to max_children — PHP is saturated, need to increase the pool or optimize code.

Then we collect data in Grafana: build dashboards with key metrics for Bitrix. Example alert: if php_fpm_active_processes exceeds 85% of max for more than 5 minutes — Telegram notification. If MySQL slow queries > 10/minute — Email. If site response time > 3 seconds — Telegram + call.

What Metrics Are Critical for Bitrix?

On the Grafana dashboard, we display:

• php_fpm_active_processes / php_fpm_max_active_processes — PHP-FPM load
• mysql_global_status_slow_queries — number of slow queries
• redis_memory_used_bytes — Redis memory usage
• node_load1 / node_load5 — system load
• Percentage of 5xx errors — indicator of application-level issues

Learn more about Prometheus and Grafana.

Monitoring Tools Comparison

Key Metrics and Alert Thresholds

Process of Work

1. Analysis: study current architecture, load (number of requests, peaks), bottlenecks (what you already know).
2. Design: choose exporters, develop alert schema, define thresholds.
3. Implementation: deploy Prometheus, Grafana, configure metric collection with exporters.
4. Test: verify data correctness, simulate failures, set up dashboards.
5. Deploy: move to production, document, conduct team training (1-hour webinar on dashboards and alert responses).

What's Included in the Work

• Deployment of Prometheus + Grafana stack on your servers or in the cloud.
• Configuration of exporters (node, mysql, php-fpm, redis, optionally nginx).
• Development of dashboards with key metrics for Bitrix.
• Setup of alerts with notifications to Telegram and Email.
• Documentation on using dashboards and responding to alerts.
• Team training (up to 2 hours online).
• Post-release support for 2 weeks (threshold adjustments, exporter updates).

Timeline — from 3 to 5 business days for full implementation. Typical cost is $1,000–$2,000, with savings of $10,000+ in prevented downtime. Our team has 8+ years of experience and 50+ successful projects, guaranteeing reliable monitoring.

Order a free assessment of your project — we will analyze the current architecture and show the benefits of a monitoring system. Contact us to set up monitoring that identifies problems before users notice them.

80% of Bitrix sites slow down due to one table

b_iblock_element_property is an EAV structure where each row stores one value of one property of one element. A catalog of 50,000 products with 30 properties yields 1.5 million rows. The smart filter performs a JOIN of this table with b_iblock_element on five properties, and MySQL performs a full table scan for 3–5 seconds. Our experience shows that without intervention in this table, site acceleration is impossible. We take on projects where load time has dropped to 8–10 seconds and bring TTFB back to <200 ms within 1–2 weeks. Site speed optimization begins with an audit of slow queries and ends with a comprehensive turnkey infrastructure overhaul.

Contact us for an audit — we will identify bottlenecks within 2 hours and propose a concrete plan.

How to achieve TTFB below 200 ms?

Server optimization is the first step. Nginx configuration goes beyond simple gzip. Specifically:

• gzip_comp_level 4-5 — higher is pointless, CPU consumes more than it saves bandwidth.
• brotli on with brotli_static on for precompressed files.
• HTTP/2 with http2_max_concurrent_streams 128.
• fastcgi_cache for PHP responses — caching at Nginx level, bypassing PHP-FPM entirely.
• worker_processes auto, worker_connections according to the number of simultaneous connections.

PHP-FPM tuning: choose between pm = dynamic and pm = static. Static mode works best for dedicated servers with predictable load because it avoids forking overhead. Dynamic saves RAM under low traffic. Calculate pm.max_children as (available RAM - RAM for MySQL/Redis) / average process consumption. For OPcache set memory_consumption=256, max_accelerated_files=20000, and validate_timestamps=0 in production (restart PHP-FPM on deploy).

MySQL/MariaDB: the main bottleneck is almost always the database. Enable slow_query_log with a threshold of 0.5 sec and analyze every query via EXPLAIN. Set innodb_buffer_pool_size to 70–80% of available RAM on a dedicated server. Create composite indexes for faceted search: (IBLOCK_ID, IBLOCK_PROPERTY_ID, VALUE) on b_iblock_element_property. Run OPTIMIZE TABLE b_iblock_element_property after mass operations.

How to configure three-level caching?

Managed component cache. Set TTL individually for each component. Catalog — 3600 sec, news feed — 300 sec, banners — 86400. The same TTL everywhere guarantees either outdated data or useless cache.

Composite cache. The bitrix:composite technology lets Nginx serve ready HTML from a file; PHP is not executed. Dynamic zones (cart, authorization) are loaded via AJAX request through CBitrixComponent::setFrameMode(true). TTFB drops below 50 ms. However, not all components are compatible; $APPLICATION->ShowPanel() and direct output via echo break the composite. We check every page through the panel 'Performance → Composite Site'. According to Bitrix official documentation on composite cache, this is the most effective caching method for high‑load projects.

Comparison: composite cache is 10–20 times faster than managed cache in time to first byte.

Memcached / Redis. Transfer cache from the file system: sessions go to Redis (session.save_handler = redis) — 10–50 times faster than files, plus cluster support. Component cache goes to Memcached via .settings.php: 'cache' => ['type' => 'memcache']. Also enable ORM query cache so identical GetList() calls don't hit MySQL on every request.

What is the fastest way to optimize Bitrix database?

Default MySQL settings are insufficient. Indexes — composite for faceted search, covering for frequent queries. MySQL responds from the index without accessing the data. Partial indexes (MariaDB) for filtering by ACTIVE = 'Y'. Audit unused indexes — each slows down INSERT/UPDATE.

Partitioning. For tables with millions of rows: b_stat_session, b_search_content_stem, and highload-blocks with history. Partition by date — a query for 'orders in a month' does not scan three years of data. Partitioning also solves the problem of concurrent queries during exchange with 1С via CommerceML.

Real case: a catalog of 200,000 products, 50 properties. Filtering by 10 properties took 12 seconds. After creating composite indexes on (IBLOCK_ID, IBLOCK_PROPERTY_ID, VALUE) and partitioning b_iblock_element_property by IBLOCK_ID, execution time dropped to 0.3 seconds. MySQL load decreased by 40 times.

Cleanup. Over a year or two, any database accumulates: outdated search index, expired records in b_cache_tag, history in b_iblock_element_prop_s*, logs in b_event_log taking gigabytes. We set up regular cleanup via agents.

Frontend and CDN

Images account for 60–80% of page weight. Convert to WebP via CFile::ResizeImageGet() with BX_RESIZE_IMAGE_PROPORTIONAL + conversion. Use srcset + sizes — never load a 3000px image into a 400px block. Add loading="lazy" for everything below the fold. AVIF offers another 20–30% savings vs WebP.

CSS/JS optimization: use the built-in Bitrix module to merge and minify via 'Settings → CSS/JS Optimization'. Apply PurgeCSS / UnCSS — in a typical Bitrix project, 60–70% of CSS is unused. Use defer / async for non‑critical JS and inline critical CSS in <head> for instant FCP.

Fonts: add <link rel="preload" as="font" crossorigin> for the main font. Set font-display: swap — text visible immediately. Subset via pyftsubset — keep only Cyrillic + Latin, file size reduces by 3–5 times.

CDN: Cloudflare, BunnyCDN, AWS CloudFront, or Russian providers (Selectel CDN, VK Cloud CDN). Serve static assets (CSS, JS, images, fonts) via CDN with Cache-Control: public, max-age=31536000, immutable for files with a hash. Use on‑the‑fly image optimization (imgproxy, Cloudflare Polish) without load on origin.

Why is load testing necessary?

Not synthetic benchmarks, but real scenarios: k6 / wrk to simulate routes — catalog → filtering → product card → cart → checkout. Measure RPS, response time (p50, p95, p99), error rate. Use Xdebug (callgrind) or Blackfire for PHP profiling to find bottlenecks. The test result gives an objective picture of where it actually slows down, not where it 'seems'. After optimization, run again to record improvements.

Results

What is included in the work?

1. Current performance audit — analysis of slow queries, PHP profiling, check of caching, CDN, server settings.
2. Server configuration — Nginx, PHP-FPM, MySQL, Redis/Memcached, OPcache.
3. Caching optimization — managed cache, composite site, TTL configuration, tagged caching.
4. Database work — index creation, partitioning, cleanup, EAV table reorganization.
5. Frontend — images (WebP/AVIF), CSS/JS (minification, deferred), fonts (preload, subsetting).
6. CDN — connection, caching rule setup.
7. Load testing — real user scenarios, metric report.
8. Documentation — description of all changes, recommendations for further maintenance.
9. Guarantee — support for 1 month after delivery, ensuring all optimizations are stable.

Monitoring

Without monitoring, everything degrades in six months. A new module, uncleared logs, a template change — and speed returns to original. Use web-vitals API for Real User Monitoring from actual visitors. Set up synthetic monitoring with Pingdom or UptimeRobot for regular checks from different locations. Configure alerts — TTFB > 500 ms or LCP > 3 sec triggers notification.

Timelines and cost

Cost is calculated individually after the audit. Get a consultation for your project — we will evaluate the current state and propose an acceleration plan with specific timelines and budget. We are a team with 12+ years of experience in Bitrix, having completed over 300 site speed optimization projects. Contact us to start the performance audit today.