You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
str, "The DCI job ID for which to perform root cause analysis (RCA)."
30
28
],
31
-
) ->PromptMessage:
29
+
) ->str:
32
30
"""
33
31
Prompt for instructions on how to do a Root Cause Analysis (RCA) of a failing DCI job. Always use this prompt when analysing a failing DCI job.
34
32
35
33
Returns:
36
34
A prompt message with instructions on how to perform RCA of a failing DCI job.
37
35
"""
38
-
content=f"""Conduct a root cause analysis (RCA) on the following DCI job: {dci_job_id}. Store all the downloaded files at /tmp/dci/<job id>, so as not to download them twice. Create a report with your findings at /tmp/dci/rca-<job id>.md. Be sure to include details about the timeline of events and the DCI job information in the report, such as the components, the topic, and the pipeline name. If there is a CILAB-<num> comment, replace it with https://issues.redhat.com/browse/CILAB-<num>. Include a hyperlink each time you refer to the DCI job ID.
36
+
returnf"""Conduct a root cause analysis (RCA) on the following DCI job: {dci_job_id}. Store all the downloaded files at /tmp/dci/<job id>, so as not to download them twice. Create a report with your findings at /tmp/dci/rca-<job id>.md. Be sure to include details about the timeline of events and the DCI job information in the report, such as the components, the topic, and the pipeline name. If there is a CILAB-<num> comment, replace it with https://issues.redhat.com/browse/CILAB-<num>. Include a hyperlink in the form https://distributed-ci.io/jobs/<job id> each time you refer to the DCI job ID.
39
37
40
38
First step is to review ansible.log (overview of the CI job execution). Then the logjuicer.txt (for regular files) and logjuicer_omg.txt (for must_gather) files that compare the logs from a previous successful run.
41
39
@@ -49,65 +47,54 @@ async def rca(
49
47
50
48
Check it the associated JIRA ticket is consistent with your findings.
str, "The subject of the analysis (team name or id, remoteci name or id)."
60
55
],
61
-
) ->PromptMessage:
56
+
) ->str:
62
57
"""
63
58
Prompt for instructions on how to analyze DCI jobs for a week.
64
59
65
60
Returns:
66
61
A prompt message with instructions on how to analyze DCI jobs for a week.
67
62
"""
68
-
content=f"""Analyze the DCI jobs for the last week for {subject}. Provide a summary of the number of jobs, the number of failures, and the failure rate. Identify the top 3 reasons for failures and provide recommendations for improvement. If there are any CILAB-<num> comments, replace them with https://issues.redhat.com/browse/CILAB-<num>. Include hyperlinks each time you refer to a DCI job ID.
63
+
returnf"""Analyze the DCI jobs for the last week for {subject}. Provide a summary of the number of jobs, the number of failures, and the failure rate. Identify the top 3 reasons for failures and provide recommendations for improvement. If there are any CILAB-<num> comments, replace them with https://issues.redhat.com/browse/CILAB-<num>. Include hyperlinks in the form https://distributed-ci.io/jobs/<job id> each time you refer to a DCI job ID.
69
64
70
65
Create a report with your findings in the /tmp/dci directory (create the directory if it doesn't exist). Be sure to include a summary, statistics and anomaly detection if applicable. Use markdown formatting for the report.
str, "The subject of the analysis (team name or id, remoteci name or id)."
81
72
],
82
-
) ->PromptMessage:
73
+
) ->str:
83
74
"""
84
75
Prompt for instructions on how to analyze DCI jobs for 2 weeks.
85
76
86
77
Returns:
87
78
A prompt message with instructions on how to analyze DCI jobs for a week.
88
79
"""
89
-
content=f"""Analyze the DCI jobs for the last 2 weeks for {subject}. Provide a summary of the number of jobs, the number of failures, and the failure rate. Identify the top 3 reasons for failures and provide recommendations for improvement. If there are any CILAB-<num> comments, replace them with https://issues.redhat.com/browse/CILAB-<num>. Include hyperlinks each time you refer to a DCI job ID.
80
+
returnf"""Analyze the DCI jobs for the last 2 weeks for {subject}. Provide a summary of the number of jobs, the number of failures, and the failure rate. Identify the top 3 reasons for failures and provide recommendations for improvement. If there are any CILAB-<num> comments, replace them with https://issues.redhat.com/browse/CILAB-<num>. Include hyperlinks in the form https://distributed-ci.io/jobs/<job id> each time you refer to a DCI job ID.
90
81
91
82
Create a report with your findings in the /tmp/dci directory (create the directory if it doesn't exist). Be sure to include a summary, statistics and anomaly detection if applicable. Use markdown formatting for the report.
str, "The subject of the analysis (remoteci name or id)."
102
89
],
103
-
) ->PromptMessage:
90
+
) ->str:
104
91
"""
105
92
Prompt for instructions on how to analyze DCI jobs for a quarter (3 months).
106
93
107
94
Returns:
108
95
A prompt message with instructions on how to analyze DCI jobs for a quarter.
109
96
"""
110
-
content=f"""Analyze the DCI jobs for the last quarter (3 months) for {subject}. Due to the large volume of data, you must use a multi-step approach with caching to avoid exhausting the context window.
97
+
returnf"""Analyze the DCI jobs for the last quarter (3 months) for {subject}. Due to the large volume of data, you must use a multi-step approach with caching to avoid exhausting the context window.
111
98
112
99
## Step 1: Data Collection and Caching
113
100
@@ -256,9 +243,6 @@ async def quarterly(
256
243
- Prioritize statistics that reveal patterns and trends
0 commit comments