Troubleshooting - Amazon CloudWatch

Troubleshooting

The following are the common troubleshooting scenarios and solutions for OTLP endpoint.

Issue Description Solution

Non-existing AWS credentials when launching OCB collector

Collector throws the following error when starting.

Error: invalid configuration: extensions::sigv4auth: could not retrieve credential provider: failed to refresh cached credentials, no EC2 IMDS role found, operation error ec2imds: GetMetadata, request canceled, context deadline exceeded.

Enter the correct credentials.

Invalid AWS credentials

Collector throws HTTP Status Code 403, Message=The security token included in the request is invalid., Details=[]“ when sending requests though OTLP endpoint.

 Refresh the AWS credentials on the collector server.

Transactions Search disabled

Collector throws Message=The OTLP API is supported with CloudWatch Logs as a Trace Segment Destination.

 Make sure Transaction Search is enabled in CloudWatch before using the OTLP endpoint for traces. For more information, see Transaction Search.
Batching and timeout issues

Collector throws one of these issues:

  • max elapsed time expired failed to make an HTTP request

  • io.opentelemetry.exporter.internal.http.HttpExporter - Failed to export spans. The request could not be executed. Full error message: timeout

  • io.opentelemetry.exporter.internal.grpc.GrpcExporter - Failed to export spans. Server responded with gRPC status code 2. Error message: timeout

  • rpc error: code = DeadlineExceeded desc = context deadline exceeded

  • rpc error: code = ResourceExhausted desc = Too many requests", "dropped_items": 1024

 Tune batching and timeout policies using batchprocessor.
Retry issues

Transient network issues between the collector and OTLP endpoint.

  • rpc error: code = Unavailable desc = error reading from server: read tcp

  • rpc error: code = Unavailable desc = unexpected HTTP status code received from server: 502 (Bad Gateway);

  • rpc error: code = Unavailable desc = unexpected HTTP status code received from server: 503 (Service Unavailable)

 Tune retry policy using exporter.
Payload rejected NA Make sure the payload sent to the trace endpoint is within the limits and restrictions. For more information, see Endpoint limits and restrictions.