Directum RX ops: find errors by log line, articles, sizing calculators, versions, checklists
Score is being calculated.
Supported versions of Linux and Windows Server, Docker, PostgreSQL and compatible DBMS (Postgres Pro, Jatoba, Tantor), Microsoft SQL Server, RabbitMQ, Elasticsearch and Kubernetes tools for Directum RX, as summarized on drxinfra.ru from the vendor documents. The table covers RX 4.12 and RX 25.2 only; for other releases it says so instead of guessing. Optional filters by component and RX version.
| Name | Required | Description | Default |
|---|---|---|---|
| component | No | Part of a component name or version text, e.g. PostgreSQL, Astra, RabbitMQ, Elasticsearch | |
| rx_version | No | RX release, e.g. 4.12 or 25.2 |
Match a log line, stack trace fragment or error message against the drxinfra.ru reference of about 200 errors seen around Directum RX: RX services and Directum Launcher, PostgreSQL, RabbitMQ, Elasticsearch, certificates and TLS, Keycloak and Kerberos, nginx, Docker and Kubernetes. Returns the best matches first, each with the exact error text, what it means, how to check and what to do (Russian), and the page link. Uses the same patterns and ranking as the search box on drxinfra.ru/errors/. Paste the error itself; remove passwords, tokens and personal data first.
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | Log line or error text, as is. The first 16000 characters are checked. | |
| limit | No | How many matches to return, best first |
Full text (Markdown, Russian) of a drxinfra.ru error page or blog article about Directum RX operations. Accepts an id as returned by find_error and search_site (errors/ or blog/), a bare slug, or a drxinfra.ru URL such as https://drxinfra.ru/blog/rabbitmq-queue-growth.html. Links inside are absolute.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | errors/<slug>, blog/<slug>, a slug or a drxinfra.ru URL |
Search drxinfra.ru: blog articles on Directum RX infrastructure (PostgreSQL, RabbitMQ, Elasticsearch, backups, monitoring, logs, Kubernetes, security, updates, AI assistants), the error reference and the tool pages (calculators, config generators, checklists). Ranked exactly like the site search: Russian words match by stem and prefix, titles weigh most. Query in Russian works best (e.g. «очередь растёт», «pg_wal», «сертификат»). Returns titles, links, snippets and ids for get_article.
| Name | Required | Description | Default |
|---|---|---|---|
| kind | No | Only one kind of page: article, error, tool (calculators and generators) or page | any |
| limit | No | How many results to return | |
| query | Yes | Words to search for |
The drxinfra.ru security self-assessment of a Directum RX installation: 22 weighted questions on backups, passwords, network exposure, updates, TLS, accounts, logs and more, from critical to low. Call without answers to get the questions with weights, hints and fixes; ask the user, then call with answers to get the score out of 100, the zone (red, yellow, green) and the gaps to close first, counted exactly as on drxinfra.ru/security-check.html, with a link that opens the same answers there.
| Name | Required | Description | Default |
|---|---|---|---|
| answers | No | Answers by question id: y = yes, p = partly, n = no, u = don't know. Unanswered questions do not count. |
How many CPU servers and how much memory a local LLM assistant for Directum RX needs (the model works with RX through MCP tools), from drxinfra measurements: llama.cpp on CPU, load tests with 1, 2 and 4 concurrent users and an answer quality check. Same model and numbers as drxinfra.ru/ai-sizing.html. Returns servers, memory, typical and p95 answer time, answers per hour, the quality score, and a comparison of all measured models on the chosen server.
| Name | Required | Description | Default |
|---|---|---|---|
| hw | No | Measured server: icelake16 = Intel Xeon Ice Lake, 16 vCPU, 32 ГБ; m1pro = Apple M1 Pro, 8 ядер CPU | icelake16 |
| kv | No | KV cache type of the model server | f16 |
| qph | No | Questions per hour from each of them | |
| model | No | Model: qwen3-4b = Qwen3 4B; qwen3-8b = Qwen3 8B; gigachat31 = GigaChat 3.1 10B-A1.8B; qwen3-30b-a3b = Qwen3 30B-A3B Instruct 2507 | qwen3-8b |
| share | No | Percent of them asking in the peak hour, usually 10-30 | |
| users | No | Employees with the assistant | |
| target | No | Acceptable typical answer time, seconds | |
| toolset | No | RX tools given to the model: all = Все 27; pilot = 16 для пилота | all |
Servers, vCPU, RAM and disks for a Directum RX installation by role (application servers, RabbitMQ, DBMS, document storage, full-text search, Ario, Kubernetes, monitoring, backups) for production, test and pre-production. Runs the very model of the drxinfra.ru/sizing.html calculator, so the numbers are the same as on the page, and returns a link that opens this calculation there. An estimate for budget and requirements, not a load test. Every parameter is optional; omitted ones take the page defaults.
| Name | Required | Description | Default |
|---|---|---|---|
| db | No | pg = PostgreSQL, mssql = Microsoft SQL Server | pg |
| ha | No | High availability: every layer survives the loss of one node | |
| os | No | linux, or windows (Windows Server: RX as services, no containers) | linux |
| dcs | No | Document capture service (scanners, mail, folders) | |
| fts | No | Full-text search (Elasticsearch or OpenSearch) | |
| k8s | No | ns = a namespace in an existing cluster, full = the whole cluster (only with place=k8s) | ns |
| ver | No | Directum RX version | 26.2 |
| ario | No | Directum Ario (recognition and classification) | |
| test | No | Test contour (a fifth of users, a tenth of data) | |
| docKB | No | Average document size, KB | |
| place | No | vm = containers on virtual machines, k8s = Kubernetes (Linux only) | vm |
| store | No | s3 = object storage (MinIO or S3 storage), fs = file storage (volume, NFS, SMB) | s3 |
| users | No | Total number of RX users | |
| years | No | Planning horizon, years | |
| active | No | Users working at the same time; 0 means 30% of the total | |
| backup | No | Backups: volume outside the contour | |
| mobile | No | Users of the mobile app | |
| pgKind | No | pro = Postgres Pro, vanilla = PostgreSQL (only with db=pg) | pro |
| logDays | No | Log retention, days | |
| preprod | No | Pre-production contour (data as in production) | |
| docsYear | No | Documents created per year | |
| arioPages | No | Ario flow, pages per hour (only with ario) | |
| historyGB | No | Archive migrated from the old system, GB: counts for storage, not for load | |
| monitoring | No | Monitoring and centralized logs | |
| testInCluster | No | Test and pre-production in the same cluster (with place=k8s and k8s=full) | |
| preprodLikeProd | No | Pre-production with the same high availability as production |
The drxinfra.ru checklist for upgrading Directum RX with a way back: 44 items in 7 phases, from two weeks before the window through the rehearsal on a test contour, the rollback plan, the window itself, checks before users come back and the first day. Optionally marks done items and returns a link that opens the same marks on drxinfra.ru/upgrade-checklist.html, where they can be printed or saved.
| Name | Required | Description | Default |
|---|---|---|---|
| done | No | Numbers of the items already done (1-44) | |
| phase | No | Only this phase (1-7); 0 = all | |
| window | No | Planned window, for the link, e.g. 15.12 22:00-06:00 (up to 40 characters) | |
| to_version | No | Target RX version, for the link (up to 40 characters) | |
| from_version | No | Current RX version, for the link (up to 40 characters) |
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
component_versionsfind_errorget_articlesearch_sitesecurity_self_checksize_aisize_rxupgrade_checklistSearch and update ARCH-Insight: architecture fact sheets, applications, tickets, tasks, incidents.
Track errors, manage performance alerts, and configure dashboards and monitors
Read-only access to Auralogs production logs: search logs, inspect errors, review AI analyses.
Search logs, investigate errors, check deployments, and monitor uptime for your elmah.io org.
Add one secure layer between your agents and this server.
