Created attachment 1430997 [details] Only project.* index is shown on kibana, there is not individual project index Description of problem: Only project.* index is shown on kibana, there is not individual project index, but logs of all project could be found under project.* index Version-Release number of selected component (if applicable): logging-elasticsearch/images/v3.9.27-2 logging-fluentd/images/v3.9.27-2 logging-curator/images/v3.9.27-2 logging-kibana/images/v3.9.27-2 logging-auth-proxy/images/v3.9.27-2 How reproducible: Always Steps to Reproduce: 1. Deploy logging 3.9 and logon kibana 2. 3. Actual results: Only project.* index is shown on kibana, there is not individual project index Expected results: Should have individual project index on kibana Additional info:
Please confirm you are logged in as a cluster admin. This change is intentional as part of [1] to support larger online clusters. I expect for non-admins you should see the pattern per namespace as was previously the case. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1563230
Yes, logged in as a cluster admin only could see project.* index, not the individual project index, use non-admins could see the pattern per namespace as was previously the case. Close it as NOTABUG
There is one corner case, if use one non-admin to create a project and populate logs, we could see index pattern project.<namespace>.<UUID>.<date> in kibana UI, if then make this user to cluster-admin later, both project.* and project.<namespace>.<UUID>.<date> indices could be viewed in kibana UI. Is that expected?
Created attachment 1432477 [details] project.* index and individual project index could be viewed in kibana
It's only expected in that the plugin does not account for this corner case. It makes no effort to modify existing index-patterns so that user customizations are not lost. In this particular case, a non-admin trying to query using the 'project.*' index-pattern will see 403 errors because the are trying to search indices for which they do not have permissions.