Error Monitoring

What this solution does

The Errors Monitoring module collects portal error data and records it in the administrative journal. Each entry preserves the full error text, the exact code location, the list of affected pages, and timestamps of occurrences.

The module tracks PHP errors extracted from the exception file log of the 1C-Bitrix system, as well as JavaScript errors occurring on portal pages. These include script exceptions, unhandled promise rejections, console.error messages, failures during script and stylesheet loading, and violations of browser permission policies.

Identical errors are merged into a single entry. The system counts the number of repetitions and records the pages where they occurred, along with the timestamp of each occurrence.

If chat support is available on the portal, the entry can be additionally sent as a short notification. The message is delivered to a private chat with the Errors Monitoring bot or to an incoming webhook for the im.message.add method. The notification includes the error type, description, location, list of pages, repetition count, and a link to the journal card.

If chat support is not available on the portal, the module continues to maintain the error journal. A warning indicating that the chat bot is not supported is displayed on the settings page, and bot-based notification sending becomes unavailable. In this case, an incoming webhook can be specified separately: the message will be sent to the webhook dialog.

In the BestRank menu under Errors Monitoring, settings for data collection and, if chat support is available, notification distribution settings are accessible.

The BestRank Errors Monitoring module provides a queue for errors that have not yet been sent. The error log includes statuses: Not Sent, Sent, and Do Not Send. Each error has a card displaying the full text and a list of triggers. The log can be exported to Excel.

Excessive messages are filtered using masks: such errors are recorded in the log and assigned the Do Not Send status, but are not delivered to the chat. For the bot and each webhook, settings include the pause between messages, the message limit per minute, and a time window during which the same error is not resent.

Checking the PHP log, sending notifications, and cleaning old records are performed by a single agent. The agent does not delete the PHP log file.

The module is useful for portal developers: the log displays the error type, description, code location, and full text. Repeated occurrences of the same error are grouped into a single record.

For testers, an error caught during verification remains in the log along with the page information and trigger time. The number of repetitions indicates whether the error is reproducible.

Portal administrators access the log, queue, and settings via the BestRank menu. There, they can configure the retention period, masks for excessive messages, and export the log to Excel.

The module is designed for maintenance and technical support. If a support chat is active, a brief summary with a link to the incident card is automatically sent to it. Full details are available in the event log.

General iT can handle the implementation of “Error Monitoring”, from installation to configuration and compatibility checks.