As a manager of the ODH, I want to know how many users hit the QUOTA boundaries, to better provide selling plans to the customers

[Piiit]

We still miss several log entries to have better stats. The JSON output should follow the tourism API which already provides those stats sufficiently. So that we could have similar dashboards with just copy/pasting some code snippets on Grafana or Kibana.

Kibana Dashboard: https://logs.opendatahub.bz.it/app/dashboards#/view/1c590400-01bb-11eb-9051-29e0c3442a1e

• [x] Add missing log entries, like remote IP, quota, roles etc to Ninja
• [x] Fix: Users without a quota setting, but logged in are automatically "Authenticated Basic" as quota policy
• [x] Update all configs on Keycloak to reflect the new quota and role policies
• [x] Create a Kibana Dashboard
• [x] Some logins do not have an email assigned, investigate that and eventually show the UUID or other fields in the dashboard to identify customers

  Found: It is a service account named service-account-cisma-elaborations which does not have any email assigned, nor login username, because it is just a machine-to-machine account... I add a fake email address service-account-cisma-elaborations@cisma.it to be shown in dashboards.

• [x] The apache proxy does not send the remote ip as x-forwarded-for, fix that
• [x] Adapt the logging output to have it equal as the tourism api

  I decided against the tourism API json output, because with that we would need two different mobility dashboards and logs, because at some point the old fields would not show up anymore, creating statistics would also be hard to do, because we would need to merge them at some point. This needs further investigation and then a separate task.

[Piiit]

@rcavaliere Please have a look into this dashboard... Everything is already on production, so if you like it, we can simply close this issue

FYI @dulvui @RudiThoeni