You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@beam.apache.org by "Kenneth Knowles (JIRA)" <ji...@apache.org> on 2018/01/19 15:27:00 UTC

[jira] [Updated] (BEAM-3178) Add a Pipeline option that sets desired logging level for logs produced by runners.

     [ https://issues.apache.org/jira/browse/BEAM-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kenneth Knowles updated BEAM-3178:
----------------------------------
    Labels: portability  (was: )

> Add a Pipeline option that sets desired logging level for logs produced by runners.
> -----------------------------------------------------------------------------------
>
>                 Key: BEAM-3178
>                 URL: https://issues.apache.org/jira/browse/BEAM-3178
>             Project: Beam
>          Issue Type: New Feature
>          Components: sdk-java-core, sdk-py-core
>            Reporter: Valentyn Tymofieiev
>            Assignee: Kenneth Knowles
>            Priority: Minor
>              Labels: portability
>
> In some cases BEAM users or runner maintainers may want to increase the logging level produced by the BEAM runners. To make it simpler, SDK should capture a desired logging level in PipelineOptions and pass it on to runners. 
> For comparison, we have instrumentation that captures logging for Java SDK harness[1]. It seems that we should have similar option that captures logging granularity on the runner side. 
> [1] https://github.com/apache/beam/blob/2b4a6b5d5cb455fe73971fde4caa7d1446cd55aa/sdks/java/core/src/main/java/org/apache/beam/sdk/options/SdkHarnessOptions.java#L62



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)