You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This view doesn't look very nice. The column headers are all collapsed with ellipses, the match expression is just text with no Topology component to visualize what is matched (#376), and editing any Rule is a manual affair by downloading the Rule as JSON, editing it with some external text editor, and re-uploading the edited JSON (and manually stripping out any fields like the id).
A cleaned up and simplified table view that looks more like the Recordings tables would be good. The event specifier, max age, max size, and archival properties can be rendered as label key-values instead of table columns. This way, anything unset/left default (like 0 second max age) can be omitted. These can also be laid out according to available space in the view, potentially stacking vertically as well, so that the space is not simply divided in only the horizontal direction.
A Topology component for visualizing the match expression selection would be good. The Cryostat backend already does some caching, and CEL expressions should be fairly cheap to evaluate, so performance should not be too heavy of a concern here. At least, the component can be available but hidden under a click/hover to call it up.
Directly editing an existing and enabled Rule would be difficult to manage due to the various side effects, but editing a disabled and cleaned Rule should be no problem. There can be a button to either a) edit an existing Rule if it is currently disabled, or b) create a new rule with an existing Rule's definition as a template, ie starting with the same match expression, event template, archival properties, etc.
The text was updated successfully, but these errors were encountered:
This view doesn't look very nice. The column headers are all collapsed with ellipses, the match expression is just text with no Topology component to visualize what is matched (#376), and editing any Rule is a manual affair by downloading the Rule as JSON, editing it with some external text editor, and re-uploading the edited JSON (and manually stripping out any fields like the
id
).The text was updated successfully, but these errors were encountered: