holmesgpt 0.13.2__py3-none-any.whl → 0.18.4__py3-none-any.whl

holmes/main.py

@@ -1,9 +1,7 @@
 # ruff: noqa: E402
 import os
-import sys
 
 from holmes.utils.cert_utils import add_custom_certificate
-from holmes.utils.colors import USER_COLOR
 
 ADDITIONAL_CERTIFICATE: str = os.environ.get("CERTIFICATE", "")
 if add_custom_certificate(ADDITIONAL_CERTIFICATE):
@@ -11,8 +9,8 @@ if add_custom_certificate(ADDITIONAL_CERTIFICATE):
 
 # DO NOT ADD ANY IMPORTS OR CODE ABOVE THIS LINE
 # IMPORTING ABOVE MIGHT INITIALIZE AN HTTPS CLIENT THAT DOESN'T TRUST THE CUSTOM CERTIFICATE
-
-
+import sys
+from holmes.utils.colors import USER_COLOR
 import json
 import logging
 import socket
@@ -31,7 +29,7 @@ from holmes.config import (
     SourceFactory,
     SupportedTicketSources,
 )
-from holmes.core.prompt import build_initial_ask_messages
+from holmes.core.prompt import build_initial_ask_messages, generate_user_prompt
 from holmes.core.resource_instruction import ResourceInstructionDocument
 from holmes.core.tools import pretty_print_toolset_status
 from holmes.core.tracing import SpanType, TracingFactory
@@ -76,6 +74,9 @@ opt_api_key: Optional[str] = typer.Option(
     help="API key to use for the LLM (if not given, uses environment variables OPENAI_API_KEY or AZURE_API_KEY)",
 )
 opt_model: Optional[str] = typer.Option(None, help="Model to use for the LLM")
