[
https://issues.apache.org/jira/browse/FLINK-6013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004222#comment-16004222
]
ASF GitHub Bot commented on FLINK-6013:
---------------------------------------
Github user zentol commented on the issue:
https://github.com/apache/flink/pull/3736
@greghogan My simple answer is that its feature freeze. There has to be
some point in time where new features, regardless of size, stability etc. can't
make it into a release. My understanding is that we decided to make the feature
freeze date this point in time. When something like this is put into place it
naturally follows that some contributions that are ready around the time of the
FF will not be merged. Given that the FF was already delayed by a week,
implicitly giving every contribution a 1 week grace period, I don't see a
reason to make an exception here. It wasn't merged before the FF; it wasn't
merged before the delayed FF, so it's not going into the release.
That's my take on the whole thing.
PS: Me closing this PR was not meant to imply "and that's the end of it". I
just amended the commit before this discussion started and didn't remove it.
> Add Datadog HTTP metrics reporter
> ---------------------------------
>
> Key: FLINK-6013
> URL: https://issues.apache.org/jira/browse/FLINK-6013
> Project: Flink
> Issue Type: Improvement
> Components: Metrics
> Affects Versions: 1.3.0
> Reporter: Bowen Li
> Assignee: Bowen Li
> Priority: Critical
> Fix For: 1.3.0
>
>
> We at OfferUp use Datadog a lot for metrics and dashboards, and I believe a
> lot other companies also do.
> Flink right now only has a StatsD metrics reporter, and users have to set up
> Datadog Agent in order to receive metrics from StatsD and transport them to
> Datadog. We don't like this approach.
> We prefer to have a Datadog metrics reporter directly contacting Datadog http
> endpoint.
> I'll take this ticket myself.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
