馃摀 Summary
In the log stream page, there used to be an action for each row to view relevant logs in context. This context could include surrounding logs from the same file, host or cloud container and it used container.id, log.file.path and host.name fields.
Action menu and "View in Context" modal
Given the log stream page is now deprecated, we have lost this feature as well.
But discover already offers in the DocViewer Flyout, an option to view Surrounding Documents.
We should leverage that logic and re-create view logs in context, a link which would appear right next to Surrounding docs and when clicked, will navigate the user to surrounding docs page, but with different context. It would carry over all the resource level filters of the document and activate them by default.
鉁旓笍 Acceptance Criteria
Design
Filters should stay enabled instead of disabled like in Surrounding docs

New action

馃摀 Summary
In the log stream page, there used to be an action for each row to view relevant logs in context. This context could include surrounding logs from the same file, host or cloud container and it used
container.id,log.file.pathandhost.namefields.Action menu and "View in Context" modal
Given the log stream page is now deprecated, we have lost this feature as well.
But discover already offers in the DocViewer Flyout, an option to view
Surrounding Documents.We should leverage that logic and re-create
view logs in context, a link which would appear right next toSurrounding docsand when clicked, will navigate the user to surrounding docs page, but with different context. It would carry over all the resource level filters of the document and activate them by default.鉁旓笍 Acceptance Criteria
Surrounding DocscalledView logs in Contextresourcefields and activate them as filters for the last 15 minsDesign
Filters should stay enabled instead of disabled like in Surrounding docs
New action