chore(aggregator): implement telemetry for aggregator#949
chore(aggregator): implement telemetry for aggregator#949
Conversation
There was a problem hiding this comment.
We should probably add a TaskExpiredTrace when a task expires instead of reaching threshold, ideally should included quorum % and operators who responded if we have access to that information.
|
Other than comments, worked perfectly on my machine |
refactor: improve attributes addition
…hore-implement-opentelemetry-for-aggregator
uri-99
left a comment
There was a problem hiding this comment.
Documentation of this PR would be highly valuable, maybe even with some screenshots.
(review still WIP)
|
Is there a way to make Jaeger auto-refresh? |
| attribute.String("merkle_root", fmt.Sprintf("0x%s", hex.EncodeToString(batchMerkleRoot[:]))), | ||
| attribute.String("status", "ok"), | ||
| ), | ||
| ) // TODO add quorum % |
There was a problem hiding this comment.
Should this TODO be resolved in this PR?
There was a problem hiding this comment.
This will be added in another pr
There was a problem hiding this comment.
What do you think about adding traces around lines 317 of this file? If the aggregator fails to SendAggregatedResponse after reaching quorum
|
Superseded by #1077 |


Description
This PR allows the aggregator to export telemetry traces to have a better observability of the system
Tasks
How to Test
Note
Docker is needed to test the PR.
It will run the Otel-Collector and Jaeger UI.
Note
Jaeger UI is available on http:localhost:16686
Send tasks
Once you sent a batch and it has been responded by the aggregator, you should be able to check the trace of the task in the Jaeger UI (
http:localhost:16686)In the search, select service:
aggregatorand pressfind tracesIt should show you the tasks you sent to aligned