8.16.0 Stack Monitoring unable to load pages for Elasticsearch with logsLocator element #199902
Comments
rseldner
added
bug
|
Pinging @elastic/obs-ux-logs-team (Team:obs-ux-logs) |
|
Looks like this was caused by a recent refactoring here: https://github.com/elastic/kibana/pull/190835/files#diff-ad4e42fbe4d2a7a99ec5d52fbf127ded12f0efe02a10e3afa0409b40be1f4bcfR383 The This happened because this file is still JS, so type-checking doesn't work. |
|
Thanks @flash1293 for digging this one out, but this seems to only happen if the Observability / Logs feature is enabled, which doesn't seem to be the default when spinning up a cluster and picking the "Search" onboarding flow.
|
|
@consulthys For cloud that's right, it is the default for on-prem though because on-prem is using the classic nav which enables the log stream app by default. |
|
@flash1293 but if I'm not mistaken, that feature can be disabled both in cloud and on-prem. |
|
@consulthys Absolutely right on all counts, just highlighting that it's broken by default on on-prem for sufficiently privileged users. |
|
Just want to validate something regarding log views and the fix for this. Ideally what we want to do is use Currently Stack Monitoring relies on a log view called Log Views are being deprecated soon (along with the log stream etc). The centralised log sources advanced setting has taken it's place. The default for this setting does contain Are we okay using the logs locator as it stands right now? (so, by default this wouldn't include the CCS prefix, but users could update their setting). We do also have a locator that can use a Data View ID, but this would have to be persisted in some way (plugin setup etc). |
|
@Kerry350 Can't we link to Discover using an ad-hoc data view with |
Fresh version of #199995 Known issues of 8.16.0 - #199902 - #199892 - #199891 FYI @paulb-elastic, @consulthys, @vinaychandrasekhar Paul suggested to involve @lcawl & @colleenmcginnis I would invite the owners of those issues to expand/edit the proposed text and add workarounds if any --------- Co-authored-by: Luca Belluccini <[email protected]>
Fresh version of elastic#199995 Known issues of 8.16.0 - elastic#199902 - elastic#199892 - elastic#199891 FYI @paulb-elastic, @consulthys, @vinaychandrasekhar Paul suggested to involve @lcawl & @colleenmcginnis I would invite the owners of those issues to expand/edit the proposed text and add workarounds if any --------- Co-authored-by: Luca Belluccini <[email protected]> (cherry picked from commit 20e023b)
Fresh version of elastic#199995 Known issues of 8.16.0 - elastic#199902 - elastic#199892 - elastic#199891 FYI @paulb-elastic, @consulthys, @vinaychandrasekhar Paul suggested to involve @lcawl & @colleenmcginnis I would invite the owners of those issues to expand/edit the proposed text and add workarounds if any --------- Co-authored-by: Luca Belluccini <[email protected]> (cherry picked from commit 20e023b)
Kibana version:
8.16.0
Elasticsearch version:
8.16.0
Original install method (e.g. download page, yum, from source, etc.):
Elastic Cloud
Describe the bug:
Stack monitoring UI errors when attempting to view Elasticsearch metrics
Kibana and Integrations Server are unaffected
Steps to reproduce:
Screenshots (if relevant):
Errors in browser console (if relevant):
Full Error text
Provide logs and/or server output (if relevant):
Any additional context:
The text was updated successfully, but these errors were encountered: