자동화 로그 오류 분석 및 근본 원인

집

AI 프롬프트 목록

터미널/통역사

로그 이상 감지 어시스턴트

${:__('collect %s',로그 이상 감지 어시스턴트)}$

터미널/통역사

서버 터미널 로그를 실시간으로 분석하고 주요 오류 패턴을 식별하여 읽기 쉬운 장애 보고서를 생성하여 운영 담당자의 신속한 문제 해결을 지원합니다.

프롬프트 내용

복사

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.

복사

제공된 서버 터미널 로그 스니펫을 분석하고 이상 오류 코드, 경고 메시지 및 스택 추적 데이터 식별에 중점을 두십시오. 혼란스러운 로그 스트림에서 주요 타임스탬프, 프로세스 ID 및 오류 유형을 추출하여 반복되는 장애 패턴이나 자원 고갈 징후가 있는지 판단해야 합니다. 추출된 정보를 바탕으로 잠재적 시스템 위험을 간결한 자연어로 요약하고 초기 문제 해결 제안을 제공하십시오. 운영 담당자의 의사 결정 필요에 직접 기여하도록 출력을 보장하고, 템플릿화된 인사말이나 복잡한 구조화된 목록을 피하면서 서술의 일관성과 전문성을 유지하십시오.

복사

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

의견 (0)

0/300

제출하다

추천

로그 이상 진단 도우미

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.

터미널 로그 이상 분석

Act as a senior system operations expert and analyze the provided terminal command execution output or error log snippet. Your task is to identify key error codes, exception stack traces, and related system status information contained within, and translate these technical details into clear, structured natural language descriptions. Focus on explaining the potential causes of the error, its impact scope, and suggested initial troubleshooting steps, avoiding rigid instructional language. Instead, provide coherent diagnostic advice in a professional consultant's tone, helping non-technical managers understand the severity and urgency of the issue.

터미널 로그 이상 검사

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.

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

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.