Add basic Opensearch telemetry to Electron App #9730
Comments
|
Refinement notes:
|
farmaazon
changed the title
|
Paweł Grabarz reports a new STANDUP for the provided date (2024-05-06): Progress: Early proof of concept implementation for sending events from GUI through Cloud API. It should be finished by 2024-05-13. |
|
Paweł Grabarz reports a new STANDUP for the provided date (2024-05-07): Progress: Fixed GUI double-initialization to be able to send project opening events correctly. Added event logger implementation to dashboard and used it to mirror GA app open/close events. It should be finished by 2024-05-13. |
|
Paweł Grabarz reports a new STANDUP for the provided date (2024-05-08): Progress: Refactored GUI side event logging to use dashboard backend implementation, noticed problems with access tokens not being refreshed. It should be finished by 2024-05-13. |
farmaazon
removed
the
s-info-needed
…eact component. (#9951) fixes #9730 Added a `logEvent` method to remote backend implementation in dashboard. Added an always-present remote backend instance that can be used for logging even when running a local project (intentional behavior). # Important Notes Because the backend implementation requires access to always fresh session token, the logger needs to be periodically updated on GUI side, so it can continue to function. To accomplish that, I simplified the app loading logic to treat GUI as an ordinary react component, so its props can be updated with normal react rendering flow. That refactor also removed the dynamic GUI asset loading code that was only needed for Rust GUI.
github-project-automation
bot
moved this from 👁️ Code review
to 🟢 Accepted
in Issues Board
|
Paweł Grabarz reports a new 🔴 DELAY for the provided date (2024-06-10): Summary: There is 14 days delay in implementation of the Add basic Opensearch telemetry to Electron App (#9730) task. Delay Cause: Complications with sharing session data and cloud backend querying code between GUI and dashboard due to very janky dynamic app loading mechanism, which had to be refactored. |
|
Paweł Grabarz reports a new STANDUP for the provided date (2024-05-09): Progress: Refactoring GUI loading code in dashboard to use vue-in-react component rendering, so dynamic props can be passed down. It should be finished by 2024-05-27. |
|
Paweł Grabarz reports a new STANDUP for the provided date (2024-05-10): Progress: Continuing GUI loading refactor. It should be finished by 2024-05-27. |
|
Paweł Grabarz reports a new STANDUP for the provided date (2024-05-13): Progress: Successfully loaded GUI in react as component, fixed GUI double-initialization bug. Currently the bridge requires loading both frameworks synchronously as part of single chunk, which I still plan to fix. It should be finished by 2024-05-27. |
|
Paweł Grabarz reports a new STANDUP for the provided date (2024-05-14): Progress: Removed all pinia usages in GUI to allow using default vue app constructor without any plugins, which simplifies loading sequence and allows splitting vue and react chunks. It should be finished by 2024-05-27. |
|
Paweł Grabarz reports a new STANDUP for the provided date (2024-05-22): Progress: Started addressing review of dashboard changes and fixing numerous linting issues. It should be finished by 2024-05-27. |
|
Paweł Grabarz reports a new STANDUP for the provided date (2024-05-23): Progress: Meeting with engine about visualization updates and reactive cache. Finished addressing review comments for dashboard changes, still working on broken tests. It should be finished by 2024-05-27. |
|
Paweł Grabarz reports a new STANDUP for the provided date (2024-05-24): Progress: Fixed affected dashboard tests, moved GUI root DOM into the dashboard view hierarchy, instead of always rendering in top-level hardcoded element. It should be finished by 2024-05-27. |
Events to track: open/close product/project (4 in total)
The text was updated successfully, but these errors were encountered: