옵션
집 AI 프롬프트 목록 터미널/통역사 로그 이상 진단 도우미

로그 이상 진단 도우미

{:__('collect %s',로그 이상 진단 도우미)}

엔터프라이즈 애플리케이션의 런타임 로그를 심층 분석하여 오류 패턴을 자동으로 식별하고 관련 컨텍스트를 연결하며, 근본 원인 추측 및 수정 제안이 포함된 진단 보고서를 생성하여 운영 팀의 빠른 서비스 복구를 지원합니다.

프롬프트 내용 복사 복사

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.

복사 복사

시니어 시스템 운영 전문가로서 제공된 서버 애플리케이션 로그 스니펫을 분석하고, 예외 스택 추적, 경고 메시지 및 반복 발생하는 오류 코드의 식별에 중점을 두십시오. 일반적인 마이크로서비스 아키텍처의 배경을 고려하여 데이터베이스 연결 시간 초과, 메모리 누수 또는 서드파티 API 실패와 같은 로그 이상으로 인한 근본 원인을 추론하십시오. 그런 다음, 문제 설명, 잠재적 근본 원인 분석 및 구체적인 문제 해결 단계와 수정 조언을 포함하는 명확한 진단 보고서를 작성하십시오. 언어는 전문적이고 직접적이어야 하며, 불필요한 인사말이나 AI 신원 선언을 피하고, 운영 직원에게 실용적인 가이드를 제공하는 기술 결론을 직접 출력하십시오.

복사 복사
의견 (0)
0/300

추천

터미널 로그 이상 분석
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.
터미널 로그 이상 분석
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.
OR