Dagster event logging not configurable through dagster api execute_run

[cdchan]

Summary

As discussed with @OwenKephart:

The dagster api execute_run command captures all Dagster events generated for the run, and then prints them out after the run is complete. This logging to stdout cannot be configured via the run config or through any logging configuration.

dagster/python_modules/dagster/dagster/cli/api.py

Line 67 in f61a89a

click.echo(line)

This can be a problem when:

1. stdout is used as logging. For example, we forward stdout to Datadog as logs.
2. dagster api execute_run command is how various RunLaunchers (like the DockerRunLauncher) launch runs
3. The combination of the two generates a lot of log spam that cannot be controlled or configured. Log spam makes it harder to pick out important or relevant events.

Reproduction

Any run using dagster api execute_run will generate this stdout output

Dagit UI/UX Issue Screenshots

Additional Info about Your Environment

---

Message from the maintainers:

Impacted by this bug? Give it a 👍. We factor engagement into prioritization.