Skip to content

Commit

Permalink
moved two workshops under debug problems scenario
Browse files Browse the repository at this point in the history
  • Loading branch information
dmitchsplunk committed Sep 6, 2024
1 parent a1285c0 commit 914bd94
Show file tree
Hide file tree
Showing 77 changed files with 15 additions and 6 deletions.
9 changes: 9 additions & 0 deletions content/en/scenarios/debug_problems/_index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
---
title: Debug Problems in Microservices
linkTitle: Debug Problems in Microservices
weight: 3
description: This scenario helps engineering teams identify and fix issues caused by planned and unplanned changes to their microservices-based applications.

---

{{% children description="true" %}}
Original file line number Diff line number Diff line change
@@ -1,11 +1,11 @@
---
title: Debug Problems in Microservices - Profiling
linkTitle: Debug Problems in Microservices - Profiling
title: Profiling Workshop
linkTitle: Profiling Workshop
weight: 3
archetype: chapter
time: 2 minutes
authors: ["Derek Mitchell"]
description: This scenario uses Database Query Performance and AlwaysOn Profiling to reduce the time required for engineers to debug problems in microservices.
description: This workshop shows how Database Query Performance and AlwaysOn Profiling can be used to reduce the time required for engineers to debug problems in microservices.

---

Expand Down
Original file line number Diff line number Diff line change
@@ -1,11 +1,11 @@
---
title: Debug Problems in Microservices - Tagging
linkTitle: Debug Problems in Microservices - Tagging
title: Tagging Workshop
linkTitle: Tagging Workshop
weight: 2
archetype: chapter
time: 2 minutes
authors: ["Derek Mitchell"]
description: This scenario uses tags to reduce the time required for SREs to isolate issues across services, so they know which team to engage to troubleshoot the issue further, and can provide context to help engineering get a head start on debugging.
description: This workshop shows how tags can be used to reduce the time required for SREs to isolate issues across services, so they know which team to engage to troubleshoot the issue further, and can provide context to help engineering get a head start on debugging.

---

Expand Down

0 comments on commit 914bd94

Please sign in to comment.