The Data Quality dashboard displays errors when a basePath is configured, preventing indices from being checked.

Kibana/Elasticsearch Stack version:

8.7.0

Steps to reproduce:

1. Configure the following settings in config/kibana.dev.yml

server.basePath: '/foo'
server.publicBaseUrl: 'http://localhost:5601/foo'

2. Start Kibana with yarn start

3. Navigate to http://localhost:5601/ in a new browser tab

Expected result

• The browser is redirected to a login page that includes the configured base path /foo, e.g.

http://localhost:5601/foo/login?next=%2Ffoo%2F

4. Login with the elastic superuser

5. Navigate to Security > Dashboards > Data Quality

Expected results

• The View errors popover button is NOT visible
• Errors are not displayed for any patterns

Actual results

• The View errors popover button is visible
• Errors are displayed for each of the patterns, per the following example text and screenshot:

Indices matching the .alerts-security.alerts-default pattern won't be checked

Errors may occur when pattern or index metadata is temporarily unavailable, or because you don't have the privileges required for access

The following privileges are required to check an index:
monitor or manage
view_index_metadata
read

• The View errors popover, when clicked, displays Not Found errors for each of the patterns, per the examples below: