Closed wylieconlon closed 3 years ago
Pinging @elastic/kibana-app-services (Team:AppServices)
@wylieconlon I just attempted to reproduce this with the latest on master but I'm not seeing it. Do you still see it?
If you do, log just before the error to see what kind of err object is being passed. Seems like our assumptions of that thing might not be accurate.
Yes, I am still seeing it on the latest master.
On Mon, Jun 28, 2021 at 7:46 PM Matthew Kime @.***> wrote:
@wylieconlon https://github.com/wylieconlon I just attempted to reproduce this with the latest on master but I'm not seeing it. Do you still see it?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/elastic/kibana/issues/103496#issuecomment-870120667, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFCW26KDV5WY6V5NZF3SJLTVECVXANCNFSM47OEV4WQ .
This happens when rollup indices are present. Its because telemetry is being collected on index patterns with the kibana_system user. While the kibana_system user has access uses view_index_metadata
to get the field list of normal indices, it currently needs read
access for rollup indices - https://www.elastic.co/guide/en/elasticsearch/reference/current/rollup-get-rollup-index-caps.html
I just started Kibana locally and I'm seeing many log messages containing this text: