Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
089e4d7 to
74cc380
Compare
74cc380 to
eae62f5
Compare
b17ae82 to
5d2d1c0
Compare
5d2d1c0 to
b01874b
Compare
19d131a to
6a90429
Compare
6a90429 to
f18df04
Compare
b01874b to
aaef818
Compare
aaef818 to
9ffbdec
Compare
f18df04 to
6601f83
Compare
9ffbdec to
9d8800f
Compare
6601f83 to
6d042b6
Compare
9d8800f to
bb9ab4d
Compare
6d042b6 to
10f6fca
Compare
7a78bb2 to
7bfe432
Compare
2687544 to
da8aa60
Compare
7bfe432 to
d6f15cb
Compare
da8aa60 to
9293145
Compare
This commit allows users to configure an otel metrics payload that has a fixed number of 'contexts' to reuse the term from dogstatsd. This is done by setting a lot of fiddly knobs and the user is responsible for keeping track of how many unique instances are possible. This commit will be chased with some clean-up as I left a lot of internal duplication in the code. I am also unsure if this generates sensible load run against a collector, just that it obeys the protocol by construction. REF SMPTNG-659 Signed-off-by: Brian L. Troutwine <brian.troutwine@datadoghq.com>
Signed-off-by: Brian L. Troutwine <brian.troutwine@datadoghq.com>
This commit avoids non-trivial duplication of the same string pool allocation. Signed-off-by: Brian L. Troutwine <brian.troutwine@datadoghq.com>
Signed-off-by: Brian L. Troutwine <brian.troutwine@datadoghq.com>
9293145 to
ee13a5a
Compare
Signed-off-by: Brian L. Troutwine <brian.troutwine@datadoghq.com>
ee13a5a to
db2e90d
Compare
|
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.
devflow unqueued this merge request: It did not become mergeable within the expected time |
| None | ||
| }; | ||
|
|
||
| let total_scopes = self.scopes_per_resource.sample(rng); |
There was a problem hiding this comment.
if resource is None, then we still generate scope metrics. Is this intentional? The naming of scopes_per_resource makes me question if this is correct (ie, if we have a no resource, then there should be no scopes)
| Ok(v1::ScopeMetrics { | ||
| scope: Some(instrumentation_scope), | ||
| metrics, | ||
| schema_url: String::new(), // 0-sized alloc |
There was a problem hiding this comment.
what is a zero-sized alloc? Asking more from a curiosity of how rust handles this
scottopell
left a comment
There was a problem hiding this comment.
looks good overall, a few thoughts in-line, but approving as they may be addressed upstack

What does this PR do?
Generate OTel metrics with context limits
This commit allows users to configure an otel metrics payload that
has a fixed number of 'contexts' to reuse the term from dogstatsd.
This is done by setting a lot of fiddly knobs and the user is
responsible for keeping track of how many unique instances are
possible.
This commit will be chased with some clean-up as I left a lot of
internal duplication in the code. I am also unsure if this generates
sensible load run against a collector, just that it obeys the
protocol by construction.
REF SMPTNG-659