First of all, thanks for your answers. > https://www.robustperception.io/using-time-series-as-alert-thresholds
I do not understand how that article can help me. If I understood that correctly, it seems to describe a way for different teams to define their own thresholds. But I have no teams, I am a lone fighter. 8-) I just want to assign different thresholds to different disks. > [...] > You obviously don't want the alert firing forever, so what do you do? > Move the threshold to 91%, and repeat the whole thing later? Say I have 3 thresholds: - only 100 MB left free - 90 % full - 95 % full If a disk hits 90 %, I may then decide to move it to the 95 % group. Initially, I thought I could create one alarm per threshold, and each alarm would only trigger for their particular threshold label. I could then add a label to each computer, in order to place all of its disks in one of the alarm thresholds. But later on I realised that I would need to add a label to each disk (to each disk metric). For example, some computers some several disks. The thresholds for the system disks (where the OS is installed) are generally different from the thresholds for user data disks. At that point I thought I could add the corresponding threshold label to each separate disk, but that's what I am struggling to do in Prometheus. Do I have to resort to some "metric_relabel_configs" magic? Could you provide an example on how to do that? Best regards, rdiez -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/71e0913f-b9b5-4fc8-9b41-223aa8bcf8a9n%40googlegroups.com.
