Piotr Rżysko

### Backward incompatible changes Changed the following metrics paths (removed `selective` from the paths): * `consumer.{hostname}.consumers-workload.{kafkaCluster}.selective.rebalance-duration` -> `consumer.{hostname}.consumers-workload.{kafkaCluster}.rebalance-duration` * `consumer.{hostname}.consumers-workload.{kafkaCluster}.selective.all-assignments` -> `consumer.{hostname}.consumers-workload.{kafkaCluster}.all-assignments` * `consumer.{hostname}.consumers-workload.{kafkaCluster}.selective.missing-resources` -> `consumer.{hostname}.consumers-workload.{kafkaCluster}.missing-resources` * `consumer.{hostname}.consumers-workload.{kafkaCluster}.selective.deleted-assignments` -> `consumer.{hostname}.consumers-workload.{kafkaCluster}.deleted-assignments`...

This PR introduces consumer load metrics that will be used by the weighted work balancer. For now, I want to start with one metric: the number of operations per second...

Flaky test: MultipleKafkaTest

2

https://github.com/allegro/hermes/runs/4517349662?check_suite_focus=true ``` pl.allegro.tech.hermes.integration.MultipleKafkaTest: setupEnvironment A MultiException has 5 exceptions. They are: pl.allegro.tech.hermes.common.exception.InternalProcessingException: org.apache.zookeeper.KeeperException$NoNodeException: KeeperErrorCode = NoNode for /hermes/groups java.lang.IllegalArgumentException: While attempting to resolve the dependencies of pl.allegro.tech.hermes.frontend.publishing.handlers.HandlersChainFactory errors were found...

``` Gradle suite > Gradle test > pl.allegro.tech.hermes.integration.auth.FrontendAuthenticationConfigurationTest.shouldAuthenticateUsingBasicAuth FAILED org.junit.ComparisonFailure: expected: but was: at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at pl.allegro.tech.hermes.integration.auth.FrontendAuthenticationConfigurationTest.shouldAuthenticateUsingBasicAuth(FrontendAuthenticationConfigurationTest.java:91) ```

Hermes management has a mechanism used for detecting inconsistencies between data centers (implemented in #1296). We would like to extend this mechanism to not only detect inconsistencies but also repair...

Consider changing current approach to rate limiting for filters

1

Currently, there are two separate rate limiting mechanisms: * Rate limiting for messages filtering * [Rate limiting for messages delivery](https://hermes-pubsub.readthedocs.io/en/latest/user/subscribing/#rate-limiting ) Both share the same configuration (property `Rate limit` from...

Clean up management/console configuration

3

Currently, properties shared by `hermes-management` and `hermes-console` need to be set in two places. An example: * [hermes-management](https://github.com/allegro/hermes/blob/7340b364c2f82642487545026bb95f2865feeb90/hermes-management/src/main/resources/application.yaml#L47) * [hermes-console](https://github.com/allegro/hermes/blob/7340b364c2f82642487545026bb95f2865feeb90/hermes-management/src/main/resources/application.yaml#L61) Since `hermes-management` exposes configuration for the console (see [the ConsoleEndpoint](https://github.com/allegro/hermes/blob/7340b364c2f82642487545026bb95f2865feeb90/hermes-management/src/main/java/pl/allegro/tech/hermes/management/api/ConsoleEndpoint.java#L29))...

Add possibility to skip events

3

Currently, there is tribal knowledge that if someone wants to skip events, they need to order retransmission from a future date. Maybe it would be useful and easier for users...

Add a linter to the project

2

We would like to add a linter to the project. It should be plugged into [the GitHub action that we currently have](https://github.com/allegro/hermes/blob/master/.github/workflows/ci.yml). Also, it would be useful to be able...

### To reproduce While working on #4180, I noticed that: ```sql explain select cab_type, vendor_id, pickup_datetime from trips order by pickup_datetime desc, cab_type desc limit 100; ``` produces the following...