-
Notifications
You must be signed in to change notification settings - Fork 21
Open
Labels
.EFFORT.LowDaysDays.RISK.LowWell-understood task, mostly mechanicalWell-understood task, mostly mechanical.VALUE.MediumImproves reliability, performance, or developer experienceImproves reliability, performance, or developer experienceTOPIC.ObservabilityMostly relate to logs, traces and metricsMostly relate to logs, traces and metrics
Milestone
Description
Abstract
This would enable us to:
- See which stages might be blocked at runtime
- Inspect an individual trace.
- Check performances
Ideally we should be able to observe the behavior of 2 or 3 connected amaru nodes.
Why?
This can help validate the runtime behavior of the node, less seen as a black box, without having to scour all the logs.
How?
Mostly by:
- Evolving
otel-uito display several services. - Making sure we display the relevant spans
Testing Strategy / Acceptance Criteria
Start otel-ui locally, a node topology and observe traces in the browser.
Discussion points
No response
Dependencies & Related Tasks
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?)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
.EFFORT.LowDaysDays.RISK.LowWell-understood task, mostly mechanicalWell-understood task, mostly mechanical.VALUE.MediumImproves reliability, performance, or developer experienceImproves reliability, performance, or developer experienceTOPIC.ObservabilityMostly relate to logs, traces and metricsMostly relate to logs, traces and metrics
Type
Projects
Status
No status