[
https://issues.apache.org/jira/browse/FLINK-7689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-7689:
----------------------------------
Labels: jdbc metrics pull-request-available stale-minor (was: jdbc metrics
pull-request-available)
> Instrument the Flink JDBC sink
> ------------------------------
>
> Key: FLINK-7689
> URL: https://issues.apache.org/jira/browse/FLINK-7689
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Common
> Affects Versions: 1.4.0
> Reporter: Martin Eden
> Priority: Minor
> Labels: jdbc, metrics, pull-request-available, stale-minor
> Original Estimate: 24h
> Time Spent: 10m
> Remaining Estimate: 23h 50m
>
> As confirmed by the Flink community in the following mailing list
> [message|http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/metrics-for-Flink-sinks-td15200.html]
> using off the shelf Flink sinks like the JDBC sink, Redis sink or Cassandra
> sink etc does not expose any sink specific metrics.
> The purpose of this ticket is to add some relevant metrics to the
> JDBCOutputFormat:
> - Meters for when a flush is made.
> - Histograms for the jdbc batch count and batch execution latency.
> These would allow deeper understanding of the runtime behaviour of
> performance critical jobs writing to external databases using this generic
> interface.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
