Separate Chrome from openobserve for Dashboard Reports
Subhra264 opened this issue · comments
Which OpenObserve functionalities are relevant/related to the feature request?
No response
Description
Dashboard reports use headless chrome instance to generate the report. So, in order for reports to work, openobserve needs to use chrome. Given the huge amount of external dependencies required for chrome to work in containers, there should be a separate binary for openobserve chrome server.
Proposed solution
Separate chrome server from openobserve.
Alternatives considered
NA