No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

What is the right way to handle "runtime" errors in a pulumi program/stack config/automation session? Right now when there's an exception thrown (through my own code or pulumi failing, config for example) stdout is spammed with unhandled errors `Resource monitor is terminating` and becomes a little tricker to spot the actual isue.

Is this what you're referring to? <https://github.com/pulumi/pulumi/issues/8236>

I'd recommend upvoting the issue and adding a comment. It'll help with prioritization.