Skip to content

Refactor observability setup in heartbeats/event_display #8643

Open

Description

@Cali0707

Given the similarities in the two sets of code, I wonder whether extracting them into a common method would be helpful, possibly with a signature like:

// SetUpObservability configures global otel meter and tracing providers, returning a
// cleanup function to be called on shutdown, and an error.
SetUpObservability(context.Context) (func(), error)

Originally posted by @evankanderson in #8640 (comment)

Activity

  1. github-actions commented on Oct 17, 2025

    @github-actions
    Contributor

    This issue is stale because it has been open for 90 days with no
    activity. It will automatically close after 30 more days of
    inactivity. Reopen the issue with /reopen. Mark the issue as
    fresh by adding the comment /remove-lifecycle stale.

  2. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Oct 17, 2025
  3. creydr commented on Oct 20, 2025

    @creydr
    Member

    /remove-lifecycle stale

  4. removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Oct 20, 2025
  5. Arpit529Srivastava commented on Mar 10, 2026

    @Arpit529Srivastava
    Contributor

    @creydr would like to work on this next, can you assign

  6. creydr commented on Mar 10, 2026

    @creydr
    Member

    sure.
    /assign @Arpit529Srivastava

    FYI: you can assign issues to yourself by commenting /assign

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

Metadata

Metadata

Labels

triage/acceptedIssues which should be fixed (post-triage)

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions