Andrey Novikov

Right now it is not possible to suppress export of some arbitrary metrics. All netrics collected in code running inside Sidekiq worker process, will be collected and exposed by yabeda-prometheus...

No, there is no way to do that currently. You can only disable the whole “Global cluster-wide metrics” group with `collect_cluster_metrics` setting. But why do you need that? I still...

Transferred this issue to main yabeda repo as it's should be fixed there. Most probably we would like to support this metrics filtering in future.

Wow. Thanks a lot for the pull request! Can you please tell a bit more why you're using standalone process for exporter? Also some quick note to README about that...

Hey @botimer. Sorry for the late reply (2022 is a little bit tough year). I refreshed your pull request in [phased-restart](https://github.com/yabeda-rb/yabeda-puma-plugin/tree/phased-restart) branch in this yabeda repo, feel free to pull...

Thanks a lot for your contribution! Released in [0.7.0](https://github.com/yabeda-rb/yabeda-puma-plugin/releases/tag/v0.7.0)

Thank you for contribution! I guess that you're not using Rails, right? Because for Ruby on Rails we have [railtie that auto-configures Yabeda](https://github.com/yabeda-rb/yabeda/blob/ab2be2235253ed6e0d45a4fa97e4decaa32be480/lib/yabeda/railtie.rb). What is your stack? Maybe we can...

That's really weird. It should be auto-configured. Thanks for providing details, I will take a look.

It is not possible at the moment. `Yabeda::Rails.on_controller_action` is a hook to adding measure of _new_ custom metrics and can't limit builtin ones. For now you can fork this gem...

I don't think that it would be useful to subscribe to all possible things from ActiveSupport. But for things that would be useful to many users pull requests are definitely...