I described in detailed the problem
in https://github.com/prometheus/prometheus/issues/8001 (which was closed
but see details there)
In short the default install from helm has 1 minute scrape which makes the
istio and kiali dashboards "empty" because they use [1m] in the query
Given a 1m scrape means the data is on average 30s old, I don't think
returning "no data" for queries is a very useful behavior, even if I was
scraping every 10 minutes I expect that any resolution I ask would be
extrapolated - but I guess I have the wrong expectations?
Can someone talk me through why "no data" is the right answer for [1m]
while there is data for [90s]
sample query:
sum(rate(istio_tcp_received_bytes_total{reporter="source"}[90s])) by
(destination_workload, destination_workload_namespace, destination_service)
Thanks a lot
Laurent
--
You received this message because you are subscribed to the Google Groups
"Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to prometheus-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/prometheus-users/cd723026-4634-4b89-b633-47c9d8543e37n%40googlegroups.com.
