Devolutions ForumDevolutions Forum

Something wrong with log settings

Something wrong with log settings

avatar
deroppi 
Product: PowerShell Universal
Version: 5.2.1


My database log target vanished after I changed the level.

“critical” does not exist…


a00d1cb3dfad723476958f5f15b5762334f7f3e3
but it is offered in the GUI


499036c586ac5304b4e38cea759790d4613df31c

499036c586ac5304b4e38cea759790d4613df31c.png

a00d1cb3dfad723476958f5f15b5762334f7f3e3.png

avatar
Adam Driscoll

Recommended Answer

I opened an issue for this. Critical is an invalid value.

github.com/ironmansoftware/powershell-universal
If you navigate to Settings \ Files \ .universal \ logging.ps1, you should be able to adjust the logging level manually.

Adam Driscoll
PowerShell Expert and Developer at Devolutions

1

All Comments (1)

avatar
Adam Driscoll

I opened an issue for this. Critical is an invalid value.

github.com/ironmansoftware/powershell-universal
If you navigate to Settings \ Files \ .universal \ logging.ps1, you should be able to adjust the logging level manually.

Adam Driscoll
PowerShell Expert and Developer at Devolutions

1