Skip to content

OTEL export broken in GO Feature Flags #444

Closed

Description

@aaronpowell
          Did you get the OTEL exporter to work? @aaronpowell

Originally posted by @Odonno in #425 (comment)

Activity

  1. self-assigned this
    on Feb 5, 2025
  2. added theissue type on Feb 5, 2025
  3. aaronpowell commented on Feb 6, 2025

    @aaronpowell
    MemberAuthor

    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.

  4. Odonno commented on Feb 6, 2025

    @Odonno
    Contributor

    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?

  5. aaronpowell commented on Feb 7, 2025

    @aaronpowell
    MemberAuthor

    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.

  6. github-actions commented on Feb 28, 2025

    @github-actions
    Contributor

    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.

  7. Odonno commented on Feb 28, 2025

    @Odonno
    Contributor

    /stale-extend ?

  8. github-actions commented on Mar 22, 2025

    @github-actions
    Contributor

    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.

  9. github-actions commented on Apr 6, 2025

    @github-actions
    Contributor

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

  10. added
    awaiting responseWaiting for the author of the issue to provide more information or answer a question
    on Apr 7, 2025
  11. github-actions commented on Oct 13, 2025

    @github-actions
    Contributor

    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.

  12. github-actions commented on Oct 27, 2025

    @github-actions
    Contributor

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

  13. danegsta commented on Nov 12, 2025

    @danegsta

    Just tested this with the new Aspire 13 support for automatically trusting the dev cert and telemetry is flowing automatically, even over https when WithOtlpSupport() is added to a go feature flags resource.

  14. danegsta commented on Nov 12, 2025

    @danegsta

    @aaronpowell this should only require adding WithOtlpSupport() to the defaults for AddGoFeatureFlag.

  15. added this to the 13 milestone on Nov 12, 2025
  16. Odonno commented on Feb 2, 2026

    @Odonno
    Contributor

    I still have the issue unfortunately. But now I strongly believe this might be due to Podman in some way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

awaiting responseWaiting for the author of the issue to provide more information or answer a question

Type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions