[
https://issues.apache.org/jira/browse/BEAM-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16523338#comment-16523338
]
Etienne Chauchot commented on BEAM-4178:
----------------------------------------
IMHO I think it is the good workaround. Indeed, even if metrics pusher pushes
metrics values at a give frequency, if the metric is not yet created (not yet
available in pipeline's MetricsContainerStepMap) there will me not pushed
either.
> Metric doesn't appear until first changed
> -----------------------------------------
>
> Key: BEAM-4178
> URL: https://issues.apache.org/jira/browse/BEAM-4178
> Project: Beam
> Issue Type: Bug
> Components: beam-model, runner-dataflow, sdk-java-core
> Affects Versions: 2.4.0
> Environment: Java, DataflowRunner
> Reporter: Kevin Peterson
> Assignee: Scott Wegner
> Priority: Minor
>
> When defining a counter Metric, I've noticed that the Metric does not show up
> in the Dataflow UI (or stackdriver) until it is first incremented or
> decremented.
> Ideally, some initial value for the metric should be reported when the
> pipeline is started.
> The specific use case I have in mind is setting up a Stackdriver alert for a
> error condition in the pipeline. But because the metric doesn't show up until
> an error actually happens, I can't set the metric up in advance.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
