Skip to content

minor updates to lambda workshop instructions #397

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 8, 2025
Merged

minor updates to lambda workshop instructions #397

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
069a30d
minor updates to lambda workshop instructions
dmitchsplunk Jul 8, 2025
c2271ec
Merge remote-tracking branch 'upstream/main'
dmitchsplunk Jul 8, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/en/ninja-workshops/6-lambda-kinesis/2-auto-instrumentation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -99,7 +99,7 @@ Next, let's take a look at the `producer-lambda` function code:

- Run the following command to view the contents of the `producer.mjs` file:
```bash
cat ~/o11y-lambda-workshop/auto/handler/producer.mjs
cat ~/workshop/lambda/auto/handler/producer.mjs
```
- This NodeJS module contains the code for the producer function.
- Essentially, this function receives a message, and puts that message as a record to the targeted Kinesis Stream
Expand Down
2 changes: 1 addition & 1 deletion content/en/ninja-workshops/6-lambda-kinesis/5-redeploy-lambdas.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -125,7 +125,7 @@ Examine the logs carefully.

> Do you notice the difference?

#### Copy the Trace ID from the `consumer-lambda` logs
#### Copy the Trace ID from the `consumer.logs` file

This time around, we can see that the consumer-lambda log group is logging our message as a `record` together with the `tracecontext` that we propagated.

Expand Down