Example Prompts
Ready-to-use prompts for common investigation, exploration, and creation scenarios
Copy-paste these prompts to get started. Replace the @mentions (e.g. @workload, @namespace) with the actual entity names from your environment - the Agent autocompletes them as you type.
Incident Investigation
Error Investigation
Investigate errors in
@workload. Check error rates, identify the most common error patterns in logs and traces, and correlate with recent events.
Root Cause Analysis
Perform a root cause analysis on
@workload: Who is affected, What is failing, Where in the call chain, When it started, and Why.
Alert Triage
Triage the alert on
@monitor. Check the current state, review recent firings, and investigate the underlying cause.
Crashloop Diagnosis
Why is
@workloadcrashlooping? Check for OOMKill events, crash events, and recent changes.
Performance
Slow Endpoints
Find the slowest endpoints in
@workload. Show P50, P95, and P99 latency broken down by path.
Slow Database Queries
Find the slowest database queries called by
@workload. Show query patterns, durations, and which endpoints trigger them.
Resource Usage
Investigate CPU and memory usage for
@workload. Show trends, compare against requests/limits, and flag anomalies.
Data Exploration
Top Errors
Show me the top 10 error-producing workloads in
@namespaceover the last 24 hours.
Log Patterns
What are the most common log patterns for
@workload? Group by pattern and show hit counts.
Change Correlation
What changed recently in
@workload? Check for image updates, config changes, scaling events, and restarts.
Dependencies
Show me the dependencies of
@workload- which services does it call, and which services call it?
Building
Dashboard
Build a dashboard for
@namespacecovering: error rates by workload, latency P95, pod restarts, and resource utilization.
Monitor
Create a monitor that fires when error rate on
@workloadexceeds 5% for more than 5 minutes, with severity S2.
Log Parsing
Parse the unstructured logs from
@workload. Extract structured fields from the raw log content.
Drop Rules
Create a drop rule to filter out health check logs from
@workload.
Infrastructure
Node Pressure
Are any nodes experiencing CPU, memory, or disk pressure? Show affected nodes and the workloads running on them.
Over-Provisioned Resources
Find workloads in
@namespacethat are over-provisioned - using significantly less CPU or memory than their requests.
Pod Health
Show me all unhealthy pods in
@namespace- crashlooping, pending, or evicted.
Smart Filtering
Use the Agent to suggest relevant filters for your investigations - just describe what you're looking at.
Suggest Filters
I'm investigating errors in
@namespace. What filters should I use to narrow down the root cause?
Find Log Patterns
What are the most important log patterns I should filter for when investigating
@workload?
Identify Key Attributes
What attributes should I filter on to find performance issues in
@workload?
Scope by Error Type
Help me isolate connection-timeout errors in
@namespace.
Tips for Effective Prompts
Be specific about scope - include the workload, namespace, or cluster you care about
State what you want to see - "Show me error rates broken down by endpoint" beats "look at errors"
Mention the signal - if you specifically want traces vs. logs, say so
Ask follow-ups - the Agent keeps context, so narrow down iteratively
Use @mentions - reference entities with
@namefor precise resolution; the Agent autocompletes from your live dataTurn repeated context into a Skill - if you find yourself writing the same framing ("always use P95", "this is a payments service", "start with the monitor") across prompts, save it as a Skill and the Agent will apply it automatically
Let the UI do the work - if you're already filtered to the right scope, just ask the question
Last updated