[
https://issues.apache.org/jira/browse/BEAM-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15895525#comment-15895525
]
Aviem Zur commented on BEAM-1616:
---------------------------------
[~bchambers] you raise interesting questions.
Since pipelines runs on distributed executors and the gauge aggregation is very
optimistic, you won't really get the last value, but one of the last values.
I believe that this type of metric is heavily geared towards unbounded
pipelines meaning it is something you would want to poll every so often, and as
such not getting the exact last value, but around it is not that big of a
problem.
The questions you raised regarding failures are also relevant for existing
metrics types, perhaps a common documentation for all of these is in order?
> Gauge Metric type
> -----------------
>
> Key: BEAM-1616
> URL: https://issues.apache.org/jira/browse/BEAM-1616
> Project: Beam
> Issue Type: Bug
> Components: beam-model, sdk-java-core, sdk-py
> Reporter: Aviem Zur
> Assignee: Ben Chambers
>
> Add support for Gauge metric type to the SDK.
> This will serve to get the last value reported.
> Interface should be along the lines of:
> {code}
> void set(long value);
> {code}
> Compare to
> http://metrics.dropwizard.io/3.1.0/apidocs/com/codahale/metrics/Gauge.html
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
