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
Is your feature request related to a problem? Please describe.
The log parser currently parses a single file.
However, when log rolling is enabled, this unnecessarily limits the ability to view a series of physical (contiguous in time, all part of the same DB session) rolled logs as a single logical log.
Describe the solution you'd like
The user should be able to give the log parser multiple log file names, or a name of a folder where there may be multiple log files.
The log parser should:
Detect the logs (when given a folder name).
Identify those logs that belong to the same db session id
Detect the time-contiguous logs (or groups of logs)
Parse the logs (or every group of logs) as if they were a single lot file
There needs to be a definition of what constitutes contiguous logs (the time difference between 2 logs)
Need to define how to handle multiple logs that are not contiguous or do not belong to the same DB session id.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The log parser currently parses a single file.
However, when log rolling is enabled, this unnecessarily limits the ability to view a series of physical (contiguous in time, all part of the same DB session) rolled logs as a single logical log.
Describe the solution you'd like
The user should be able to give the log parser multiple log file names, or a name of a folder where there may be multiple log files.
The log parser should:
There needs to be a definition of what constitutes contiguous logs (the time difference between 2 logs)
Need to define how to handle multiple logs that are not contiguous or do not belong to the same DB session id.
The text was updated successfully, but these errors were encountered: