-
Fix incorrect proxy transaction handling at shutdown due to not flushing the data before processing shutdown event. 412.
-
Log a warning, instead of failing a Lambda function, if auth retrieval from AWS Secrets Manager fails. Reporting APM data will not work, but the Lambda function invocations will proceed. 401
-
Use User-Agent header with Lambda extension version and propagate info from apm agents 404
-
experimental:[] Allow metadata in register transaction 384
-
Print response body on error if decoding fails 382
-
Parse and log APM Server error responses, and backoff on critical errors 281
-
Disable CGO to prevent libc/ABI compatibility issues 292
-
Deprecate
ELASTIC_APM_DATA_RECEIVER_TIMEOUT_SECONDS
in favour ofELASTIC_APM_DATA_RECEIVER_TIMEOUT
294 -
Log shutdown reason on exit 297
-
Add support for collecting and shipping function logs to APM Server 303
-
Batch data collected from lambda logs API before sending to APM Server 314
-
Fix possible data corruption while processing multiple log events 309
-
Log a warning when authentication with APM Server fails 228
-
Handle http.ErrServerClosed correctly 234
-
Handle main loop errors correctly 252
-
Avoid sending corrupted compressed data to APM Server 257
-
Avoid creating http transports on each info request 260
-
Randomise the initial grace period to avoid collisions 240
-
Handle metadata errors correctly 254
-
Always flush data to APM server before shutting down and avoid concurrent access to data channel 258
-
Only add executables to extension 216
-
Add support for building and pushing docker images 199
First stable release of the Elastic APM AWS Lambda extension.