Felix Scheinost

Oh cool, that you have a hunch so quickly! @huskyii I just checked on a different Linux machine, that should work as well, right? In there I have the following...

@huskyii I think I was using `1.24.2` at the time. @vquicksilver Yeah, its probably a duplicate of that issue. I tried working around the issuee right now by using the...

Okay, I just ran `tailscaled` manually on Linux against official Tailscale server. I turned override local DNS on, then off again and watched the log: ``` # Turn override local...

Bump: Please don't close this PR automatically.

@mmanciop Thanks for rebasing your changes on my PR! Regarding the change in the log group ARN. That dosn't seem right to me. Have you tested this on AWS? I...

@mmanciop When I do `describe-log-groups` on my log groups I get an ARN without `/aws`. Only when the log group name contains `/aws`, like for lambdas, does the ARN also...

> The :* at the end of the ARN for the log-group, however, seem pretty legit. Yeah, I think so. It seems like it does work without it but both...

Hi @mmanciop, unfortunately even the trailing `:*` seems to break showing the logs for a trace. I cherry picked all your changes, deployed and tried showing the logs for a...

I am using CloudWatch traces on the official AWS web console.

> Besides, the spec clearly states with the example that the :* must be there: https://opentelemetry.io/docs/reference/specification/resource/semantic_conventions/cloud_provider/aws/logs/ These are merely "examples". This links also references [the official AWS documentation](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/iam-access-control-overview-cwl.html#CWL_ARN_Format), which states:...