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

<https://www.pulumi.com/docs/reference/cli/pulumi_up/|https://www.pulumi.com/docs/reference/cli/pulumi_up/>
The `--debug` flag is what you're looking for, I think.

That showed me some different debug output, but it still didn’t output my logs…

I’m still looking for an answer to this. It seems like a really simple one - surely someone has used `<http://pulumi.info|pulumi.info>` or `pulumi.debug` for logging?

`<http://pulumi.log.info|pulumi.log.info>` outputs to the console during a preview or up. They're formatted nicely but they're not suitable for use as trace or error logs.

For example, if you use them inside a resource constructor, they appear to the right of the resource during preview and up.

But they're not error logs that you can capture using `pulumi up 2&gt; errors.log`.