That's assuming that I'm correct here, which seems to be the case following the code: https://github.com/prometheus/common/blob/317b7b125e8fddda956d0c9574e5f03f438ed5bc/model/alert.go#L50 -> https://github.com/prometheus/common/blob/317b7b125e8fddda956d0c9574e5f03f438ed5bc/model/labelset.go#L143 -> https://github.com/prometheus/common/blob/317b7b125e8fddda956d0c9574e5f03f438ed5bc/model/signature.go#L56
On Friday, 25 September 2020 at 13:11:30 UTC+1 l.mi...@gmail.com wrote: > Depends what you mean by "unique". > AFAIR fingerprint is computed from alerts labels, so unique means here: a > unique combination of labels. > It's not unique as an "event" - if alert fires, then resolves and then > fires again that both old and newly firing alerts will have same > fingerprint. > > So an alert with same combination of labels should have same fingerprint > for every occurrence of that alert. > On Friday, 25 September 2020 at 12:25:31 UTC+1 baca...@gmail.com wrote: > >> Hi all. >> >> We are interested in organizing alerts in a persistent storage for >> querying them later since Stack is quite unpractical for that. >> >> We were considering using the "fingerprint" as a unique identifier for >> each alert but I've found inconsistent statements on the Internet about its >> uniqueness. >> >> Is the fingerprint unique or to which degree can it be considered unique? >> >> Thanks, >> F. >> > -- 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/7941d247-7fc1-4711-986d-c533077bc69an%40googlegroups.com.
