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
in my case i might have several related, but different things in a stack. say, 5 unknown, different strings. as i resolve one of them, i want to mark that one as resolved or delete it so i know its handled once i push out new code
I can see us adding deletes but not sure it makes sense for mark fixed (we only do it on error events) unless it's the whole stack. When looking at a stack, each stack should be unique so marking one as fixed while all others are not messes with stats and isn't exactly clear what's going on. I think there are better approaches as stated earlier for making stacks unique with custom stacking keys, in the case of log events that have meta data.
On a side note, I can definitely see your use case, just trying to see if it's clear what happens if we were to implement it that way (making only a single event as fixed or hidden), maybe hidden is the way to go?
niemyjski
transferred this issue from exceptionless/Exceptionless.UI
Mar 6, 2023
When drilled into a particular event or error, it would be nice to be able to mark that item in the same way when in the "grid" overview.
Putting the buttons in the upper right with the other nav buttons seems like a good place for them
The text was updated successfully, but these errors were encountered: