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
It should be visible what went wrong, what went good. RIght now it's only this table and another Warning when date ranges is too wide for the event logs.
The text was updated successfully, but these errors were encountered:
The main problem is knowing whether we have that information to include or not. I believe we need to modify PSEventViewer which by itself needs a rewrite (to include different methods of getting information) to output more information what it actually managed to scan, what failed and so on. It's quite silent on what it does, what logs did return events, what logs failed for some reason etc.
The table you're showing is actually filled out by second call direct to event logs, not thru PSEventViewer. It's possible this calls goes thru, yet PSEventViewer calls won't. This table you're showing is only verification of what logs actually store at the moment. And I don't think it even checks all logs. Probably it should be expanded (or different Table should be built) with information from all logs that are about to be scanned for events, including files, forwarders and so on.
I would say this issue is a low priority if anything.
It should be visible what went wrong, what went good. RIght now it's only this table and another Warning when date ranges is too wide for the event logs.
The text was updated successfully, but these errors were encountered: