Format, include, exclude, customize the headers and generate log

[ericfran]

Hi,
maybe I didn't search well for the info, but is is possible to:

• set a specific format for the log genarted line (destiantion to logfile, ...) as on the screen only the message is displayed when as with this :
  Set-PSFLoggingProvider -Name console -Enabled $true -Style '%Message%'
  Write-PSFMessage -Message 'Some text'

it displays : Some text

So is it possible to have the same when the provider is to a logfile ?
Can we set for example date, and messages or message only ?

regards,

[FriedrichWeinmann]

Heya Eric,
you sure can*

Basically, you can define the properties on the message object you want (and the order you want them in).
What you can't do, is change the format. So if you configure a logfile as CSV, you get a CSV file. Maybe one with only single column - message - but it will be a valid CSV.

Anyway, the parameter you are looking for is -Headers

[ericfran]

Hi,
Yes I found it by looking to members ✌️
And I could set the required column.
The only issue is that when I put the %message% it is between double-quotes 😕, can this be configured ? Be able to set or set none around message or other headers should be great, possible ?
Regards

[FriedrichWeinmann]

The current implementation does not support removing the quotes - that's part of how PowerShell converts to CSV and part of that limit I mentioned.
That said, it would be a doable update.
There is a reason the logfile provider does not at this time support a free log format style: I did not want to encourage people to use a non-structured format for their logging, rather than one that is easily readable not just for humans, but also for scripts (to facilitate automated processing of logs).
That said, it's not really something I am adamant about - the audience has shifted and there is value in being able to log into a server and be able to scan the logs in a plain notepad without having to first in bring tools or use PowerShell.

Consider it queued for the next release. Probably as a new format for the logfile provider.

[ericfran]

Hi,ThanksI like a lot of features of the tool, was little look by my unknown of setting like header to set them, and then solve it and then saw the “” ‘concern’ ( mine  😉) and understand your approach and purpose of it.Thanks a lotRegardsOn 11 Jan 2025, at 23:08, Friedrich Weinmann ***@***.***> wrote: The current implementation does not support removing the quotes - that's part of how PowerShell converts to CSV and part of that limit I mentioned. That said, it would be a doable update. There is a reason the logfile provider does not at this time support a free log format style: I did not want to encourage people to use a non-structured format for their logging, rather than one that is easily readable not just for humans, but also for scripts (to facilitate automated processing of logs). That said, it's not really something I am adamant about - the audience has shifted and there is value in being able to log into a server and be able to scan the logs in a plain notepad without having to first in bring tools or use PowerShell. Consider it queued for the next release. Probably as a new format for the logfile provider. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>