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
description="The starting time boundary for the search period. String in RFC3339 format.",
171
+
description="The ending time boundary for the search period. String in RFC3339 format.",
172
172
type="string",
173
173
required=True,
174
174
),
@@ -188,7 +188,7 @@ def __init__(
188
188
required=False,
189
189
),
190
190
"workload": ToolParameter(
191
-
description="The kubernetes workload name for filtering configuration changes. Deployment name or Pod name for example.",
191
+
description="Kubernetes resource name to filter configuration changes (e.g., Pod, Deployment, Job, etc.). Must be the full name. For Pods, include the exact generated suffix.",
Copy file name to clipboardExpand all lines: holmes/plugins/toolsets/robusta/robusta_instructions.jinja2
+2Lines changed: 2 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -3,6 +3,8 @@
3
3
* If a change seems important to the investigation, Use fetch_finding_by_id with the configuration change ID to get full details of the change.
4
4
* You must ALWAYS call fetch_configuration_changes_metadata when investigating an alert
5
5
* Never respond without calling fetch_configuration_changes_metadata
6
+
* When investigating a resource (pod, deployment, or job), if no relevant information is available from the live cluster at the time of investigation, call the fetch_resource_issues_metadata function to retrieve its historical alert data.
7
+
* You can use fetch_resource_issues_metadata to get issues context for a specific kubernetes resource. Start with a 4 hours window and try to expand to 24 hours windows if nothing comes up.
6
8
* When investigating an alert, look at historical configuration changes that happen 4 hours before the alert started
7
9
* If you found a change that caused the alert, you MUST write: 'The issue was introduced by ...' with a short description of the change, and the date of it.
), f"Line {i+1} should be: {expected_line.strip()!r}, but got: {lines[i].strip()!r}. This tests make sure the import order in {file_name} file is correct, if you see this, go to {file_name} file and move your imports code to lower lines."
0 commit comments