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.
It's frustrating when I don't want to have all the logs for errors, warnings, verbose, etc. comingled together in a single file
Describe the solution you'd like
I'd like the ability to specify different log files for different write events. Something like a flag to Set-LogPath that allows the command to only affect the logged events related to a specific log facility. For example:
This would allow for more specialized use cases for log files, e.g. some logs (error & debug) are only visible to admins, whereas other logs are visible to anyone, all using the log location and file system permissions.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
It's frustrating when I don't want to have all the logs for errors, warnings, verbose, etc. comingled together in a single file
Describe the solution you'd like
I'd like the ability to specify different log files for different write events. Something like a flag to
Set-LogPath
that allows the command to only affect the logged events related to a specific log facility. For example:This would allow for more specialized use cases for log files, e.g. some logs (error & debug) are only visible to admins, whereas other logs are visible to anyone, all using the log location and file system permissions.
The text was updated successfully, but these errors were encountered: