(I couldn't reopen the previous PR so I've created a new one with my changes on top of the new main branch) Closes #404
Added a filter UI on Exceptions page to filter by Url, Host, Start Date and End Date. I've followed the same UI pattern as the one used on the SQL active/top page filters. These have been features requested at Stack that will be very handy to search for specific exceptions without manipulating the opserver url or search box.
Filter by Url: filters exceptions by Url, wildcards such as * or % can be entered.
Filter by Host: filters exceptions by Host, wildcards such as * or % can be entered.
Filter by Start Date: filters exceptions that were created from Start Date onwards.
Filter by End Date: filters exceptions that were created from End Date backwards.
The picker date format and text is regionalized based on browser/pc settings. The value the picker sends to the controller has always the fixed format of YYYY-MM-DDThh:mm. It also has an option to clear the field.
What I have tested
I've run OpServer locally with a local DB containing test Exceptions data. Tested the following behaviour:
Filter by Url, with and without wildcards
Filter by Host, with and without wildcards
Filter by Start Date
Filter by End Date
Any combination of the above filters, Url + Host, Start Date + End Date, etc.
Load More feature loads more exceptions using the current filters
Changing the Group or Log mantains the current filter values
Summary
(I couldn't reopen the previous PR so I've created a new one with my changes on top of the new main branch) Closes #404
Added a filter UI on Exceptions page to filter by Url, Host, Start Date and End Date. I've followed the same UI pattern as the one used on the SQL active/top page filters. These have been features requested at Stack that will be very handy to search for specific exceptions without manipulating the opserver url or search box.
The picker date format and text is regionalized based on browser/pc settings. The value the picker sends to the controller has always the fixed format of YYYY-MM-DDThh:mm. It also has an option to clear the field.
What I have tested
I've run OpServer locally with a local DB containing test Exceptions data. Tested the following behaviour: