Skip to content

Stateless notification server + viz saving

Raffi Kwankam requested to merge viz-saving into main


The notification server now properly uses the DB.

Triggers are saved to the DB, and when alerts are made those are saved to the DB also (for now alerts are made after creating a new trigger, but this should run via scheduler)

Also, RPC bugfix. It now works with custom non-readonly classes, and therefore List<MyClass>, MyClass[], etc (the fix was very easy and dumb)


Visualizations can be saved to, and loaded from, the database (as VisualizationBlueprints converted to JSON)

Saving happens automatically after creating a graph, and replacing a graph as the user replaces it on the DB

Loading happens once automatically on startup

Merge request reports