Skip to content

Commit 013710f

Browse files
committed
Add navigation to scenario pages
1 parent 9958df4 commit 013710f

File tree

3 files changed

+25
-11
lines changed

3 files changed

+25
-11
lines changed

scenario1.md

Lines changed: 13 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ finally
3434
}
3535
```
3636

37-
Recapping: besides the custom SQL dependency tracking needed for OpenTelemetry **no custom code (besides SDK bootstrapping) is required**.
37+
Recapping: besides the custom SQL dependency tracking needed for OpenTelemetry, **no custom code (besides SDK bootstrapping) is required**.
3838

3939
## Requirement validation
4040

@@ -44,35 +44,35 @@ In Jaeger UI, traces can be filtered by service and operation, displaying an ove
4444

4545
![Jaeger trace overview](media/01-jaeger-dbtime-calls.png)
4646

47-
In application insights this is available under Performance:
47+
In Application Insights the same information is available under Performance:
4848

4949
![Application Insights trace overview](media/01-ai-dbtime-calls.png)
5050

5151
### 2. Duration of SQL operations
5252

53-
In Jaeger, clicking on a trace display details it, including the SQL call duration:
53+
In Jaeger, clicking on a trace display detailed information, including the SQL call duration:
5454

5555
![Jaeger trace details](media/01-jaeger-getdbtime.png)
5656

57-
In application insights we can view as dependencies:
57+
In Application Insights we can either view as dependencies:
5858

5959
![As dependencies](media/01-ai-dependencies-list.png)
6060

61-
Or as part of the end to end transaction:
61+
Or as part of the end-to-end transaction:
6262

6363
![As end to end transaction](media/01-ai-getdbtime-detail.png)
6464

6565
### 3. Log information containing SQL Server response
6666

67-
As the sample application is using Application Insights as logging provider the screenshot below shows how the log can be scoped to the end to end transaction.
67+
As the sample application is using Application Insights as logging provider the screenshot below shows how the log can be scoped to the end-to-end transaction.
6868

6969
![AI logs](media/01-ai-getdbtime-items.png)
7070

71-
This is powerful! If you have distinct system taking care of tracing and logging finding logs for a trace won't be so simple.
71+
This is powerful. If you have distinct system taking care of tracing and logging finding logs for a trace won't be so simple.
7272

7373
## Running this scenario
7474

75-
In order to run this scenario locally ensure that following requirements are met:
75+
In order to run this scenario locally ensure the following requirements are met:
7676

7777
- SQL Server is available at `server=localhost;user id=sa;password=Pass@Word1;`<br/>
7878
A way to accomplish it is to run as a linux docker container:
@@ -103,3 +103,8 @@ To run the sample start the project Sample.TimeApi. To generate load use the fol
103103
```bash
104104
watch -n 1 curl --request GET http://localhost:5002/api/time/dbtime
105105
```
106+
107+
## Where to go next
108+
109+
- [Back to overview](./README.md)
110+
- [Scenario 2: REST API call chain](./scenario2.md)

scenario2.md

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ The dependency graph in Application Insights is available under Application Map:
6969

7070
## Running this scenario
7171

72-
In order to run this scenario locally ensure that following requirements are met:
72+
In order to run this scenario locally ensure the following requirements are met:
7373

7474
- SQL Server is available at `server=localhost;user id=sa;password=Pass@Word1;`<br/>
7575
A way to accomplish it is to run as a linux docker container:
@@ -99,4 +99,9 @@ To run the sample start the projects Sample.TimeApi and Sample.MainApi. To gener
9999

100100
```bash
101101
watch -n 1 curl --request GET http://localhost:5001/api/dbtime
102-
```
102+
```
103+
104+
## Where to go next
105+
106+
- [Back to overview](./README.md)
107+
- [Scenario 3: Asynchronous transactions](./scenario3.md)

scenario3.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -163,7 +163,7 @@ Visualization for Application Insights is available under "Metrics":
163163

164164
## Running this scenario
165165

166-
In order to run this scenario locally ensure that following requirements are met:
166+
In order to run this scenario locally ensure the following requirements are met:
167167

168168
- SQL Server is available at `server=localhost;user id=sa;password=Pass@Word1;`<br/>
169169
A way to accomplish it is to run as a linux docker container:
@@ -223,3 +223,7 @@ Enqueuing from "WebSiteC" every 30 seconds
223223
```bash
224224
watch -n 30 curl --request GET http://localhost:5001/api/enqueue/WebSiteC
225225
```
226+
227+
## Where to go next
228+
229+
- [Back to overview](./README.md)

0 commit comments

Comments
 (0)