I did setup the extension, and got the following logs when using LAMBDA_INSIGHTS_LOG_LEVEL=info
INIT_START Runtime Version: nodejs:16.v11 Runtime Version ARN: arn:aws:lambda:us-east-1::runtime:ee071345fbee0f4751fcbcd47a5784052d8f7d4256ca7f31e6056b294cee515c
--
[2023-02-06T13:15:45.700Z INFO cloudwatch_lambda_agent] Logging initialized.
[2023-02-06T13:15:45.703Z INFO cloudwatch_lambda_agent::rapid::rapid_client] Registering the Lambda Insights Extension.
[2023-02-06T13:15:45.748Z INFO cloudwatch_lambda_agent] Event sink started.
[2023-02-06T13:15:45.748Z INFO cloudwatch_lambda_agent::logs::logs_server] Initialized logging server on port 3000
[2023-02-06T13:15:45.748Z INFO cloudwatch_lambda_agent::rapid::rapid_client] Requesting subscription to logs at: http://127.0.0.1:9001/2020-08-15/logs with agent_id: 0df15f0b-0427-4566-9b11-dfcc7b0221e5
LOGS Name: cloudwatch_lambda_agent State: Subscribed Types: [Platform]
thread 'sender' panicked at 'cannot access native cert store: Os { code: 2, kind: NotFound, message: "No such file or directory" }', /local/p4clients/pkgbuild-MH37M/workspace/build/AWSLogsLambdaInsights/AWSLogsLambdaInsights-1.0.98.0/AL2012/DEV.STD.PTHREAD/build/private/cargo-home/registry/src/-7a426414fc8f052b/hyper-rustls-0.20.0/src/connector.rs:46:30
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
EXTENSION Name: cloudwatch_lambda_agent State: Ready Events: [INVOKE,SHUTDOWN]
START RequestId: 512bbc82-3475-4f40-9273-70641b82c7cd Version: $LATEST
[2023-02-06T13:15:46.837Z INFO cloudwatch_lambda_agent::runtime_event_collector] Received next response from runtime api.
[2023-02-06T13:15:46.842Z INFO cloudwatch_lambda_agent::event_sink] Received invoke event for request 512bbc82-3475-4f40-9273-70641b82c7cd. Map size: 0
[2023-02-06T13:15:46.842Z INFO cloudwatch_lambda_agent::event_sink] Completed match. Map size: 1
END RequestId: 512bbc82-3475-4f40-9273-70641b82c7cd
REPORT RequestId: 512bbc82-3475-4f40-9273-70641b82c7cd Duration: 450.71 ms Billed Duration: 451 ms Memory Size: 1024 MB Max Memory Used: 145 MB Init Duration: 1181.47 ms XRAY TraceId: 1-63e0fd81-54338b9008cb957431cf8647 SegmentId: 28a8641802bcd381 Sampled: true
[2023-02-06T13:22:16.331Z INFO cloudwatch_lambda_agent::logs::logs_server] Received platform metrics for 512bbc82-3475-4f40-9273-70641b82c7cd
[2023-02-06T13:22:16.331Z INFO cloudwatch_lambda_agent::event_sink] Received platform metrics for request 512bbc82-3475-4f40-9273-70641b82c7cd. Map size: 1
[2023-02-06T13:22:16.331Z INFO cloudwatch_lambda_agent::event_sink] Not writing metrics for report event because next invoke has not been received.
[2023-02-06T13:22:16.331Z INFO cloudwatch_lambda_agent::event_sink] Completed match. Map size: 1
[2023-02-06T13:22:16.336Z INFO cloudwatch_lambda_agent::runtime_event_collector] Received next response from runtime api.
[2023-02-06T13:22:16.336Z INFO cloudwatch_lambda_agent::runtime_event_collector] Received SHUTDOWN event with reason Some("spindown")
[2023-02-06T13:22:16.337Z INFO cloudwatch_lambda_agent] Joining on sink handle.
[2023-02-06T13:22:16.337Z INFO cloudwatch_lambda_agent::event_sink] Received system metrics for request 512bbc82-3475-4f40-9273-70641b82c7cd. Map size: 1
[2023-02-06T13:22:16.337Z INFO cloudwatch_lambda_agent::outputs::cloudwatch::event_buffer] Event buffer received event
[2023-02-06T13:22:16.337Z INFO cloudwatch_lambda_agent::outputs::cloudwatch::event_buffer] Flushing batch of 1 events after 390.588483445s to /aws/lambda-insights::ingester-service-staging-removeV1Async/LAG3jZeeWlwdItDk9eYKNVEni
[2023-02-06T13:22:16.337Z ERROR cloudwatch_lambda_agent::outputs::cloudwatch::event_buffer] Failed to write batch of performance events due to full buffer. "Disconnected(..)"
[2023-02-06T13:22:16.337Z INFO cloudwatch_lambda_agent::event_sink] Completed match. Map size: 0
[2023-02-06T13:22:16.337Z INFO cloudwatch_lambda_agent::event_sink] Received shutdown event.
[2023-02-06T13:22:16.337Z INFO cloudwatch_lambda_agent::event_sink] Received spindown without any invoke data.
[2023-02-06T13:22:16.337Z INFO cloudwatch_lambda_agent::outputs::cloudwatch::event_buffer] Flushing event buffer because shutdown was requested.
[2023-02-06T13:22:16.337Z INFO cloudwatch_lambda_agent::outputs::cloudwatch::sender] Shutdown received in Sender.
[2023-02-06T13:22:16.337Z INFO cloudwatch_lambda_agent::outputs::cloudwatch::sender] Waiting for shutdown to complete: Requested
[2023-02-06T13:22:16.837Z INFO cloudwatch_lambda_agent::outputs::cloudwatch::sender] Waiting for shutdown to complete: Requested
[2023-02-06T13:22:17.337Z INFO cloudwatch_lambda_agent::outputs::cloudwatch::sender] Waiting for shutdown to complete: Requested
[2023-02-06T13:22:17.837Z INFO cloudwatch_lambda_agent::outputs::cloudwatch::sender] Waiting for shutdown to complete: Requested
I can't find any reference to Failed to write batch of performance events due to full buffer.
I did setup the extension, and got the following logs when using
LAMBDA_INSIGHTS_LOG_LEVEL=infoI can't find any reference to
Failed to write batch of performance events due to full buffer.