Display service id along with/instead of consuming application

[AlexanderYastrebov]

As an event owner
I want to know service id of consumer
So it is possible to configure authorization

Authorization configuration requires consumer service id while nakadi ui displays application name supplied by consumer which may be different from service id.

[SergKam]

If I understand correctly, you are talking about owning_application in a subscription.
https://nakadi.io/manual.html#definition_Subscription*owning_application
Because "low-level" consumers shown are taken form auth token.
There are several problems with a subscription that cannot be solved on UI level.

• This parameter provided by subscription creator and not validated by Nakadi.
• Even more, the "sub" in auth token used to read from subscription can be different from owning_application
• Even more, it can be several applications reading from one subscription.
  All this can be implemented only on Nakadi server side.

(Zalando specific workaround)
The only reliable method of finding readers for a subscription (for adding them to authz config) is to
look at the zmon graph of subscription.

The graph a bit brocken right now, you need manualy change nakadi-live to nakadi-live-consumption at the top.

but then you will see the real name of consuming app for authz.

[whiskeysierra]

Even more, the "sub" in auth token used to read from subscription can be different from owning_application

Isn't that exactly the problem?