I have thousands of connection errors in Iguana and would like to know if there is a way to bulk delete just those errors rather than deleting them one at a time. I don’t want to use the Clear/Mark Channel Errors option on the Dashboard page because there are errors that I would like to keep.
I am also interested in finding a way to bulk delete errors, or bulk “mark” errors. Is there a way currently, or does it need to be submitted as an enhancement request?
It’s always been possible to bulk mark errors to semi hide them from the dashboard. The errors are not really deleted but are just hidden. Nothing is lost so there is nothing stopping one from exporting the errors into a CSV file and searching through it.
What are the steps for bulk “marking” errors? I can’t find the article in the KB.
You do it from the dashboard.
I’ve attached a screen shot to my last post which shows how to do it from the dashboard.
Got it, thanks. That will clear/mark all errors on a channel. I was wondering if there is a way to search the logs for certain errors, and only mark those. I may want to mark all errors during a specific time range, or only certain types of errors.
No not currently. You can always browse and export the errors even after they have been marked though so the data hasn’t been lost. I have attached a screen shot of the search criteria in the log screen.
I’m familiar with the Search Criteria in the logs. I was hoping that the search criteria could be used to bulk mark errors. Maybe in a future release.
They are good ideas for what we should consider when we re-work the logging system. Thanks for taking the time to give the feedback. The bigger focus for Iguana 6.0 will be on comprehensive overhaul of the source code management functionality:
I think the logging system would be best tackled in similar manner with a comprehensive rethinking of it works making it into something is much better.
Bulk resubmitting of specific messages (without having to reposition the channel, or export and re-import) would be nice too. For example, from the log search, identify certain types of errors/messages and resubmit them all. Additionally, giving the user the option to “mark” those errors upon resubmitting, so that only new errors generated by the reprocessing of the message will be logged as unmarked.
You must be logged in to reply to this topic.
Please don't hesitate to take anonymous feedback survey or leave us a comment.