Hi there
When troubleshooting different use cases the common sources of that that we search for, currently is separated and in different folders, organized by the location where that information exists.
It would be useful to have a report that could shown the main useful information that happen in a timeframe that we could set in the
UI grouped by troubleshooting use case.
Authentication Report .txt:
| Time Frame | source | Count | Event Ids | Error Codes | Details |
| 12h00-13h00 | Event Log Lsa | 3 | YYYY, XXXX, | | < event message >
| 12h00 - 13h00 | Event Logs Kerberos | 4| AAAA, BBBB| | < event message >
| 12h00 - 13h00 | FREB Logs | 3 | | 401.2 | Request Summary with URL, App Pool, Authentication
| 12h00 - 13h00 | Http Err | 3 | | 403 | http response message
Crash Reports.txt:
| Time Frame | source | Count | Error Codes |
| 11h00-13h00 | Event Log WAS | 3 | YYYY, XXXX, |
| 11h00 - 13h00 | IIS Logs | 100 | 500 |
Currently we have different sources of information: Event Logs , IIS Logs, Freb Logs, Http Err Logs. For each entry that we find that is a error or warning we could increment the count, collect the Event ID and the Error Code/Status Code.
To not impact the time we take to collect all the data , this reports could be generated only by the person that is troubleshooting the issues. For this it could exist a button that could represent the trigger to generate such reports.
With this information we could easily identify i which time frame we had the main errors that we are looking for depending on the use case, such as Authentication or Crashing.