[
https://issues.apache.org/jira/browse/FLINK-16611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17093993#comment-17093993
]
Stephen Whelan commented on FLINK-16611:
----------------------------------------
[~chesnay] I share the same concern especially since its not just the metrics
but tags as well. The more tags you have, the less metrics you will be able to
batch together.
We could allow the user to set the value in `datadog.conf` so they can control
it if the default value doesn't work for them.
{code:java}
int max_metrics_per_request;
public void open(MetricConfig config) {
...
max_metrics_per_request = config.getInteger(MAX_METRICS_PER_REQUEST, 100);
}
{code}
Alternatively, keeping track of the total request length as you iterate through
the metrics seems aggressive. Though more accurate.
> Datadog reporter should chunk large reports
> -------------------------------------------
>
> Key: FLINK-16611
> URL: https://issues.apache.org/jira/browse/FLINK-16611
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Metrics
> Affects Versions: 1.9.0
> Reporter: Chesnay Schepler
> Assignee: Stephen Whelan
> Priority: Major
>
> Datadog has a maximum size for reports that it accepts.
> If the report exceeds this size it is simply rejected, rendering the reporter
> unusable.
> We should investigate what this size limit is, and split the report into
> multiple chunks.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
