PowerShell error tracking

Automation should save you work, not hide its failures. Use the Sentry PowerShell module to send error reports to Telebugs on your server.

 󱓻 2 3 4 5

󰅶 󰔎 Local time Local time  

  󰤨  󰍛 󰂅

~/hoofnotes ❯ pwsh

~/hoofnotes ❯ Install-Module -Name Sentry -Scope CurrentUser

~/hoofnotes ❯ nvim Sync-Notes.ps1

Import-Module Sentry

Start-Sentry {

# Copy the complete Telebugs DSN, key and path included.

$_.Dsn = 'YOUR_TELEBUGS_DSN'

}

try {

throw 'Hello from Hoof Notes'

} catch {

$_ | Out-Sentry

} finally {

Stop-Sentry

}

~/hoofnotes ❯ ./Sync-Notes.ps1

Hang on, I already use Sentry

Keep Sentry and change its destination to your Telebugs DSN. Your error reports stay on your server. You don’t need a Sentry account.

Does this suit unattended automation?

Yes. A script can report a failure even when nobody is there to read its console. Pipe a caught error to Out-Sentry to keep a report in Telebugs.

Will every failed command throw an exception?

Not necessarily. PowerShell distinguishes terminating and non-terminating errors. Your script controls which failures to report; the SDK doesn’t turn every warning into an exception.