feat(datastreams): added segment_name to hashable tags#4013
Conversation
BenchmarksBenchmark execution time: 2025-10-03 13:41:10 Comparing candidate commit e99cb04 in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 24 metrics, 0 unstable metrics. |
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
The merge request has been interrupted because the build 0 took longer than expected. The current limit for the base branch 'main' is 120 minutes. Possible reasons:
|
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
This PR is rejected because it was updated |
|
/merge -c |
|
View all feedbacks in Devflow UI.
This merge request is not in the queue and can't be unqueued To get help about command usage, write If you need support, contact us on Slack #devflow with those details! |
|
/merge |
|
View all feedbacks in Devflow UI.
This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
The expected merge time in
The merge request has been interrupted because the build 0 took longer than expected. The current limit for the base branch 'main' is 120 minutes. |
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
What does this PR do?
Adds new hashable tag to DSM.
Motivation
We now support latency segments, which can be set using the following code
This can be used to break down internal (processing latency).
Now:
Topic A -> Service -> Topic Bwill have internal latency from consume to produce.With
segment_name:Topic A-> Service (segment A) -> Service (segment B)-> Topic Binternal latency in this example is split into 2 named segments. The user can define any number of segments.Reviewer's Checklist
./scripts/lint.shlocally.Unsure? Have a question? Request a review!