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

You likely need to use the `--logtostderr` flag too.

Thanks! That helps. Oddly, some of my debug messages are missing from the log... even with `-v9`.

Kind of interesting that the help states `--logtostderr Log to stderr instead of to files`. Any idea where those log files are stored and organized when the `--logtostderr` option is not used?

Ok. I found out what was happening to my missing debug messages - it seems that output on stdout can writeover the same line as the stderr output. So, if the streams are not separated then you are likely to lose some messages :cry:

That is actually surprising. Do you have an example of that?  If you do - would be great to open an issue in github. That doesn’t sound intentional. 

Yea, I can share a snippet of my code and I still have the console output too. For what it is worth, I upgraded to v1.11.0 this morning. I'll likely file an issue tomorrow morning, I was just about to sign off for the evening.

<https://github.com/pulumi/pulumi/issues/3965>