Pinging code owners:

• processor/interval: @RichieSams @sh0rez @djaglowski

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@genadipost which version are you using?
From what I can see, the processor/intervalprocessor is a part of builder-config.yaml
Could you explain the question in more detail?

I think that's a valid issue with contrib distro:

error decoding 'processors': unknown type: "intervalprocessor" for id: "intervalprocessor" (valid values: [experimental_metricsgeneration metricstransform probabilistic_sampler resource batch attributes filter groupbytrace routing logdedup remotetap sumologic tail_sampling groupbyattrs k8sattributes span memory_limiter cumulativetodelta deltatocumulative deltatorate geoip redaction resourcedetection transform])

I see it's not part of https://github.com/open-telemetry/opentelemetry-collector-releases/blob/main/distributions/otelcol-contrib/manifest.yaml indeed.

Since it's stability is still development I guess code-owners would need to evaluate if this component can make it to beta (not sure if there are specific requirements for components to be included in contrib distro). @RichieSams @sh0rez @djaglowski any plans/thoughts on this?

The alternative would be to build a custom Collector following the steps from https://opentelemetry.io/docs/collector/custom-collector/.

Thanks for pointing it out @ChrsMark. I completely missed that aspect.

@ChrsMark @VihasMakwana I would like aggregate all metrics over 5 minutes. Could i get the same functionality by using Metrics Transform Processor or other processor?

I think it's ok to include in beta

@ChrsMark @VihasMakwana @RichieSams Should I open a ticket?

No, we can use this issue as a tracker. This issue can be assigned to me.
I've been behind trying to finish all my work issues before the end of the quarter. But I can do this change this week