Sd containerized lambda v3

[homelessbirds]

Please follow conventional commit standards
in your commit messages and pull request title.

Give us some context

• What problems does this PR solve?
• Add any context that will help us review your changes such as testing notes,
  links to related docs, screenshots, etc.
• If your issue relates to an existing GitHub issue, please link to it.

[github-actions]

Hi @homelessbirds 👋

Thanks for your pull request! Your PR is in a queue, and a writer will take a look soon. We generally publish small edits within one business day, and larger edits within three days.

We will automatically generate a preview of your request, and will comment with a link when the preview is ready (usually 10 to 20 minutes). If you add any more commits, you can comment netlify build on this PR to update the preview.

[netlify]

✅ Deploy Preview for docs-website-netlify ready!

Name	Link
🔨 Latest commit	0cd8ff8
🔍 Latest deploy log	https://app.netlify.com/sites/docs-website-netlify/deploys/6631665c6e2de50008f53943
😎 Deploy Preview	https://deploy-preview-17050--docs-website-netlify.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[keegoid-nr]

Specifically, the Lambda console UI configuration section details the handler wrapper details they will need to know.
https://docs.newrelic.com/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/instrument-your-own/#console

[homelessbirds]

I think I fixed this

[keegoid-nr]

I left some inline comments

[jeff-colucci]

Looks good, just a couple of small things. I think once you fix them you'll be good roll!

[akristen]

Suggested change

	If you're using a containerized image for Lambda and want to monitor your application, you'll need to add New Relic to your code. After you add our pre-built layer to your image, push the image to your AWS Elastic Container Registry. From there, whenever you run your function, New Relic will run, at the same time.
	If you're using a containerized image for Lambda and want to monitor your application, you'll need to add New Relic to your code. After you add our pre-built layer to your image, push the image to your AWS Elastic Container Registry. From there, whenever you run your function, New Relic will run at the same time.

[akristen]

I'd update the titles themselves in the doc to remove the "Step X" in all the docs

[homelessbirds]

done!

[akristen]

OK, no typos and doc makes sense / has good flow. some fast follows:

• Def update the tab component ids to be specific to the content rather than just the default numerals. There's some buggy behavior that can happen if we. keep the ids as the default values
• I'd update the titles of the docs to match what appears in the nav. for eample, when you click "Link accounts", the doc still says "Step 1"

My more general thoughts are mostly about thinking through how to make this less abstract. Some of the steps can be a little confusing if this is your first time doing this kind of task, especially since the users have to reference different docs sites.

I'm not sure what the solution is, but there are a few places where having an example throughline might help. For example:

• In step "Create image", do customers name this new image? In step 1 of configure lambda function -- "the image you pushed to AWS ECR", using an example name for a docker image might be helpful so customers can be confident that it's the new image and not the other ones that they had to use
• In "Configure your Lambda function", you mention an "original function", but I'm not sure it's clear what you're referrring to. Are we configuring the original Lambda function, making a copy of the function and customizing the copy?
• The configure your Lambda function seems like it needs some unspooling and a bit more hand holding. I have a lot more questions than I have answers, and I worry that we might miss some users who aren't Lambda experts or New Relic experts. The step seems to really address more advanced users, but I think it's helpful to unspool and add etail where possible