OTEL export broken in GO Feature Flags

[aaronpowell]

          Did you get the OTEL exporter to work? @aaronpowell

Originally posted by @Odonno in #425 (comment)

[aaronpowell]

I think the problem might be caused by the OTLE endpoint being served on a self-signed certificate from the Aspire app host, which then isn't trusted in the container. This is mostly a problem with container resources because executable resources run on the host which the aspnet dev cert is trusted, whereas inside the container it hasn't been trusted.

[Odonno]

I trust you on that. I am also unsure if it is related to the private IP address, can't the OTEL endpoint be consumed via its service name?

[aaronpowell]

The way the networking is configured with Docker the endpoint that it access it via, host.docker.internal:<some port>, is available within the container, but the SSL certificate for the OTEL endpoint isn't valid so it fails.

[github-actions]

We have noticed this issue has not been updated within 21 days. If there is no action on this issue in the next 14 days, we will automatically close it. You can use /stale-extend to extend the window.

[Odonno]

/stale-extend ?

[github-actions]

We have noticed this issue has not been updated within 21 days. If there is no action on this issue in the next 14 days, we will automatically close it. You can use /stale-extend to extend the window.

[github-actions]

This issue has been stale for 5 weeks and has been automatically closed.