Closed kostyaLem closed 1 year ago
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself.
This doesn't look right. These actions do not support avg, min, max etc =(
In that case it is likely no process in Contrib currently fits your needs. Either the transformprocessor or metricstransformprocessor would need updating. Can you provide more in-depth details about how you'd like to collapse scope metrics?
@kostyaLem, how did you get this data in the first place? It seems pretty unusual. Metric datapoints usually have the same timestamp with different attributes. That's what the metrics transform processor expects. But you have different timestamps, so you need time aggregation, which is more like backend responsibility. A collector component doing the time aggregation would require a state with a significant amount of memory allocated to it. We might introduce such component someday, but it's not a priority at this point.
@TylerHelmuth @dmitryax I prepared a small diagram that describes how I imagine it :D
Thx
The diagram doesn't say anything about aggregation type. It can be read as spatial aggregation, which is supported by the metrics transform processor. You need time aggregation over a predefined time window. It'll not be implemented any time soon as it's a backend concern, not data collection. We cannot just support metric objects with a set of different timestamp data points because it solves a very narrow use case. Again, can you let us know what Service you have sending this kind of data?
The .NET service sends application performance metrics every minute (threads, cpu usage, memory and etc.). Ok. How to "reduce" the telemetry input stream using the metrics transform processor?
The .NET service sends application performance metrics every minute (threads, cpu usage, memory and etc.).
Do you use OTel .NET instrumentation?
Ok. How to "reduce" the telemetry input stream using the metrics transform processor?
I don't think the collector has anything to offer to "reduce" the size of such metrics other than drop some of them by name
Do you use OTel .NET instrumentation?
Yes.
I don't think the collector has anything to offer to "reduce" the size of such metrics other than drop some of them by name
Okay. Thanks for taking the time !
Producing less metrics at the source is also an option. The .NET auto-instrumentation supports an env var to disable instrumentation by library.
The instrumentation should allow you to increase the measurements interval to produce less data points
Component(s)
processor/metricstransform, processor/transform
Describe the issue you're reporting
Description:
I have a set of data points for each metric. I looked at all the processors and did not find the right one that would help to aggregate each metric. How to collapse each metric in scopeMetrics.metrics to single values ? Thanks for reading (I don't have Slack so I'm posting here) :D
Config.yaml:
ActualResult:
Want to get:
Singe value using avregare, sum, min or max functions for each metrics in scopeMetrics.