Hi Anchit, That last bit is very interesting - the fact that it works fine with subtasks <= 30. It could be that either Influx or Grafana are not able to keep up with the data being produced. I would guess that the culprit is Grafana if looking at any particular subtask index works fine and only the full aggregation shows issues. I'm not familiar enough with Grafana to know which parts of the queries are "pushed down" to the database and which are done in Grafana. This might also very by backend database.
Anecdotally, I've also seen scenarios using Grafana and Influx together where the system seems to get overwhelmed fairly easily.. I suspect the Graphite/Grafana combo would work a lot better in production setups. This might be relevant: https://github.com/grafana/grafana/issues/2634 -Jamie On Tue, Nov 1, 2016 at 5:48 PM, Anchit Jatana <development.anc...@gmail.com> wrote: > I've set the metric reporting frequency to InfluxDB as 10s. In the > screenshot, I'm using Grafana query interval of 1s. I've tried 10s and more > too, the graph shape changes a bit but the incorrect negative values are > still plotted(makes no difference). > > Something to add: If the subtasks are less than equal to 30, the same query > yields correct results. For subtask index > 30 (for my case being 50) it > plots junk negative and poistive values. > > Regards, > Anchit > > > > -- > View this message in context: http://apache-flink-user- > mailing-list-archive.2336050.n4.nabble.com/Flink-Metrics- > InfluxDB-Grafana-Help-with-query-influxDB-query-for- > Grafana-to-plot-numRecordsIn-numRen-tp9775p9819.html > Sent from the Apache Flink User Mailing List archive. mailing list archive > at Nabble.com. > -- Jamie Grier data Artisans, Director of Applications Engineering @jamiegrier <https://twitter.com/jamiegrier> ja...@data-artisans.com
