/plugadvpl:log-diagnose

Diagnose Protheus logs by parsing timestamped events from console.log and error.log files, matching them against alert rules, and enriching outputs with TDN correction tips. It extracts root-cause signals from noisy multi-line logs to pinpoint compilation failures and thread errors.

Finding the root cause of Protheus compilation failures involves applying recency-first alert rules to parsed log events. This approach prioritizes the most recent error signals in compila.log files, helping you quickly identify underlying RPO or authentication problems.

Filtering Protheus log diagnostics by severity, category, rule id, and time window is fully supported. You can set a since filter relative to the log's last timestamp to narrow down specific database or ORA issues during targeted troubleshooting.

Protheus log diagnostics supports extracting events from multiple log header formats across console, error, profile, and compila.log files. It preserves stacks and multi-line SQL dumps during two-stage parsing to ensure accurate REST API and network issue detection.

REST API startup errors may miss TDN tips if the log header format is unrecognized during event parsing. Successful diagnosis requires matching parsed events against the 19 alert rules to properly attach applicable official TDN URLs from the 93-tip catalog.

Automated Protheus log triage relies on recognizing specific log header formats and 19 predefined alert rules. Logs with non-standard headers or novel error patterns outside the current TDN tip catalog may not yield enriched correction suggestions or actionable findings.