Corrected the above expression by fixing node_disk_write_read_seconds_total to node_disk_write_time_seconds_total:- (rate( node_disk_read_time_seconds_total [5m]) + rate(node_disk_write_time_seconds_total[5m]))/(rate(node_disk_reads_completed_total[5m]) + rate(node_disk_writes_completed_total[5m])) > <Some integer value>
On Tuesday, September 15, 2020 at 11:31:43 AM UTC-7 rsch...@gmail.com wrote: > Thanks for quick response. Few clarifications:- > 1) Is below calculation is right to get equivalent of "system.io.await" ? > (rate( node_disk_read_time_seconds_total [5m]) + > rate(node_disk_read_time_seconds_total[5m]))/(rate(node_disk_reads_completed_total[5m]) > > + rate(node_disk_writes_completed_total[5m])) > <Some integer value> > > 2) If prometheus server has to perform this calculation let say every 5 > minutes, will this cause CPU load if there are many such alerts for > different environments firing at the same time? Is there any better > alternative to this? > > > > On Monday, September 14, 2020 at 10:24:56 PM UTC-7 wp...@pobox.com wrote: > >> You can calculate it from the basic IO metrics Prometheus provided. >> >> Regards. >> >> >> rsch...@gmail.com wrote: >> >> In datadog I used metrics "system.io.await" to create alert on my linux >> instances. What is the equivalent metrics in prometheus? >> >> -- 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/1f8732de-c212-4029-903e-a8c23fd4835en%40googlegroups.com.
