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
{{ message }}
This repository was archived by the owner on Sep 2, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: get-started/o11y-ai-promptlibrary.rst
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -193,16 +193,16 @@ This section shows examples of situations in which you can use the Assistant to
193
193
194
194
When you receive an alert, possible prompts you might use in the Assistant to help resolve the incident include the following:
195
195
196
-
* Example 1: I received an alert related to the paymentservice. What's happening?
196
+
* I received an alert related to the paymentservice. What's happening?
197
197
198
-
* Example 2: I received an alert with incident ID Ggn_D1TA4BU. What's going on?
198
+
* I received an alert with incident ID Ggn_D1TA4BU. What's going on?
199
199
200
-
* Example 3: Can you look at my APM data and logs to understand the root cause of this issue?
200
+
* Can you look at my APM data and logs to understand the root cause of this issue?
201
201
202
202
.. raw:: html
203
203
204
204
<embed>
205
-
<h4>Example prompt 1: Poor<aname="example-prompt-1-poor"class="headerlink"href="#example-prompt-1-poor"title="Permalink to this headline">¶</a></h4>
205
+
<h4>Example prompt: Poor<aname="example-prompt-1-poor"class="headerlink"href="#example-prompt-1-poor"title="Permalink to this headline">¶</a></h4>
206
206
</embed>
207
207
208
208
:guilabel:`I received an alert related to the paymentservice. What's happening?`
@@ -212,7 +212,7 @@ This example is poor because it does not give the Assistant enough specific info
212
212
.. raw:: html
213
213
214
214
<embed>
215
-
<h4>Example prompt 2: Good<aname="example-prompt-2-good"class="headerlink"href="#example-prompt-2-good"title="Permalink to this headline">¶</a></h4>
215
+
<h4>Example prompt: Good<aname="example-prompt-2-good"class="headerlink"href="#example-prompt-2-good"title="Permalink to this headline">¶</a></h4>
216
216
</embed>
217
217
218
218
:guilabel:`I received an alert with incident ID Ggn_D1TA4BU. What's going on?`
@@ -222,7 +222,7 @@ This example is good because it is focused. It states that you received an alert
222
222
.. raw:: html
223
223
224
224
<embed>
225
-
<h4>Example prompt 3: Excellent<aname="example-prompt-3-excellent"class="headerlink"href="#example-prompt-3-excellent"title="Permalink to this headline">¶</a></h4>
225
+
<h4>Example prompt: Excellent<aname="example-prompt-3-excellent"class="headerlink"href="#example-prompt-3-excellent"title="Permalink to this headline">¶</a></h4>
226
226
</embed>
227
227
228
228
:guilabel:`Can you look at my APM data and logs to understand the root cause of this issue?`
@@ -237,16 +237,16 @@ If you are looking at an alert in the UI, this prompt is excellent because the A
237
237
238
238
When a service is experiencing problems, possible prompts you might use to help resolve the incident include the following:
239
239
240
-
* Example 1: Show me the last 3 traces for apm-classic errors.
240
+
* Show me the last 3 traces for apm-classic errors.
241
241
242
-
* Example 2: Paymentservice in online boutique env is having issues in past 15 mins. What's going on?
242
+
* Paymentservice in online boutique env is having issues in past 15 mins. What's going on?
243
243
244
-
* Example 3: Paymentservice in online boutique env is having issues in past 15 mins. Look for any relevant error exemplar traces. Once you've identified the exemplar traces, analyze each full trace by its trace ID
244
+
* Paymentservice in online boutique env is having issues in past 15 mins. Look for any relevant error exemplar traces. Once you've identified the exemplar traces, analyze each full trace by its trace ID
245
245
246
246
.. raw:: html
247
247
248
248
<embed>
249
-
<h4>Example prompt 1: Poor<aname="id1"class="headerlink"href="#id1"title="Permalink to this headline">¶</a></h4>
249
+
<h4>Example prompt: Poor<aname="id1"class="headerlink"href="#id1"title="Permalink to this headline">¶</a></h4>
250
250
</embed>
251
251
252
252
:guilabel:`Show me the last 3 traces for apm-classic errors.`
@@ -256,7 +256,7 @@ This prompt is poor because you do not give the Assistant a time range or enviro
256
256
.. raw:: html
257
257
258
258
<embed>
259
-
<h4>Example prompt 2: Good<aname="id2"class="headerlink"href="#id2"title="Permalink to this headline">¶</a></h4>
259
+
<h4>Example prompt: Good<aname="id2"class="headerlink"href="#id2"title="Permalink to this headline">¶</a></h4>
260
260
</embed>
261
261
262
262
:guilabel:`Paymentservice in online boutique env is having issues in past 15 mins. What's going on?`
@@ -266,7 +266,7 @@ This prompt is good because it gives the service and the time range. Telling the
266
266
.. raw:: html
267
267
268
268
<embed>
269
-
<h4>Example prompt 3: Excellent<aname="id3"class="headerlink"href="#id3"title="Permalink to this headline">¶</a></h4>
269
+
<h4>Example prompt: Excellent<aname="id3"class="headerlink"href="#id3"title="Permalink to this headline">¶</a></h4>
270
270
</embed>
271
271
272
272
:guilabel:`Paymentservice in online boutique env is having issues in past 15 mins. Look for any relevant error exemplar traces. After identifying the exemplar traces, analyze each full trace by its trace ID`
0 commit comments