APM Setup for 1С-Битрикс: Performance Monitoring

Imagine: during peak hours your Bitrix e-commerce site starts slowing down. Managers can't keep up with orders, the catalog opens in 8 seconds, and 1C exchange freezes. A single query to b_iblock_element takes 4 seconds — and there are thousands like it per minute. Standard Xdebug profiling shows the problem, but only when it's too late. APM works continuously, capturing every slow request, every error, and every throughput drop. We integrate APM into your 1С-Битрикс so you see real performance data 24/7. Unlike one-time measurements, APM provides time series: you know that yesterday p95 response time was 1.2s, and today it's 2.9s — and you can react immediately.

We use two main stacks: Elastic APM (open-source, self-hosted) and New Relic / Datadog (SaaS). For each project we pick the optimal option based on load and budget. The result — dashboards in Kibana or New Relic UI, alerts in Slack/Telegram, full control over performance. Below, technical details.

Process of Setting Up APM

1. Architecture and load analysis. Identify critical points: slow pages, heavy SQL, external calls.
2. Choose APM stack. Elastic APM or New Relic — based on speed, budget, and data control needs.
3. Install and configure APM Server, Elasticsearch, and Kibana (or New Relic agent).
4. Configure the PHP agent on the server. Optimize parameters like transaction_sample_rate.
5. Create dashboards and alerts. Track p95 response time, error rate, Apdex.
6. Test and calibrate. Validate data correctness and fine-tune notifications.

APM Monitoring in Bitrix

The PHP agent intercepts request execution and sends metrics to a central store. Elastic APM flow:

PHP-агент (elastic-apm-php) → APM Server → Elasticsearch → Kibana (APM UI)

Installing the PHP agent:

# Debian/Ubuntu
curl -L -O https://github.com/elastic/apm-agent-php/releases/download/v1.x.x/apm-agent-php_Linux_x86-64.deb
dpkg -i apm-agent-php_Linux_x86-64.deb

In php.ini:

extension=elastic_apm.so
elastic_apm.server_url=http://apm-server:8200
elastic_apm.service_name=bitrix-site
elastic_apm.environment=production
elastic_apm.transaction_sample_rate=0.1

transaction_sample_rate=0.1 — profiles 10% of requests. On high-load sites, 100% incurs noticeable overhead.

The agent automatically captures:

• Incoming HTTP requests — response time, status, URL, method.
• SQL queries — to b_iblock_element, b_sale_order, b_crm_deal and all other tables. Shows time, query body, execution plan.
• External HTTP calls — curl_exec, file_get_contents. Calls to 1C, payment gateways, external APIs.
• Exceptions — \Bitrix\Main\SystemException, unhandled errors.

For custom operations (long import scripts, heavy aggregations), create spans manually:

use Elastic\Apm\ElasticApm;

$transaction = ElasticApm::getCurrentTransaction();
$span = $transaction->beginCurrentContextSpan('import.products', 'custom');
// ... import logic ...
$span->end();

Which APM to Choose: Elastic or New Relic?

Elastic APM is free, self-hosted, full data control. New Relic is cloud-based, easier to start, but pay-per-GB. For small projects (up to 500 requests/min), Elastic APM often suffices; for large ones with 1000+ requests/s, New Relic is more convenient with built-in alerts and integrations. We help you choose and set up either.

Why transaction_sample_rate Matters?

This is the percentage of requests for which detailed traces are collected. 0.1 (10%) is the sweet spot: low overhead, enough data to find bottlenecks. Setting 1.0 profiles every request — overhead becomes noticeable at high loads. We tune sample_rate to your traffic and server resources. For a site with 100,000 visits/day, sample_rate 0.1 yields ~1,000 traces/minute — a statistically significant sample.

Key Metrics and Alerts

After setup, Kibana APM UI provides:

• Response time — average and 95th percentile by URL.
• Throughput — requests per minute.
• Error rate — percentage of errored requests.
• Apdex — satisfaction index: ratio of fast (<T), tolerable (<4T), and slow requests.

Alerts configured in Kibana Alerting: if p95 response time exceeds 3 seconds for more than 5 minutes — notification in Slack or email. For particularly critical pages (cart, checkout), we lower thresholds to 1 second.

Timelines

What's Included?

We provide: full documentation of the APM architecture, maintenance instructions, training for your admin on Kibana/New Relic, notification setup in your corporate messenger. Optionally, integration with your existing monitoring system (Zabbix, Prometheus). Turnkey — from agent installation to live dashboards. Contact us for a consultation — we'll assess your project for free.

What the Data Says

According to Elastic APM PHP agent documentation, the minimum overhead at sample_rate 0.1 is less than 1% — confirmed by our measurements on projects with catalogs up to 500,000 products.

Why Choose Us?

We've been working with 1С-Битрикс and APM for over 5 years. We've set up monitoring for 40+ projects, including catalogs with millions of products and CRMs with thousands of deals per day. Experience with Elastic APM, New Relic, Datadog. We work under contract with a guarantee. Order APM setup for your Bitrix site and gain performance transparency.

APM doesn't replace profiling — it shows what is degrading and when. A profiler explains why. But together they give full control. Get a consultation — we'll help you find the optimal solution.

1C-Bitrix Module Development and Setup

The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.

Why is init.php the worst place for business logic?

Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.

Standard Modules: Typical Problems and Solutions

Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.

e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.

Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.

Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.

Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.

How to Design Infoblocks for Performance?

We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.

Custom Module Development

Each module follows the structure /local/modules/vendor.modulename/:

• install/index.php — setup class, create tables via $DB->RunSQLBatch()
• lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
• admin/ — administrative pages using CAdminList, CAdminForm
• include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
• REST API endpoints via \Bitrix\Rest\RestManager

The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.

Examples of implemented tasks:

• Campaign management — visual condition builder via CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
• Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
• Booking system — real-time calendar, locking via $DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook

Components and Composite Cache

Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.

Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.

What to Check Before Installing a Marketplace Module?

Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.

Migration to D7

When upgrading PHP or switching to a new edition — refactor outdated calls:

• CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
• CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
• CModule::IncludeModule() → Bitrix\Main\Loader::includeModule() Testing on staging, rollback via git on issues.

According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.

Comparison: Init.php vs Module

Module Development Scope and Cost

What is included in module development?

• Technical specification and architectural plan
• Code following PSR-4 and Bitrix code style
• Unit tests (PHPUnit) for business logic
• Integration tests for events and REST API
• Installation, configuration, and API documentation
• Repository and documentation access
• Administrator training for module usage
• 6-month warranty support

Estimated timelines and complexity:

Cost is calculated individually — contact us for a project estimate.

Module Testing

Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.

Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.

Practical Examples

Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.

Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.

Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.

We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.