Skip to content

Conversation

jlvoiseux
Copy link
Contributor

Resolves #180

Changes

If none of ELASTIC_APM_SECRET_TOKEN or ELASTIC_APM_API_KEY are detected, the extension logs a warning instead of exiting. The docs have been updated accordingly. Note that the corresponding agent still needs to be added to the list of services allowed to communicate with the Server / Integration anonymously.

How to test

  • Setup a Python Lambda function with the Python APM Agent and the Lambda extension.
  • Add the python service to the list of services allowed to communicate anonymously with your Server / Integration
  • In the Lambda configuration, only set the following environment variables:
ELASTIC_APM_LAMBDA_APM_SERVER=<Your APM Server>
ELASTIC_APM_LOG_LEVEL=debug 

The debug log level allows us to check that the APM Server returns a 202 response.

@github-actions github-actions bot added the aws-λ-extension AWS Lambda Extension label Apr 12, 2022
@ghost
Copy link

ghost commented Apr 12, 2022

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2022-04-14T10:09:05.244+0000

  • Duration: 7 min 26 sec

Test stats 🧪

Test Results
Failed 0
Passed 184
Skipped 4
Total 188

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@jlvoiseux jlvoiseux marked this pull request as ready for review April 12, 2022 15:47
@jlvoiseux jlvoiseux merged commit 1cecd9e into elastic:main Apr 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

aws-λ-extension AWS Lambda Extension

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Running extension without Secret token and API Key

1 participant