I would like to propose to introduce a new binary crate quent-open.
The goal is to let users quickly spawn a quent viewer for their quent telemetry data.
This crate builds the required server and ui components on the fly by bootstrapping a small binary crate and running it. It will also spawn the browser.
Initially it would work with local files (you point it to a directory with telemetry data), but we can support other importer methods (via a trait) to allow users to add additional methods (via a runtime config). For example, if users collect benchmark run results with telemetry data using a remote service, an importer could take a benchmark run and fetch the corresponding telemetry data from the remote service to render locally. The runtime config would capture where quent-open can find the importer.
Initially we would also use the runtime config to map engines to their UiAnalyzer trait implementation. Later we can move that information to be included directly in the exported files or via a sidecar file (see #231), so that quent-open can fetch and build the matching implementation.
Later we can also provide this functionality as library if users want to embed this functionality.
I would like to propose to introduce a new binary crate
quent-open.The goal is to let users quickly spawn a quent viewer for their quent telemetry data.
This crate builds the required server and ui components on the fly by bootstrapping a small binary crate and running it. It will also spawn the browser.
Initially it would work with local files (you point it to a directory with telemetry data), but we can support other importer methods (via a trait) to allow users to add additional methods (via a runtime config). For example, if users collect benchmark run results with telemetry data using a remote service, an importer could take a benchmark run and fetch the corresponding telemetry data from the remote service to render locally. The runtime config would capture where
quent-opencan find the importer.Initially we would also use the runtime config to map engines to their
UiAnalyzertrait implementation. Later we can move that information to be included directly in the exported files or via a sidecar file (see #231), so thatquent-opencan fetch and build the matching implementation.Later we can also provide this functionality as library if users want to embed this functionality.