flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-7009) dogstatsd mode in statsd reporter
Date Tue, 11 Jul 2017 07:26:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-7009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16081812#comment-16081812

ASF GitHub Bot commented on FLINK-7009:

Github user svendx4f commented on the issue:

    Hi all, 
    @dbrinegar , are you still working on this? I started using Datadog for flink a couple
of days ago, then directly wanted to suggest a PR to remove the object ids from metrics names...
only to find you had started working on it already :) 
    I would really like this to be in place, at the moment I edit my datadog dashboard at
every flink or job restart, that will not be an option in production. 
    Anything I can contribute to this PR to help it go forward?

> dogstatsd mode in statsd reporter
> ---------------------------------
>                 Key: FLINK-7009
>                 URL: https://issues.apache.org/jira/browse/FLINK-7009
>             Project: Flink
>          Issue Type: Improvement
>          Components: Metrics
>    Affects Versions: 1.4.0
>         Environment: org.apache.flink.metrics.statsd.StatsDReporter
>            Reporter: David Brinegar
>             Fix For: 1.4.0
> The current statsd reporter can only report a subset of Flink metrics owing to the manner
in which Flink variables are handled, mainly around invalid characters and metrics too long.
 As an option, it would be quite useful to have a stricter dogstatsd compliant output.  Dogstatsd
metrics are tagged, should be less than 200 characters including tag names and values, be
alphanumeric + underbar, delimited by periods.  As a further pragmatic restriction, negative
and other invalid values should be ignored rather than sent to the backend.  These restrictions
play well with a broad set of collectors and time series databases.
> This mode would:
> * convert output to ascii alphanumeric characters with underbar, delimited by periods.
 Runs of invalid characters within a metric segment would be collapsed to a single underbar.
> * report all Flink variables as tags
> * compress overly long segments, say over 50 chars, to a symbolic representation of the
metric name, to preserve the unique metric time series but avoid downstream truncation
> * compress 32 character Flink IDs like tm_id, task_id, job_id, task_attempt_id, to the
first 8 characters, again to preserve enough distinction amongst metrics while trimming up
to 96 characters from the metric
> * remove object references from names, such as the instance hash id of the serializer
> * drop negative or invalid numeric values such as "n/a", "-1" which is used for unknowns
like JVM.Memory.NonHeap.Max, and "-9223372036854775808" which is used for unknowns like currentLowWaterMark
> With these in place, it becomes quite reasonable to support LatencyGauge metrics as well.
> One idea for symbolic compression is to take the first 10 valid characters plus a hash
of the long name.  For example, a value like this operator_name:
> {code:java}
> TriggerWindow(TumblingProcessingTimeWindows(5000), ReducingStateDescriptor{serializer=org.apache.flink.api.java.typeutils.runtime.PojoSerializer@f3395ffa,
ProcessingTimeTrigger(), WindowedStream.reduce(WindowedStream.java-301))
> {code}
> would first drop the instance references.  The stable version would be:
> {code:java}
> TriggerWindow(TumblingProcessingTimeWindows(5000), ReducingStateDescriptor{serializer=org.apache.flink.api.java.typeutils.runtime.PojoSerializer,
reduceFunction=org.apache.flink.streaming.examples.socket.SocketWindowWordCount$1}, ProcessingTimeTrigger(),
> {code}
> and then the compressed name would be the first ten valid characters plus the hash of
the stable string:
> {code}
> TriggerWin_d8c007da
> {code}
> This is just one way of dealing with unruly default names, the main point would be to
preserve the metrics so they are valid, avoid truncation, and can be aggregated along other
dimensions even if this particular dimension is hard to parse after the compression.

This message was sent by Atlassian JIRA

View raw message