📓 Summary
The LogExplorer component that the log_explorer plugin exports currently inherits the URL state synchronization from Discover. In order to make it reusable in different UIs we want to prevent it from modifying the URL so the consumer has control over that.
✔️ Acceptance criteria
- The
LogExplorer component doesn't interact with the URL in any way.
- It exposes its state such that it can be initialized and reacted-to by the consuming app.
- There is a new Observability Log Explorer state machine that handles initialisation
- The Observability Log Explorer app registered by
observability_log_explorer synchronizes the necessary parts of the state to the URL, such that...
- a page reload restores these parts of the state.
- it can be migrated as the schema changes.
Please see #165255 (comment) for more specific implementation details.
💡 Implementation hints
- Maybe versioning the url state would help in managing url schema migrations?
📓 Summary
The
LogExplorercomponent that thelog_explorerplugin exports currently inherits the URL state synchronization from Discover. In order to make it reusable in different UIs we want to prevent it from modifying the URL so the consumer has control over that.✔️ Acceptance criteria
LogExplorercomponent doesn't interact with the URL in any way.observability_log_explorersynchronizes the necessary parts of the state to the URL, such that...Please see #165255 (comment) for more specific implementation details.
💡 Implementation hints