Skip to content

Make sure that all consensus / network stages use the observability crate format #696

@etorreborre

Description

@etorreborre

Abstract

Once the new consensus stages are merged, make sure that the traces follow the guidelines set by #638

Why?

This is important to ensure the stability of tracing.

How?

By using the existing guidelines.

Testing Strategy / Acceptance Criteria

Collecting the traces and checking them.

Discussion points

No response

Dependencies & Related Tasks

No response

Checklist

  • I understand that feature requests and unrefined work item should be open as GitHub Discussions instead.
  • I have assigned this item to an existing milestone from the roadmap
  • I have added a label capturing the impact of this item (i.e. value for users/stakeholders if successful)
  • I have added a label capturing the delivery risk of this item (i.e. how likely is it that this task will succeed as planned)
  • I have added a label capturing the effort of this item (i.e. how large is the task?)

Metadata

Metadata

Assignees

Labels

.EFFORT.LowDays.RISK.LowWell-understood task, mostly mechanical.VALUE.MediumImproves reliability, performance, or developer experienceTOPIC.DeploymentMostly related to deployments, releases, continuous delivery, etc..TOPIC.ObservabilityMostly relate to logs, traces and metrics

Type

Projects

Status

No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions