Skip to content
This repository was archived by the owner on Sep 2, 2025. It is now read-only.

Commit a8195e6

Browse files
committed
remove numbering
1 parent 6ff9874 commit a8195e6

File tree

1 file changed

+12
-12
lines changed

1 file changed

+12
-12
lines changed

get-started/o11y-ai-promptlibrary.rst

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -193,16 +193,16 @@ This section shows examples of situations in which you can use the Assistant to
193193

194194
When you receive an alert, possible prompts you might use in the Assistant to help resolve the incident include the following:
195195

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?
197197

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?
199199

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?
201201

202202
.. raw:: html
203203

204204
<embed>
205-
<h4>Example prompt 1: Poor<a name="example-prompt-1-poor" class="headerlink" href="#example-prompt-1-poor" title="Permalink to this headline">¶</a></h4>
205+
<h4>Example prompt: Poor<a name="example-prompt-1-poor" class="headerlink" href="#example-prompt-1-poor" title="Permalink to this headline">¶</a></h4>
206206
</embed>
207207

208208
: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
212212
.. raw:: html
213213

214214
<embed>
215-
<h4>Example prompt 2: Good<a name="example-prompt-2-good" class="headerlink" href="#example-prompt-2-good" title="Permalink to this headline">¶</a></h4>
215+
<h4>Example prompt: Good<a name="example-prompt-2-good" class="headerlink" href="#example-prompt-2-good" title="Permalink to this headline">¶</a></h4>
216216
</embed>
217217

218218
: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
222222
.. raw:: html
223223

224224
<embed>
225-
<h4>Example prompt 3: Excellent<a name="example-prompt-3-excellent" class="headerlink" href="#example-prompt-3-excellent" title="Permalink to this headline">¶</a></h4>
225+
<h4>Example prompt: Excellent<a name="example-prompt-3-excellent" class="headerlink" href="#example-prompt-3-excellent" title="Permalink to this headline">¶</a></h4>
226226
</embed>
227227

228228
: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
237237

238238
When a service is experiencing problems, possible prompts you might use to help resolve the incident include the following:
239239

240-
* Example 1: Show me the last 3 traces for apm-classic errors.
240+
* Show me the last 3 traces for apm-classic errors.
241241

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?
243243

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
245245

246246
.. raw:: html
247247

248248
<embed>
249-
<h4>Example prompt 1: Poor<a name="id1" class="headerlink" href="#id1" title="Permalink to this headline">¶</a></h4>
249+
<h4>Example prompt: Poor<a name="id1" class="headerlink" href="#id1" title="Permalink to this headline">¶</a></h4>
250250
</embed>
251251

252252
: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
256256
.. raw:: html
257257

258258
<embed>
259-
<h4>Example prompt 2: Good<a name="id2" class="headerlink" href="#id2" title="Permalink to this headline">¶</a></h4>
259+
<h4>Example prompt: Good<a name="id2" class="headerlink" href="#id2" title="Permalink to this headline">¶</a></h4>
260260
</embed>
261261

262262
: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
266266
.. raw:: html
267267

268268
<embed>
269-
<h4>Example prompt 3: Excellent<a name="id3" class="headerlink" href="#id3" title="Permalink to this headline">¶</a></h4>
269+
<h4>Example prompt: Excellent<a name="id3" class="headerlink" href="#id3" title="Permalink to this headline">¶</a></h4>
270270
</embed>
271271

272272
: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

Comments
 (0)