Skip to content

Revisit trace targets #2332

Description

@Mirko-von-Leipzig

The current set is retained from our original node components. This no longer reflects the current system entirely well, and could use some refinement imo.

It also makes sense (to me) to have the miden:: prefix on all of them so we can differentiate between ours, and third party traces.

Step one is deciding on a new set of targets for each service.

Something to consider is adding these options as outputs in #2331 so callers know what's available.

Metadata

Metadata

Assignees

No one assigned

    Labels

    telemetryRelates to tracing and open-telemetry

    Fields

    No fields configured for Enhancement.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions