Skip to content

Commit

Permalink
Incorrect Metric reported in MetricsReporter.scala
Browse files Browse the repository at this point in the history
Current implementation for processingRate-total uses wrong metric:
mistakenly uses inputRowsPerSecond instead of processedRowsPerSecond
  • Loading branch information
Taaffy authored Sep 18, 2017
1 parent 3b049ab commit afe083f
Showing 1 changed file with 1 addition and 1 deletion.
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ class MetricsReporter(
// Metric names should not have . in them, so that all the metrics of a query are identified
// together in Ganglia as a single metric group
registerGauge("inputRate-total", () => stream.lastProgress.inputRowsPerSecond)
registerGauge("processingRate-total", () => stream.lastProgress.inputRowsPerSecond)
registerGauge("processingRate-total", () => stream.lastProgress.processedRowsPerSecond)
registerGauge("latency", () => stream.lastProgress.durationMs.get("triggerExecution").longValue())

private def registerGauge[T](name: String, f: () => T)(implicit num: Numeric[T]): Unit = {
Expand Down

0 comments on commit afe083f

Please sign in to comment.