Open jloleysens opened 1 week ago
Pinging @elastic/kibana-management (Team:Kibana Management)
Pinging @elastic/kibana-core (Team:Core)
@jloleysens Beyond just adding additional locator params, this could be a good use case for the Discover contextual awareness framework (even more so because I see a Logs Explorer link, and it's being deprecated in favour of Discover). It would allow you to register a "profile" in Discover to detect when users are looking at deprecation logs (e.g. by checking the index pattern), then provide extension point implementations to customize the interface, e.g. default state like columns, custom cell renderers and actions, app menu links, and more. It could be a great way to help users migrate off deprecated APIs by providing additional context, links out to alternative APIs, etc. directly in Discover.
You can find more info in our docs, and please shoot us a message in the One Discover channel if you have any questions or want to chat more!
Today when we link to discover from UA:
It renders something like the following Discover:
Can we make this more useful by leveraging the
DiscoverAppLocatorParams
to, by default, set:log.level
,message
,x-opaque-id
,elasticsearch.cluster.name
,elasticsearch.event.category