Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add means to mark events, errors, etc as handled/fixed or delete them from details view #1279

Open
EricZimmerman opened this issue Jan 26, 2017 · 3 comments

Comments

@EricZimmerman
Copy link

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

@niemyjski
Copy link
Member

So you could directly mark an error event as fixed or delete the event.

Would this just be a one way action, like you wouldn't be able to mark it as unfixed unless you went to the stack?

@EricZimmerman
Copy link
Author

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

@niemyjski
Copy link
Member

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 niemyjski transferred this issue from exceptionless/Exceptionless.UI Mar 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants