You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Yes. Im using TSVB to calculate CPU usage as a percentage but it works for lots of other metrics in an opentelemetry schema.
Im using the opentelemetry operator with a prometheus scraper and using data prepper to send the data to opensearch. My schema looks like this:
It should be easy as calculating the sum of the idle time and divide it by the sum of time in all CPU modes, that should give us the percentage of time.
Same applies to all operations that require performing an aggregation on some fields to perform a mathematical operation in some other fields, this has also happened with calculating IO latency. I need to sum the time that was spent reading from disk and divide that by the operations that were performed.
This isn't an issue when prometheus sends its data to metricbeat like I explain here since metricbeat pushes the metric name as its own field, increasing field count (which is not great).
Describe the solution you'd like
We can either support cross series operations or add another field for metric aggregations where we can add a filter. so that instead of only having Aggregation and Field, we would also have a filter like we do on the Filter Ratio aggregation
Describe alternatives you've considered
We can either support cross series operations or add another field for metric aggregations where we can add a filter.
Cross series operations would be very interesting to see, but I understand that it might be more complicated to implement.
Additional context
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.

Yes. Im using TSVB to calculate CPU usage as a percentage but it works for lots of other metrics in an opentelemetry schema.
Im using the opentelemetry operator with a prometheus scraper and using data prepper to send the data to opensearch. My schema looks like this:
It should be easy as calculating the sum of the idle time and divide it by the sum of time in all CPU modes, that should give us the percentage of time.
Same applies to all operations that require performing an aggregation on some fields to perform a mathematical operation in some other fields, this has also happened with calculating IO latency. I need to sum the time that was spent reading from disk and divide that by the operations that were performed.
This isn't an issue when prometheus sends its data to metricbeat like I explain here since metricbeat pushes the metric name as its own field, increasing field count (which is not great).
Describe the solution you'd like
We can either support cross series operations or add another field for metric aggregations where we can add a filter. so that instead of only having Aggregation and Field, we would also have a filter like we do on the Filter Ratio aggregation
Describe alternatives you've considered
We can either support cross series operations or add another field for metric aggregations where we can add a filter.
Cross series operations would be very interesting to see, but I understand that it might be more complicated to implement.
Additional context
The text was updated successfully, but these errors were encountered: