Ideally the consumer group names should be prepended with the service_name as well just for consistency, but renaming the consumer groups will make us loose all the backlog we have in all the topics and not process it. I don't think consistency is important enough to do that. What do you think @mobrovac ?

Another approach how to minimize the damage to normal change prop while making a nice and uniform use of the service_name everywhere is to rename normal ChangeProp service from changeprop to change-prop - this will break logging and metrics, but those dashboards are easily fixable.

In T181291#3785309, @Pchelolo wrote:

Ideally the consumer group names should be prepended with the service_name as well just for consistency, but renaming the consumer groups will make us loose all the backlog we have in all the topics and not process it. I don't think consistency is important enough to do that. What do you think @mobrovac ?

+1. Le'ts go with just retry and error topics for now.

In T181291#3785350, @Pchelolo wrote:

Another approach how to minimize the damage to normal change prop while making a nice and uniform use of the service_name everywhere is to rename normal ChangeProp service from changeprop to change-prop - this will break logging and metrics, but those dashboards are easily fixable.

Euh, actually ChangeProp's name in the production environment is changeprop, not change-prop. In that sense, it would be more correct to change the service name in its config.yamlto changeprop.

Euh, actually ChangeProp's name in the production environment is changeprop, not change-prop. In that sense, it would be more correct to change the service name in its config.yamlto changeprop.

The service name in the config.yaml is already changeprop and that prevents us from using the service name for retry/error topics and consumer group names universally because retry topics are named with change-prop prefix, but more importantly the consumer group names have change-prop prefix. Changing the consumer group names in CP will make us loose some events. It's not a big deal for most of the topics, but it would be an issue for transfusions. Perhaps we can increase transfusion concurrency, get rid of the backlog as much as possible and rename?

Yeah, we'd need to schedule that in such a way so as to switch the names while the backlog is 0.