William Dumont

Moved the publisher interface to the processor/internal pkg. It's not ideal because in the future it would be nice to expand the functionality to other components but that should be...

@djaglowski I like your approach :) Helpers should be used to provide optional features for components that require special behaviors (for example "WithStart", "WithCapabilities" and "WithShutdown"). Forcing all components to...

I would like the extension not to depend on the remotetap processor with the idea to deprecate the remotetap processor once the extension is mature enough. The config for the...

Hey @atoulme @djaglowski @jaronoff97, following the SIG meeting (and a week off), I worked on a 2nd POC. As discussed, this time I implemented this concept in the core repository...

Following @atoulme's comment, I moved the component back to contrib and kept only the changes related to the processor helper in core. @djaglowski @jaronoff97 Here are the new relevant links:...

Hi, I tried it with the following config, and the native histograms are exposed just like they are exposed by my app: ``` receivers: prometheus: config: scrape_configs: - job_name: 'otel-collector'...

Ah you are right, I was missing the scape_protocols, I can reproduce it now, thanks :)

> Can you give an example? I think that if we have an object in the resulting array that doesn't have the key field at all, it may become harder...

Looking at the group_by functionalities used in other languages, I think that it makes sense for the user to choose if the objects with missing keys should be dropped or...

Hi, thanks for opening this issue. I think that you can currently achieve the same result with: `alloy run