터미널 오류 로그 자동 분석

집

AI 프롬프트 목록

터미널/통역사

터미널 로그 이상 검사

${:__('collect %s',터미널 로그 이상 검사)}$

터미널/통역사

Linux 터미널 오류에 대해 자연어 설명 및 수정 명령을 생성하며, 특정 사용 사례에 초점을 맞춥니다.

프롬프트 내용

복사

When a user encounters a non-zero exit code or standard error output while executing a command in the Linux terminal, the system should automatically capture the error context, identify the specific error type (such as permission denied, file not found, or syntax error), and explain the root cause in natural language, while providing a single line of executable fix command, ensuring the output is concise and requires no additional explanation.

복사

사용자가 Linux 터미널에서 명령을 실행할 때 0이 아닌 종료 코드 또는 표준 오류 출력이 발생하는 경우, 시스템은 오류 컨텍스트를 자동으로 캡처하고 구체적인 오류 유형(예: 권한 거부, 파일 없음 또는 구문 오류)을 식별하며, 자연어로 근본 원인을 설명하고 동시에 복사하여 직접 실행할 수 있는 수정 명령을 한 줄 제공하여, 출력이 간결하고 추가 설명이 필요하지 않도록 보장합니다.

복사

공유 링크를 복사하려면 클릭

의견 (0)

0/300

제출하다

추천

터미널 로그 이상 분석 도우미

When a user encounters an error while executing a command in the terminal, analyze the provided error output text to identify the specific exception type such as permission denied, path not found, or missing dependencies. Based on the current operating system environment, determine the most likely root cause and directly provide one or more copy-pasteable fix commands or configuration adjustment suggestions. Ensure the solution is highly available and secure, avoiding vague descriptions.

로그 이상 감지 어시스턴트

Please analyze the provided server terminal log snippets to identify error codes, warning-level information, and key timestamps along with module names. Extract specific error descriptions, assess their severity, and attempt to infer potential root causes such as out-of-memory errors, connection timeouts, or permission denials. Finally, compile the analysis into a concise fault summary that includes the error type, occurrence time, and suggested initial troubleshooting steps to assist the operations team in rapid response.

로그 이상 감지 어시스턴트

Please analyze the provided server terminal log snippets to identify recurring error codes or warning messages, and infer possible root causes based on the context. You need to extract key timestamps, process IDs, and error stack traces, compare them against known common failure patterns, and finally output a concise anomaly summary that points out the most likely failure point and suggests initial troubleshooting steps, ensuring natural language flow and focus on solving specific operational issues.

터미널 로그 이상 감지

When a user encounters a non-zero exit code, segmentation fault, or program interruption due to missing dependencies while executing commands in a Linux terminal, deeply analyze the last ten command history entries and standard error output streams of the current session. Identify specific anomaly types such as permission denied, path not found, or library version conflicts, and infer the root cause by combining system environment information. Subsequently, provide a single line of directly executable repair command or configuration adjustment suggestion, ensuring the solution is immediately operable without disrupting the existing system state. Finally, summarize the core issue and resolution path in concise natural language.

터미널 로그 이상 감지

When a user encounters a non-zero exit code, segmentation fault, or critical service interruption while executing commands in a Linux terminal, analyze the last 50 lines of terminal output to identify specific exception stack traces, error codes, and associated system state parameters. Based on common failure patterns, infer the root cause and provide a detailed operational guide containing specific fix commands, configuration adjustment suggestions, or temporary workarounds, ensuring the solution is executable and prevents recurrence of similar issues.

터미널 로그 이상 분석 도우미

When a user encounters an error while executing a command in a Linux or Unix terminal, analyze the provided error output to identify specific error codes or exception types. Based on the system environment context, infer the root cause and provide a safe, executable fix command or troubleshooting step, ensuring the solution is concise and directly applicable to the current terminal session.