[
https://issues.apache.org/jira/browse/BEAM-6930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17122868#comment-17122868
]
Beam JIRA Bot commented on BEAM-6930:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> Wrong log severity in Dataflow logs
> -----------------------------------
>
> Key: BEAM-6930
> URL: https://issues.apache.org/jira/browse/BEAM-6930
> Project: Beam
> Issue Type: Bug
> Components: runner-dataflow
> Environment: SDK version: Apache Beam SDK for Java 2.11.0
> Job type: Streaming
> Reporter: Oleksandr Bushkovskyi
> Priority: P2
> Labels: stale-P2
>
> Hi, I'm not sure if this problem should be posted here, please correct me if
> it belongs to some GCP Dataflow specific issue tracker.
> With a default logger configuration I see info logs as errors in GCP console.
> Logger:
> {code:java}
> <dependency>
> <groupId>org.slf4j</groupId>
> <artifactId>slf4j-simple</artifactId>
> <version>1.7.25</version>
> </dependency>
> {code}
> Logging:
> {code:java}
> private Logger LOG = LoggerFactory.getLogger(MakeAlignmentViaHttpFn.class);
> ...
> LOG.info(String.format("Sending Alignment request (#%s) with %d elements...",
> ...));
> {code}
>
> Appears as "severity: ERROR" in GCP Console, see screenshot:
> [https://user-images.githubusercontent.com/31351436/53070821-10e83f80-352c-11e9-93d2-bffeefaba6b8.png]
>
> referring issue in my project:
> https://github.com/allenday/nanostream-dataflow/issues/58
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
