Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AWS XRay exporter receiving http 408 error #36338

Open
AchuthSankar opened this issue Nov 12, 2024 · 4 comments
Open

AWS XRay exporter receiving http 408 error #36338

AchuthSankar opened this issue Nov 12, 2024 · 4 comments
Labels
bug Something isn't working exporter/awsxray needs triage New item requiring triage Stale

Comments

@AchuthSankar
Copy link

Component(s)

exporter/awsxray

What happened?

Description

OTEL Collector when configured with AWS Xray is receving error message from AWS Xray as follows:
error internal/base_exporter.go:153 Exporting failed. Rejecting data. {"kind": "exporter", "data_type": "traces", "name": "awsxray", "error": "Permanent error: : \n\tstatus code: 408, request id: ", "rejected_items": 512}

Steps to Reproduce

Steps to reproduce:
OTEL configuration:

  receivers:
  otlp:
	protocols:
	  grpc:
		endpoint: 0.0.0.0:4317
	  http:
		endpoint: 0.0.0.0:4318
processors:
  memory_limiter:
	check_interval: 1s
	limit_percentage: 75
	spike_limit_percentage: 15
  batch:
	send_batch_max_size: 50
	send_batch_size: 50
exporters:
  awsxray:
	region: us-east-1
service:
  pipelines:
	traces:
	  receivers: [otlp]
	  processors: [memory_limiter, batch]
	  exporters: [awsxray]

OTEL collector Version: otelcol-contrib version 0.111.0

Otel collector is deployed in a pod with 1gb RAM and 500m cpu. There are 2 replicas.

Expected Result

No Error should come, all traces should be visible in AWS Xray

Actual Result

warn [email protected]/batch_processor.go:279 Sender failed {"kind": "processor", "name": "batch", "pipeline": "traces", "error": "Permanent error: : \n\tstatus code: 408, request id: "}

Collector version

otelcol-contrib version 0.111.0

Environment information

Environment

OTEL Contrib binary 0.111.0 downloaded from github
OS: Rocky Linux (uname -a: 6.1.79-99.167.amzn2023.x86_64)

OpenTelemetry Collector configuration

receivers:
  otlp:
	protocols:
	  grpc:
		endpoint: 0.0.0.0:4317
	  http:
		endpoint: 0.0.0.0:4318
processors:
  memory_limiter:
	check_interval: 1s
	limit_percentage: 75
	spike_limit_percentage: 15
  batch:
	send_batch_max_size: 50
	send_batch_size: 50
exporters:
  awsxray:
	region: us-east-1
service:
  pipelines:
	traces:
	  receivers: [otlp]
	  processors: [memory_limiter, batch]
	  exporters: [awsxray]

Log output

2024-11-12T20:59:56.392Z        error   internal/base_exporter.go:153   Exporting failed. Rejecting data.       {"kind": "exporter", "data_type": "traces", "name": "awsxray", "error": "Permanent error: : \n\tstatus code: 408, request id: ", "rejected_items": 50}
go.opentelemetry.io/collector/exporter/exporterhelper/internal.(*BaseExporter).Send
        go.opentelemetry.io/collector/[email protected]/exporterhelper/internal/base_exporter.go:153
go.opentelemetry.io/collector/exporter/exporterhelper.NewTracesRequestExporter.func1
        go.opentelemetry.io/collector/[email protected]/exporterhelper/traces.go:136
go.opentelemetry.io/collector/consumer.ConsumeTracesFunc.ConsumeTraces
        go.opentelemetry.io/collector/[email protected]/traces.go:26
go.opentelemetry.io/collector/processor/batchprocessor.(*batchTraces).export
        go.opentelemetry.io/collector/processor/[email protected]/batch_processor.go:434
go.opentelemetry.io/collector/processor/batchprocessor.(*shard).sendItems
        go.opentelemetry.io/collector/processor/[email protected]/batch_processor.go:277
go.opentelemetry.io/collector/processor/batchprocessor.(*shard).processItem
        go.opentelemetry.io/collector/processor/[email protected]/batch_processor.go:249
go.opentelemetry.io/collector/processor/batchprocessor.(*shard).startLoop
        go.opentelemetry.io/collector/processor/[email protected]/batch_processor.go:234
2024-11-12T20:59:56.392Z        warn    [email protected]/batch_processor.go:279  Sender failed   {"kind": "processor", "name": "batch", "pipeline": "traces", "error": "Permanent error: : \n\tstatus code: 408, request id: "}

Additional context

No response

@AchuthSankar AchuthSankar added bug Something isn't working needs triage New item requiring triage labels Nov 12, 2024
Copy link
Contributor

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@AchuthSankar
Copy link
Author

This is intermittent it works for some time and then in between its throws the error. No pattern as such,
sample of dates at which this error happened
2024-11-12T20:49:19
2024-11-12T20:59:56
2024-11-12T21:01:42
2024-11-12T21:12:13

@AchuthSankar
Copy link
Author

any help is much appreciated

Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working exporter/awsxray needs triage New item requiring triage Stale
Projects
None yet
Development

No branches or pull requests

1 participant