[
https://issues.apache.org/jira/browse/BEAM-13691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17516951#comment-17516951
]
Beam JIRA Bot commented on BEAM-13691:
--------------------------------------
This issue is assigned but has not received an update in 30 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> insufficient error message on Cloud Logging
> -------------------------------------------
>
> Key: BEAM-13691
> URL: https://issues.apache.org/jira/browse/BEAM-13691
> Project: Beam
> Issue Type: Improvement
> Components: runner-dataflow
> Reporter: Ryan (Jaemun) Jung
> Assignee: Ning
> Priority: P2
> Labels: error_message_improvement, stale-assigned, usability
>
> While using GCP dataflow, the default compute engine service
> account([email protected]) was
> accidentally deleted by another user. All the scheduled Dataflow jobs
> suddenly started failing.
> But with Cloud Logging messages, it's not possible to figure out the reason
> because the error message on Cloud Logging only shows general error messages:
> ```
> apache_beam.runners.dataflow.dataflow_runner.DataflowRuntimeException:
> Dataflow pipeline failed. State: FAILED, Error:
> Error processing pipeline.
> ```
> While the logs in the internal logging system clearly indicates
> as:`not_found: Account deleted`
> If it's possible to offer detailed information via Cloud Logging, it will
> allow the users to troubleshoot by themselves.
> Please let me know if there's any further information needed.
> (Creating a Beam ticket because I was guided that it's a Beam related feature
> than Dataflow)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
