Prompt Library

why prompt resolve ai is highly capable at navigating telemetry and surfacing issues but to get precise, fast, and contextually relevant answers when you're hunting for a specific datasource, behavior, or anomaly; prompts are your power tool benefits of prompting clarity speaks to resolve ai in a vernacular it’s trained to understand speed shortens the path to answers in chat precision directs the investigation to relevant resources or dimensions use prompts like giving instructions to a skilled coworker clear, scoped, and focused on outcomes resource selection when prompting, the resource is your entry point this might be a specific service, deployment, environment, pod, or application represented in resolve ai's knowledge graph once selected, the resource and its respective environment are displayed above the chat input box example prompts "investigate the health of my checkout application " "pick the frontend application " "check the status of frontend pod jyt2a375 iuy34 " 👉 tip use "@" to explicitly select or get auto suggestions on resource names time resolve ai investigations and chats always operate in a time window time scoping your prompt ensures the platform can collect and analyze the correct telemetry defaults time range if not specified, resolve ai defaults to analyzing the last 1 hour time zone if you don’t specify a time zone, resolve ai assumes the one set in your browser or local system how to override the defaults to override these defaults and narrow in on exactly what you need, include any of the following in your prompt start and end time (absolute) a specific time relative time range, such as "last 2 hours" or "since yesterday" example prompts "what happened around 3 24 pm et on april 10?" "check application logs from 9 00 am to 11 00 am today " "show me error logs from the last 15 minutes " "investigate system behavior since may 5 until now " 👉 tip review the updated time range displayed in the message generated by resolve ai analysis tools resolve ai leverages a number of data sources when you want it to look in a specific tool or data type, you can enter specific prompts spans and traces use when exploring performance bottlenecks or errors in distributed applications that are instrumented with tracing example prompts "check the spans for error patterns in my checkout application" "explain why traces in my checkout application have been slower than 2 minutes " "can you explain trace e97f261d4fccfdbfb19be22e5174ab5e that happened 2 hours ago?" logs useful when deep diving into error logs or issues that are captured in logs example prompts "show error logs for my checkout application " "were there any 5xx log entries around 5 pm yesterday?" "how often did the nullpointexception log occur in the last hour?" dashboards ideal for short and long term trends captured by metrics on dashboards example prompts "check dashboards to evaluate the health of my checkout application " "investigate trends on @my dashboard over the last 2 days " 👉 tip use "@" to explicitly select or get auto suggestions on dashboard names events great for change detection and deployments example prompts "were there any change events on my checkout application in the last day?" "check kubernetes events on the my k8s ns namespace " configurations to validate or suspect config drift or bad deploys example prompts "what is the current configuration of my checkout deployment?" "show me a diff of the current configuration vs the last known configuration for the svc analysis deployment over the past 24 hours " use cases and examples service outage use case a service in staging is failing example prompt change impact use case new deploy introduced a performance issue example prompt trace level question use case detailed analysis on a large trace example prompt errors in spans use case specifically analyze spans for errors example prompt