Seth L

You may want to ask this question in the instrumentation repos. I do not think this is related to the collector @Aneurysm9 @anuraaga

From the docs enable debugging log add a key value pair into /opt/aws/aws-otel-collector/etc/extracfg.txt and restart collector echo "loggingLevel=DEBUG" | sudo tee -a /opt/aws/aws-otel-collector/etc/extracfg.txt sudo /opt/aws/aws-otel-collector/bin/aws-otel-collector-ctl -a stop sudo /opt/aws/aws-otel-collector/bin/aws-otel-collector-ctl -a...

https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/awsecscontainermetricsreceiver/internal/awsecscontainermetrics/resource.go#L66 not sure why it is set like this I will try to hunt down who wrote this code

So while this is not supported officially. You can test installing the red hat arm64 rpm. It should work but no guarantees from my end.

I do not see cache being added

The code has been merged and should be available in release 16 of otel. If you would like to test this code I can create a unofficial docker image for...

Why do you not run in ecs fargate with our samples?

https://github.com/aws-observability/aws-otel-test-framework/blob/terraform/terraform/eks/main.tf#L170-L174 look here for setting the url of the mock server. Note sample app url is already set up

Create ingress for mock server sample app ingress here https://github.com/aws-observability/aws-otel-test-framework/blob/terraform/terraform/eks/otlp.tf#L255-L287

Check how pod type works for sample app then use for mock server https://github.com/aws-observability/aws-otel-test-framework/blob/terraform/terraform/eks/otlp.tf#L234-L253