[
https://issues.apache.org/jira/browse/FLINK-14332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aljoscha Krettek closed FLINK-14332.
------------------------------------
Resolution: Won't Do
Hi [~lukesun],
I'm very sorry about the hassle with this feature but the Flink community added
[https://flink-packages.org/] exactly for such cases. We first want to add
integrations with external projects there and possibly move them to Flink
proper when there is huge community demand.
This is, for example, the entry for the DogStatsD reporter:
[https://flink-packages.org/packages/dogstatsd-metrics-reporter]. I suggest to
similarly add the SignalFX reporter there. I'm happy to help with the process
for this or get the right people ([~rmetzger]) involved.
> add flink-metrics-signalfx to flink-metrics
> -------------------------------------------
>
> Key: FLINK-14332
> URL: https://issues.apache.org/jira/browse/FLINK-14332
> Project: Flink
> Issue Type: New Feature
> Components: Runtime / Metrics
> Reporter: Luke Sun
> Assignee: Luke Sun
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> To support the [SignalFX|[https://www.signalfx.com/]] API and library
> dependencies:
> * com.signalfx.public:signalfx-java
> * com.signalfx.public:signalfx-codahale
> and add shaded package because io.dropwizard.metrics:metrics-core dependency
> is not equal to flink-metrics-dropwizard.
>
> flink-conf.yaml
> {code:java}
> metrics.reporter.signalfx.class:
> org.apache.flink.metrics.signalfx.ScheduledSignalFXReporter
> metrics.reporter.signalfx.interval: 60 SECONDS
> metrics.reporter.signalfx.token: xxx
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
