Автоматический анализ журналов ошибок терминала

Дом

Список AI-промптов

Терминал/Интерпретатор

Диагностика логов терминала

${:__('collect %s',Диагностика логов терминала)}$

Терминал/Интерпретатор

Глубокий анализ ошибок терминала Linux/Unix с указанием причин и решений.

Содержание промпта

Копировать

Analyze the provided terminal error logs or failed command outputs to identify specific error codes, missing dependencies, or permission issues, and provide executable fix commands or configuration adjustments based on the current operating system environment, ensuring the solution is directly actionable and compliant with security standards.

Копировать

Проанализируйте предоставленные журналы ошибок терминала или вывод неудачных команд, чтобы определить конкретные коды ошибок, отсутствующие зависимости или проблемы с правами доступа, и предоставьте исполняемые команды исправления или настройки конфигурации на основе текущей среды операционной системы, убедившись, что решение является непосредственно исполняемым и соответствует стандартам безопасности.

Копировать

Поделиться Нажмите, чтобы скопировать ссылку

Комментарии (0)

0/300

Представлять на рассмотрение

Рекомендация

Детектор аномалий в логах

Act as a senior system operations expert and analyze the provided server terminal log snippets. Focus on identifying error codes, warning messages, and exception stack traces, inferring the root cause of service interruption or performance degradation based on context. Finally, output a concise report in natural language containing the problem description, potential root cause speculation, and specific remediation advice or troubleshooting steps, ensuring the content is directly usable without further explanation.

Детектор аномалий в логах

Analyze the provided server terminal log snippets to identify abnormal error patterns such as connection timeouts or memory leaks, and extract key error stack traces. Based on the system architecture context, infer the most likely root cause, and finally generate a concise fault report containing problem description, impact scope, and preliminary troubleshooting suggestions to assist the operations team in rapid response.

Анализ аномалий в журнале терминала

Please analyze the provided Linux terminal error log snippet, identifying key error codes, process IDs, and timestamps within it, and infer possible causes based on context. You need to translate technical stack trace information into natural language descriptions understandable by non-technical personnel, pointing out the most likely root cause and providing preliminary troubleshooting suggestions. Ensure the output is concise and focused on solving practical problems, avoiding any templated openings or closings.

Ассистент диагностики логов

Act as a senior system operations expert and analyze the provided server application log snippets, focusing on identifying exception stack traces, warning messages, and recurring error codes. Contextualize these findings within a typical microservices architecture to infer the root cause of the anomalies, such as database connection timeouts, memory leaks, or third-party API failures. Subsequently, produce a clear diagnostic report that includes the problem description, potential root cause analysis, and specific troubleshooting steps with remediation advice. Ensure the language is professional and direct, avoiding any redundant openings or AI identity statements, and deliver technical conclusions that offer practical guidance for operations staff.

Анализ аномалий в журнале терминала

Analyze the following Linux terminal error output to identify the specific anomaly type such as permission denied, missing dependency, or configuration error, infer the root cause based on context, and finally provide a single executable command to fix the issue, ensuring the command is idempotent and does not disrupt the existing system state.

Детектор аномалий в логах

Please analyze the provided server terminal log snippets, focusing on identifying abnormal error codes, warning messages, and stack trace data. You need to extract key timestamps, process IDs, and error types from the chaotic log stream to determine if there are recurring failure patterns or signs of resource exhaustion. Based on the extracted information, summarize potential system risks in concise natural language and provide preliminary troubleshooting suggestions. Ensure the output directly serves the decision-making needs of operations staff, avoiding any templated openings or complex structured lists, while maintaining narrative coherence and professionalism.