+opt_fast_model: Optional[str] = typer.Option(
+    None, help="Optional fast model for summarization tasks"
+)
 opt_config_file: Optional[Path] = typer.Option(
     DEFAULT_CONFIG_LOCATION,  # type: ignore
     "--config",
@@ -136,13 +137,6 @@ opt_json_output_file: Optional[str] = typer.Option(
     envvar="HOLMES_JSON_OUTPUT_FILE",
 )
 
-opt_post_processing_prompt: Optional[str] = typer.Option(
-    None,
-    "--post-processing-prompt",
-    help="Adds a prompt for post processing. (Preferable for chatty ai models)",
-    envvar="HOLMES_POST_PROCESSING_PROMPT",
-)
-
 opt_documents: Optional[str] = typer.Option(
     None,
     "--documents",
@@ -177,6 +171,7 @@ def ask(
     # common options
     api_key: Optional[str] = opt_api_key,
     model: Optional[str] = opt_model,
+    fast_model: Optional[str] = opt_fast_model,
     config_file: Optional[Path] = opt_config_file,
     custom_toolsets: Optional[List[Path]] = opt_custom_toolsets,
     max_steps: Optional[int] = opt_max_steps,
@@ -199,7 +194,6 @@ def ask(
     ),
     json_output_file: Optional[str] = opt_json_output_file,
     echo_request: bool = opt_echo_request,
-    post_processing_prompt: Optional[str] = opt_post_processing_prompt,
     interactive: bool = typer.Option(
         True,
         "--interactive/--no-interactive",
@@ -244,6 +238,7 @@ def ask(
         config_file,
         api_key=api_key,
         model=model,
+        fast_model=fast_model,
         max_steps=max_steps,
         custom_toolsets_from_cli=custom_toolsets,
         slack_token=slack_token,
@@ -258,6 +253,7 @@ def ask(
         dal=None,  # type: ignore
         refresh_toolsets=refresh_toolsets,  # flag to refresh the toolset status
         tracer=tracer,
+        model_name=model,
     )
 
     if prompt_file and prompt:
@@ -295,11 +291,11 @@ def ask(
             console,
             prompt,
             include_file,
-            post_processing_prompt,
             show_tool_output,
             tracer,
             config.get_runbook_catalog(),
             system_prompt_additions,
+            json_output_file=json_output_file,
         )
         return
 
@@ -316,7 +312,7 @@ def ask(
         f'holmes ask "{prompt}"', span_type=SpanType.TASK
     ) as trace_span:
         trace_span.log(input=prompt, metadata={"type": "user_question"})
-        response = ai.call(messages, post_processing_prompt, trace_span=trace_span)
+        response = ai.call(messages, trace_span=trace_span)
         trace_span.log(
             output=response.result,
         )
@@ -342,6 +338,7 @@ def ask(
         issue,
         show_tool_output,
         False,  # type: ignore
+        log_costs,
     )
 
     if trace_url:
@@ -387,7 +384,6 @@ def alertmanager(
     system_prompt: Optional[str] = typer.Option(
         "builtin://generic_investigation.jinja2", help=system_prompt_help
     ),
-    post_processing_prompt: Optional[str] = opt_post_processing_prompt,
 ):
     """
     Investigate a Prometheus/Alertmanager alert
@@ -410,7 +406,7 @@ def alertmanager(
         custom_runbooks=custom_runbooks,
     )
 
-    ai = config.create_console_issue_investigator()  # type: ignore
+    ai = config.create_console_issue_investigator(model_name=model)  # type: ignore
 
     source = config.create_alertmanager_source()
 
@@ -443,8 +439,6 @@ def alertmanager(
             issue=issue,
             prompt=system_prompt,  # type: ignore
             console=console,
-            instructions=None,
-            post_processing_prompt=post_processing_prompt,
         )
         results.append({"issue": issue.model_dump(), "result": result.model_dump()})
         handle_result(result, console, destination, config, issue, False, True)  # type: ignore
@@ -521,7 +515,6 @@ def jira(
     system_prompt: Optional[str] = typer.Option(
         "builtin://generic_investigation.jinja2", help=system_prompt_help
     ),
-    post_processing_prompt: Optional[str] = opt_post_processing_prompt,
 ):
     """
     Investigate a Jira ticket
@@ -539,7 +532,7 @@ def jira(
         custom_toolsets_from_cli=custom_toolsets,
         custom_runbooks=custom_runbooks,
     )
-    ai = config.create_console_issue_investigator()  # type: ignore
+    ai = config.create_console_issue_investigator(model_name=model)  # type: ignore
     source = config.create_jira_source()
     try:
         issues = source.fetch_issues()
@@ -560,8 +553,6 @@ def jira(
             issue=issue,
             prompt=system_prompt,  # type: ignore
             console=console,
-            instructions=None,
-            post_processing_prompt=post_processing_prompt,
         )
 
         console.print(Rule())
@@ -614,7 +605,7 @@ def ticket(
     system_prompt: Optional[str] = typer.Option(
         "builtin://generic_ticket.jinja2", help=system_prompt_help
     ),
-    post_processing_prompt: Optional[str] = opt_post_processing_prompt,
+    model: Optional[str] = opt_model,
 ):
     """
     Fetch and print a Jira ticket from the specified source.
@@ -655,7 +646,7 @@ def ticket(
         },
     )
 
-    ai = ticket_source.config.create_console_issue_investigator()
+    ai = ticket_source.config.create_console_issue_investigator(model_name=model)
     console.print(
         f"[bold yellow]Analyzing ticket: {issue_to_investigate.name}...[/bold yellow]"
     )
@@ -664,7 +655,8 @@ def ticket(
         + f" for issue '{issue_to_investigate.name}' with description:'{issue_to_investigate.description}'"
     )
 
-    result = ai.prompt_call(system_prompt, prompt, post_processing_prompt)
+    ticket_user_prompt = generate_user_prompt(prompt, context={})
+    result = ai.prompt_call(system_prompt, ticket_user_prompt)
 
     console.print(Rule())
     console.print(
@@ -685,14 +677,14 @@ def github(
     ),
     github_owner: Optional[str] = typer.Option(
         None,
-        help="The GitHub repository Owner, eg: if the repository url is https://github.com/robusta-dev/holmesgpt, the owner is robusta-dev",
+        help="The GitHub repository Owner, eg: if the repository url is https://github.com/HolmesGPT/holmesgpt, the owner is HolmesGPT",
     ),
     github_pat: str = typer.Option(
         None,
     ),
     github_repository: Optional[str] = typer.Option(
         None,
-        help="The GitHub repository name, eg: if the repository url is https://github.com/robusta-dev/holmesgpt, the repository name is holmesgpt",
+        help="The GitHub repository name, eg: if the repository url is https://github.com/HolmesGPT/holmesgpt, the repository name is holmesgpt",
     ),
     update: Optional[bool] = typer.Option(False, help="Update GitHub with AI results"),
     github_query: Optional[str] = typer.Option(
@@ -711,7 +703,6 @@ def github(
     system_prompt: Optional[str] = typer.Option(
         "builtin://generic_investigation.jinja2", help=system_prompt_help
     ),
-    post_processing_prompt: Optional[str] = opt_post_processing_prompt,
 ):
     """
     Investigate a GitHub issue
@@ -730,7 +721,7 @@ def github(
         custom_toolsets_from_cli=custom_toolsets,
         custom_runbooks=custom_runbooks,
     )
-    ai = config.create_console_issue_investigator()
+    ai = config.create_console_issue_investigator(model_name=model)
     source = config.create_github_source()
     try:
         issues = source.fetch_issues()
@@ -750,8 +741,6 @@ def github(
             issue=issue,
             prompt=system_prompt,  # type: ignore
             console=console,
-            instructions=None,
-            post_processing_prompt=post_processing_prompt,
         )
 
         console.print(Rule())
@@ -797,7 +786,6 @@ def pagerduty(
     system_prompt: Optional[str] = typer.Option(
         "builtin://generic_investigation.jinja2", help=system_prompt_help
     ),
-    post_processing_prompt: Optional[str] = opt_post_processing_prompt,
 ):
     """
     Investigate a PagerDuty incident
@@ -814,7 +802,7 @@ def pagerduty(
         custom_toolsets_from_cli=custom_toolsets,
         custom_runbooks=custom_runbooks,
     )
-    ai = config.create_console_issue_investigator()
+    ai = config.create_console_issue_investigator(model_name=model)
     source = config.create_pagerduty_source()
     try:
         issues = source.fetch_issues()
@@ -836,8 +824,6 @@ def pagerduty(
             issue=issue,
             prompt=system_prompt,  # type: ignore
             console=console,
-            instructions=None,
-            post_processing_prompt=post_processing_prompt,
         )
 
         console.print(Rule())
@@ -882,7 +868,6 @@ def opsgenie(
     system_prompt: Optional[str] = typer.Option(
         "builtin://generic_investigation.jinja2", help=system_prompt_help
     ),
-    post_processing_prompt: Optional[str] = opt_post_processing_prompt,
     documents: Optional[str] = opt_documents,
 ):
     """
@@ -900,7 +885,7 @@ def opsgenie(
         custom_toolsets_from_cli=custom_toolsets,
         custom_runbooks=custom_runbooks,
     )
-    ai = config.create_console_issue_investigator()
+    ai = config.create_console_issue_investigator(model_name=model)
     source = config.create_opsgenie_source()
     try:
         issues = source.fetch_issues()
@@ -919,8 +904,6 @@ def opsgenie(
             issue=issue,
             prompt=system_prompt,  # type: ignore
             console=console,
-            instructions=None,
-            post_processing_prompt=post_processing_prompt,
         )
 
         console.print(Rule())

holmes/plugins/interfaces.py

@@ -1,4 +1,5 @@
-from typing import List, Iterable
+from typing import Iterable, List
+
 from holmes.core.issue import Issue
 from holmes.core.tool_calling_llm import LLMResult
 

holmes/plugins/prompts/__init__.py

@@ -1,8 +1,9 @@
 import os
 import os.path
+from datetime import datetime, timezone
 from typing import Optional
+
 from jinja2 import Environment, FileSystemLoader
-from datetime import datetime, timezone
 
 THIS_DIR = os.path.abspath(os.path.dirname(__file__))
 

holmes/plugins/prompts/_fetch_logs.jinja2

@@ -1,9 +1,10 @@
 {%- set loki_ts = toolsets | selectattr("name", "equalto", "grafana/loki") | first -%}
-{%- set coralogix_ts = toolsets | selectattr("name", "equalto", "coralogix/logs") | first -%}
+{%- set coralogix_ts = toolsets | selectattr("name", "equalto", "coralogix") | first -%}
 {%- set k8s_base_ts = toolsets | selectattr("name", "equalto", "kubernetes/logs") | selectattr("fetch_pod_logs", "defined") | first -%}
 {%- set k8s_yaml_ts = toolsets | selectattr("name", "equalto", "kubernetes/logs") | rejectattr("fetch_pod_logs", "defined") | first -%}
 {%- set opensearch_ts = toolsets | selectattr("name", "equalto", "opensearch/logs") | first -%}
 {%- set datadog_ts = toolsets | selectattr("name", "equalto", "datadog/logs") | first -%}
+{%- set openshift_ts = toolsets | selectattr("name", "equalto", "openshift/logs") | first -%}
 {%- set bash_ts = toolsets | selectattr("name", "equalto", "bash") | first -%}
 
 ## Logs
@@ -11,6 +12,7 @@
 * IMPORTANT: ALWAYS inform the user about what logs you fetched. For example: "Here are pod logs for ..."
 * IMPORTANT: If logs commands have limits mention them. For example: "Showing last 100 lines of logs:"
 * IMPORTANT: If a filter was used, mention the filter. For example: "Logs filtered for 'error':"
+* IMPORTANT: If a date range was used (even if just the default one and you didn't specify the parameter, mention the date range. For example: "Logs from last 1 hour..."
 
 {% if loki_ts and loki_ts.status == "enabled" -%}
 * For any logs, including for investigating kubernetes problems, use Loki
@@ -23,9 +25,9 @@
 ** If there are too many logs, or not enough, narrow or widen the timestamps
 * If you are not provided with time information. Ignore start_timestamp and end_timestamp.
 {%- elif coralogix_ts and coralogix_ts.status == "enabled" -%}
-### coralogix/logs
-#### Coralogix Logs Toolset
-Tools to search and fetch logs from Coralogix.
+### coralogix
+#### Coralogix Toolset
+Tools to search and fetch logs, traces, metrics, and other telemetry data from Coralogix.
 {% include '_default_log_prompt.jinja2' %}
 {%- elif k8s_base_ts and k8s_base_ts.status == "enabled" -%}
 {% include '_default_log_prompt.jinja2' %}
@@ -34,8 +36,29 @@ Tools to search and fetch logs from Coralogix.
 ### datadog/logs
 #### Datadog Logs Toolset
 Tools to search and fetch logs from Datadog.
-{% include '_default_log_prompt.jinja2' %}
+* Use the tool `fetch_pod_logs` to access an application's logs.
+* Do fetch application logs yourself and DO not ask users to do so
+* If you have an alert/monitor try to figure out the time it fired
+** Then, use `start_time=-300` (5 minutes before `end_time`) and `end_time=<time monitor started firing>`  when calling `fetch_pod_logs`.
+** If there are too many logs, or not enough, narrow or widen the timestamps
+* If the user did not explicitly ask about a given timeframe, ignore the `start_time` and `end_time` so it will use the default.
+* IMPORTANT: ALWAYS inform the user about the actual time period fetched (e.g., "Looking at logs from the last <X> days")
+* IMPORTANT: If a limit was applied, ALWAYS tell the user how many logs were shown vs total (e.g., "Showing latest <Y> of <Z> logs")
+* IMPORTANT: If any filters were applied, ALWAYS mention them explicitly
+{%- elif openshift_ts and openshift_ts.status == "enabled" -%}
+### openshift/logs
+#### OpenShift Logs Toolset
+Tools to search and fetch logs from OpenShift.
+* Use the tool `oc_logs` to access an application's logs.
+* Do fetch application logs yourself and DO not ask users to do so
+* If you have an alert/monitor try to figure out the time it fired
+** If there are too many logs, or not enough, narrow or widen the timestamps
+* IMPORTANT: ALWAYS inform the user about the actual time period fetched (e.g., "Looking at logs from the last <X> days")
+* IMPORTANT: If a limit was applied, ALWAYS tell the user how many logs were shown vs total (e.g., "Showing latest <Y> of <Z> logs")
+* IMPORTANT: If any filters were applied, ALWAYS mention them explicitly
 {%- elif k8s_yaml_ts and k8s_yaml_ts.status == "enabled" -%}
+### Logs from newrelic
+* you can fetch logs from newrelic if this is toolset is enabled
 ### kubernetes/logs
 #### Kubernetes Logs Toolset
 Tools to search and fetch logs from Kubernetes.
@@ -54,6 +77,8 @@ DO NOT use `--tail` or `| tail` when calling `kubectl logs` because you may miss
 ** 'kubernetes/logs'
 ** 'grafana/loki'
 ** 'opensearch/logs'
-** 'coralogix/logs'
+** 'coralogix'
 ** 'datadog/logs'
+** 'openshift/logs'
+** 'newrelic'
 {%- endif -%}

holmes/plugins/prompts/_general_instructions.jinja2

@@ -12,8 +12,7 @@
 * do not stop investigating until you are at the final root cause you are able to find.
 * use the "five whys" methodology to find the root cause.
 * for example, if you found a problem in microservice A that is due to an error in microservice B, look at microservice B too and find the error in that.
-* if you cannot find the resource/application that the user referred to, assume they made a typo or included/excluded characters like - and.
-* in this case, try to find substrings or search for the correct spellings
+* if you cannot find the resource/application that the user referred to, assume they made a typo or included/excluded characters like - and in this case, try to find substrings or search for the correct spellings
 * always provide detailed information like exact resource names, versions, labels, etc
 * even if you found the root cause, keep investigating to find other possible root causes and to gather data for the answer like exact names
 * if a runbook url is present you MUST fetch the runbook before beginning your investigation

holmes/plugins/prompts/_runbook_instructions.jinja2

@@ -1,21 +1,33 @@
-{% if runbooks and runbooks.catalog|length > 0 %}
+{%- set sections = [
+  {'title': 'Runbook Catalog', 'content': runbook_catalog},
+  {'title': 'Subject/Issue Runbooks', 'content': custom_instructions},
+  {'title': 'Global Instructions', 'content': global_instructions}
+] -%}
+{%- set available = sections | selectattr('content') | list -%}
+{%- if available -%}
 # Runbook Selection
 
-You (HolmesGPT) have access to a set of runbooks that provide step-by-step troubleshooting instructions for various known issues.
-If one of the following runbooks relates to the user's issue, you MUST fetch it with the fetch_runbook tool.
+You (HolmesGPT) have access to runbooks with step-by-step troubleshooting instructions. 
+If one of the following runbooks relates to the user's issue or match one of the alerts or symptoms listed in the runbook entry, you MUST fetch it with the fetch_runbook tool.
+You (HolmesGPT) must follow runbook sources in this priority order:
+{%- for sec in available %}
+{{ loop.index }}) {{ sec.title }} (priority #{{ loop.index }})
+{%- endfor %}
 
-## Available Runbooks for fetch_runbook tool
-{% for runbook in runbooks.catalog %}
-### description: {{ runbook.description }}
-link: {{ runbook.link }}
-{% endfor %}
+{%- for sec in available %}
+## {{ sec.title }} (priority #{{ loop.index }})
 
-If there is a runbook that MIGHT match the user's issue, you MUST:
+{%- set content = (sec.content|string) -%}
+{{ content.replace('\n', '\n   ') }}
+
+{%- endfor %}
+
+
+If a runbook might match the user's issue, you MUST:
 1. Fetch the runbook with the `fetch_runbook` tool.
 2. Decide based on the runbook's contents if it is relevant or not.
-3. If it seems relevant, inform the user that you accesses a runbook and will use it to troubleshoot the issue.
+3. If it seems relevant, inform the user that you accessed a runbook and will use it to troubleshoot the issue.
 4. To the maximum extent possible, follow the runbook instructions step-by-step.
 5. Provide a detailed report of the steps you performed, including any findings or errors encountered.
-6. If a runbook step requires tools or integrations you don't have access to tell the user that you cannot perform that step due to missing tools.
-
+6. If a runbook step requires tools or integrations you don't have access to, tell the user that you cannot perform that step due to missing tools.
 {%- endif -%}

holmes/plugins/prompts/base_user_prompt.jinja2

@@ -0,0 +1,7 @@
+{{ user_prompt }}
+
+{% if runbooks_enabled %}
+{% include '_runbook_instructions.jinja2' %}
+{% endif %}
+
+{% include '_current_date_time.jinja2' %}

holmes/plugins/prompts/conversation_history_compaction.jinja2

@@ -0,0 +1,89 @@
+This conversation history is too long and no longer fits your context window. 
+Your task is to create a detailed summary of the conversation so far. This will help continuing the investigation after summarisation is done.
+This summary should be thorough in capturing technical details, code patterns, and architectural decisions that would be essential for continuing development work without losing context.
+
+Before providing your final summary, wrap your analysis in <analysis> tags to organize your thoughts and ensure you've covered all necessary points. In your analysis process:
+
+1. Chronologically analyze each message and section of the conversation. For each section thoroughly identify:
+   - The user's explicit requests and intents
+   - Your approach to addressing the user's requests
+   - Key decisions, technical concepts and code patterns
+   - Specific details like kubernetes resource names, namespaces, relevant logs extracts (verbatim), etc
+   - What tools were called and the outcome or analysis of the tool output
+2. Double-check for technical accuracy and completeness, addressing each required element thoroughly.
+
+Your summary should include the following sections:
+
+1. Primary Request and Intent: Capture all of the user's explicit requests and intents in detail
+2. Key Technical Concepts: List all important technical concepts, technologies, and frameworks discussed.
+3. Resources: Enumerate specific kubernetes or cloud resources and logs extract examined. Pay special attention to the most recent messages and include logs or tool outputs where applicable and include a summary of why this resource is important.
+4. Tool calls: List all tool calls that were executed and whether they failed/succeeded. Make sure to mention the full arguments used. Only summarize the arguments if they are over 200 characters long
+5. Problem Solving: Document problems solved and any ongoing troubleshooting efforts.
+6. Pending Tasks: Outline any pending tasks that you have explicitly been asked to work on.
+7. Current Work: Describe in detail precisely what was being worked on immediately before this summary request, paying special attention to the most recent messages from both user and assistant. Include resource names and their namespace and log extracts where applicable.
+8. Optional Next Step: List the next step that you will take that is related to the most recent work you were doing. IMPORTANT: ensure that this step is DIRECTLY in line with the user's explicit requests, and the task you were working on immediately before this summary request. If your last task was concluded, then only list next steps if they are explicitly in line with the users request. Do not start on tangential requests without confirming with the user first.
+                       If there is a next step, include direct quotes from the most recent conversation showing exactly what task you were working on and where you left off. This should be verbatim to ensure there's no drift in task interpretation.
+
+Here's an example of how your output should be structured:
+
+<example>
+<analysis>
+[Your thought process, ensuring all points are covered thoroughly and accurately]
+</analysis>
+
+<summary>
+1. Primary Request and Intent:
+   [Detailed description]
+
+2. Key Technical Concepts:
+   - [Concept 1]
+   - [Concept 2]
+   - [...]
+
+3. Infrastructure Resources:
+   - [Deployment name 1]
+      - [Summary of why this deployment is important]
+      - [Summary of the issues identified with this deployment, if any]
+      - [List of related pods/services or otyher resources and why they are relevant]
+   - [Pod name 2]
+      - [Summary of why this pod is important]
+      - [Summary of the issues identified with this pod, if any]
+      - [List of related pods/services or otyher resources and why they are relevant]
+   - [...]
+
+4. Tool Calls:
+   - [✅ function_name {args}]
+   - [✅ function_name {args}]
+   - [❌ function_name {args} - NO DATA]
+   - [❌ function_name {args} - Error message]
+   - [...]
+
+5. Problem Solving:
+   [Description of solved problems and ongoing troubleshooting]
+
+6. Pending Tasks:
+   - [Task 1]
+   - [Task 2]
+   - [...]
+
+7. Current Work:
+   [Precise description of current work]
+
+8. Optional Next Step:
+   [Optional Next step to take]
+
+</summary>
+</example>
+
+Please provide your summary based on the conversation so far, following this structure and ensuring precision and thoroughness in your response.
+
+There may be additional summarization instructions provided in the included context. If so, remember to follow these instructions when creating the above summary. Examples of instructions include:
+<example>
+## Compact Instructions
+When summarizing the conversation focus on typescript code changes and also remember the mistakes you made and how you fixed them.
+</example>
+
+<example>
+# Summary instructions
+When you are using compact - please focus on test output and code changes. Include relevant logs verbatim.
+</example>

holmes/plugins/prompts/generic_ask.jinja2

@@ -8,14 +8,10 @@ If you have a good and concrete suggestion for how the user can fix something, t
 If you are unsure about the answer to the user's request or how to satisfy their request, you should gather more information. This can be done by asking the user for more information.
 Bias towards not asking the user for help if you can find the answer yourself.
 
-{% include '_current_date_time.jinja2' %}
-
 Use conversation history to maintain continuity when appropriate, ensuring efficiency in your responses.
 
 {% include '_general_instructions.jinja2' %}
 
-{% include '_runbook_instructions.jinja2' %}
-
 # Style guide
 
 * Reply with terse output.

holmes/plugins/prompts/generic_ask_conversation.jinja2

@@ -4,7 +4,6 @@ Ask for multiple tool calls at the same time as it saves time for the user.
 Do not say 'based on the tool output' or explicitly refer to tools at all.
 If you output an answer and then realize you need to call more tools or there are possible next steps, you may do so by calling tools at that point in time.
 If you have a good and concrete suggestion for how the user can fix something, tell them even if not asked explicitly
-{% include '_current_date_time.jinja2' %}
 
 Use conversation history to maintain continuity when appropriate, ensuring efficiency in your responses.
 

holmes/plugins/prompts/generic_ask_for_issue_conversation.jinja2

@@ -3,7 +3,6 @@ Whenever possible you MUST first use tools to investigate then answer the questi
 Ask for multiple tool calls at the same time as it saves time for the user.
 Do not say 'based on the tool output' or explicitly refer to tools at all.
 If you output an answer and then realize you need to call more tools or there are possible next steps, you may do so by calling tools at that point in time.
-{% include '_current_date_time.jinja2' %}
 
 ### Context Awareness:
 Be aware that this conversation is follow-up questions to a prior investigation conducted for the {{issue}}.

holmes/plugins/prompts/generic_investigation.jinja2

@@ -4,7 +4,6 @@ Ask for multiple tool calls at the same time as it saves time for the user.
 Do not say 'based on the tool output'
 
 Provide an terse analysis of the following {{ issue.source_type }} alert/issue and why it is firing.
-* {% include '_current_date_time.jinja2' %}
 * If the tool requires string format timestamps, query from 'start_timestamp' until 'end_timestamp'
 * If the tool requires timestamps in milliseconds, query from 'start_timestamp' until 'end_timestamp'
 * If you need timestamp in string format, query from 'start_timestamp_millis' until 'end_timestamp_millis'