Skip to content

Commit f515488

Browse files
author
p-hagen-sfx
committed
few MD fixes & fixed alert bug blocking Hugo
1 parent cf60401 commit f515488

File tree

1 file changed

+14
-12
lines changed

1 file changed

+14
-12
lines changed

content/en/tko/session-2/docs/instrument.md

Lines changed: 14 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,32 +1,34 @@
1-
# Instrument REVIEWS for Tracing
2-
## Use Data Setup to instrument a Python application.
1+
# Instrument REVIEWS for Tracing
2+
3+
## Use Data Setup to instrument a Python application
4+
35
Within the O11y Cloud UI:
46

57
Data Setup -> Monitor Applications -> Python (traces) -> Add Integration
68

79
Provide the following to the Configure Integration Wizard:
8-
- Service: review
9-
- Django: no
10+
11+
- Service: review
12+
13+
- Django: no
1014
- collector endpoint: http://localhost:4317
11-
- Environment: rtapp-workshop-<YOURNAME>
15+
- Environment: rtapp-workshop-[YOURNAME]
1216
- Kubernetes: yes
1317
- Legacy Agent: no
14-
1518

1619
We are instructed to:
1720

18-
* Install the instrumentation packages for your Python environment.
19-
20-
pip install splunk-opentelemetry[all]
21+
- Install the instrumentation packages for your Python environment.
22+
23+
pip install splunk-opentelemetry[all]
2124

2225
splunk-py-trace-bootstrap
2326

24-
* Configure the Downward API to expose environment variables to Kubernetes
27+
- Configure the Downward API to expose environment variables to Kubernetes
2528
resources.
2629

2730
For example, update a Deployment to inject environment variables by adding .spec.template.spec.containers.env like:
2831

29-
```
3032
apiVersion: apps/v1
3133
kind: Deployment
3234
spec:
@@ -62,7 +64,7 @@ The actions we must perform include:
6264
- Update our Dockerfile for REVIEW so that our program is bootstrapped with splunk-py-trace
6365
6466
{{% alert title="Note" color="info" %}} We will accomplish this by 1) generating a new requirements.txt file, 2) generating a new container image with an updated Dockerfile for REVIEW and then 3) update the review.deployment.yaml to capture all of these changes.
65-
{{% / alert}}
67+
{{% /alert%}}
6668
6769
6870
## 1: Update the REVIEW container

0 commit comments

Comments
 (0)