You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This repository contains code and tools for working with Elastic APM's AWS Lambda solution.
5
+
This repository contains code and tools for working with the Elastic APM AWS Lambda extension.
6
6
7
-
If you're looking to get started with Elastic's AWS Lambda extension and agent instrumentation, the [AWS Lambda Extension](https://www.elastic.co/guide/en/apm/guide/current/monitoring-aws-lambda.html)documentation is the place to start.
7
+
Ready to use Elastic APM to monitor your Lambda functions? See [Monitoring AWS Lambda Functions](https://www.elastic.co/guide/en/apm/guide/current/monitoring-aws-lambda.html) to get started.
Copy file name to clipboardExpand all lines: apm-lambda-extension/DEVELOPMENT.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@
3
3
4
4
### :robot: Automatically
5
5
6
-
Releasing a version of the Lambda Extension requires a tag release.
6
+
Releasing a version of the Elastic APM AWS Lambda extension requires a tag release.
7
7
8
8
Tag the release via your preferred tagging method. Tagging a release (v0.0.2) via the command line looks something like this.
9
9
@@ -22,7 +22,7 @@ and a Release in the Github UI.
22
22
23
23
### :thumbsdown: Manually
24
24
25
-
Releasing a version of the Lambda Extension is currently a three step manual process.
25
+
Releasing a version of the Elastic APM AWS Lambda extension is currently a three step manual process.
26
26
27
27
1. Tag the Release
28
28
2. Create the Build Artifacts
@@ -33,7 +33,7 @@ Releasing a version of the Lambda Extension is currently a three step manual pro
33
33
See the above section regarding tagging a release.
34
34
### Create the Build Artifacts
35
35
36
-
Next, create the build artifacts for the release. These are go binaries of the Lambda Extension, built for both Intel and ARM architectures.
36
+
Next, create the build artifacts for the release. These are go binaries of the Elastic APM AWS Lambda extension, built for both Intel and ARM architectures.
37
37
38
38
If you were creating the build artifacts for the v0.0.2 release, that might look something like this
Copy file name to clipboardExpand all lines: apm-lambda-extension/e2e-testing/README.md
+3-4
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,11 @@
1
1
# End-to-End Testing
2
2
3
-
The file `e2e_test.go` contains an end-to-end test of the Elastic APM Lambda Extension. This test is built on top of the AWS SAM CLI, which allows running Lambda functions and their associated layers locally.
3
+
The file `e2e_test.go` contains an end-to-end test of the Elastic APM AWS Lambda extension. This test is built on top of the AWS SAM CLI, which allows running Lambda functions and their associated layers locally.
4
4
5
5
## Setup
6
6
7
7
Since this test is sensibly longer than the other unit tests, it is disabled by default. To enable it, go to `.e2e_test_config` and set the environment variable `RUN_E2E_TESTS` to `true`.
8
-
In order to run the Lambda functions locally, the following dependencies must be installed :
8
+
In order to run the Lambda functions locally, the following dependencies must be installed :
9
9
-[Install](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-sam-cli-install.html) the SAM CLI. Creating an AWS account is actually not required.
10
10
- Install Docker
11
11
- Install a Go Runtime
@@ -17,7 +17,7 @@ cd apm-lambda-extension/e2e-testing
17
17
go test
18
18
```
19
19
20
-
### Command line arguments
20
+
### Command line arguments
21
21
The command line arguments are presented with their default value.
22
22
```shell
23
23
-rebuild=false # Rebuilds the Lambda function images
@@ -31,4 +31,3 @@ Example :
31
31
```shell
32
32
go test -rebuild=false -lang=java -timer=40 -java-agent-ver=1.28.4
0 commit comments