version: "1.0.2" name: log-analysis description: "Анализ журнала регистрации и технологического журнала 1С. Используй когда нужно разобрать ЖР, ТЖ, исключения, блокировки, SQL/DBMSSQL, deadlock, long call, фоновые задания, HTTP-сервис или связать записи журнала с кодом."

Log Analysis

MCP routing

• Preferred path: use MCP unica tools unica.code.search, unica.meta.info, unica.project.map, unica.code.diagnostics, unica.standards.search, and unica.standards.explain.
• Use unica.runtime.execute only for related syntax/tests/launch verification, not as a substitute for log evidence.
• Do not call internal runtime, analyzer, standards, or package adapters directly. They are hidden behind MCP unica.

Inputs

Accept explicit journal registration exports, technological log files, copied log fragments, or paths provided by the user. Preserve timestamps, process/session ids, users, infobase, event kind, module/procedure, transaction id, SQL text, and correlation ids.

References

• Read ../../references/platform/runtime-diagnostics.md for ЖР/ТЖ timeline, startup, web-client, HTTP, background job, and process/session evidence.
• Read ../../references/platform/db-performance.md when log fragments contain SQL, locks, deadlocks, waits, long queries, or DBMS-specific artifacts.

Workflow

1. Classify the evidence: ЖР event, ТЖ event, platform exception, DBMS/SQL, lock/deadlock, long call, background job, HTTP service, web client request, or auth/session problem.
2. Build a timeline. Keep clock source and timezone explicit when several files are involved.
3. Extract module, procedure, metadata object, HTTP path, query text, user/session, and transaction identifiers.
4. Map log entries back to source with unica.code.search and metadata with unica.meta.info.
5. Use unica.standards.search or unica.standards.explain for diagnostic ids and development-standard recommendations. The exact meaning of a platform message requires a platform-help source; if public MCP unica does not expose one, report the contract gap.
6. Separate root cause from consequences: the first exception/lock/timeout usually matters more than later rollback noise.
7. For DBMS evidence, preserve lock holder/waiter, SQL text, transaction boundary, process id, session id, wait event, table/index name, and elapsed time together.

Output

• Root-cause hypothesis with evidence lines.
• Timeline of key events.
• Affected code and metadata paths.
• Recommended fix or next measurement.
• Missing evidence, if the log fragment cannot support a reliable conclusion.

MCP example

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "unica.code.search",
    "arguments": {
      "cwd": "<workspace>",
      "sourceSet": "<source-set-from-project-map>",
      "query": "ВыполнитьОбменСКонтрагентом",
      "limit": 20
    }
  }
}