Custom User Action Logging Setup for 1C-Bitrix

Custom User Action Logging Setup for 1C-Bitrix

On projects with 200+ content managers and administrators, the question "who changed the price on this product yesterday at 17:30?" remains unanswered without proper logging. The built-in Bitrix event log records far from everything, and what it records is stored without convenient filtering. For example, you won't know who unpublished a product or changed its name. Without detailed auditing, it's impossible to prove a specific employee's action or restore the change history. We solve this: we configure comprehensive logging with custom handlers, rotation, and archiving. Having completed over 50 Bitrix projects, we guarantee transparency for every action. Our engineers develop handlers for infoblocks, orders, and CRM, add diff comparison, and customizable filters. Contact us — we'll select the optimal logging configuration for your project.

Why the built-in event log is insufficient

Bitrix writes events out of the box into the b_event_log table. It is enabled in the main module settings: Settings → Product Settings → Module Settings → Main Module → "Event Log" tab.

Standard logged events:

• Login/logout (USER_LOGIN, USER_LOGOUT)
• Login failures (USER_LOGIN_FAILED)
• Module rights changes (MODULE_RIGHTS_CHANGED)
• File operations via file manager (FILE_DELETE, FILE_EDIT)
• User operations (USER_ADD, USER_EDIT, USER_DELETE)

These events cover only system actions. Content changes — products, articles, prices — stay out of sight. Without custom handlers, you remain blind to most modifications.

The following remain outside standard configuration:

• Infoblock element changes (products, articles, news) — key gap
• Order changes (status updates, editing)
• Price and stock changes
• CRM module actions (contacts, deals, leads)

On commercial projects, these are exactly the changes that most often require auditing. Our custom solution is three times more effective than the standard one because it adds diff comparison and flexible filters. Records are stored with exact time, IP address, and user session.

How to extend logging via event handlers

For logging infoblock changes, subscribe to the iblock module events:

• OnBeforeIBlockElementUpdate — get data BEFORE change
• OnAfterIBlockElementUpdate — record the fact of change

Both events are needed to record a diff — which fields changed and from which values to which. The handler is registered in /local/php_interface/init.php via AddEventHandler() or in the module's events.php file. Below are key fields to log:

For recording, use CEventLog::Add():

CEventLog::Add([
    'SEVERITY' => 'INFO',
    'AUDIT_TYPE_ID' => 'IBLOCK_ELEMENT_UPDATE',
    'MODULE_ID' => 'iblock',
    'ITEM_ID' => $elementId,
    'DESCRIPTION' => json_encode([
        'user_id' => $GLOBALS['USER']->GetID(),
        'changes' => $diff,
    ], JSON_UNESCAPED_UNICODE),
]);

Records go into the same b_event_log table and are visible in the standard event log interface.

AddEventHandler("iblock", "OnBeforeIBlockElementUpdate", "MyLogIBlockBeforeUpdate");
AddEventHandler("iblock", "OnAfterIBlockElementUpdate", "MyLogIBlockAfterUpdate");
// ... rest of code

How to configure order action logging

The sale module has its own events: OnSaleOrderSaved, OnSaleStatusOrder, OnSalePayOrder. For full order audit, we subscribe to OnSaleOrderSaved — it fires on every order save. Inside the handler, we access the \Bitrix\Sale\Order object to get the current state. For comparison with the previous state, we load the order from the database before save (in OnBeforeSaleOrderSaved). This captures all changes: status, composition, delivery address, prices.

Rotation and storage

The b_event_log table grows quickly. On an active store (1000+ orders/day, 50+ editors) — up to 100,000 records per month. Rotation settings:

• Retention time — set in event log settings (unlimited by default)
• Manual cleanup — CEventLog::CleanUp($days) via agent
• Recommendation — keep 90 days in Bitrix, archive older records to a separate table or file

Optimal storage configuration:

What is included in logging setup

We provide a complete package:

• Development of custom handlers for infoblocks, orders, and CRM
• Configuration of rotation and archiving
• Testing on test data with creation of reference records
• Documentation on journal access and filtering
• Delivery of handler source code
• Training for administrators on working with the journal
• 30-day support after delivery

Quick verification of configuration

After attaching handlers: modify a test product in admin panel, then open Settings → Tools → Event Log, filter by type IBLOCK_ELEMENT_UPDATE. The record should contain the element ID and a diff of changes in the description.

Basic logging setup takes one business day. Get a consultation on logging configuration today. Contact us — we will help set up logging to any requirements. Achieve transparency and control over all actions on your Bitrix project.

For more details on the event log, see the official Bitrix documentation: Event Log

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.