Hello, I have looked online and I cant find any best practices for filling 
up the description and the summary. from the examples I see that Summary 
should be the shortest (plus the minimum usage of labels). But maybe it is 
an observation bias. 

I am trying to generate some automatic documentation around alerting and 
having a lot of labels makes it as user friendly as reading the yaml file 
directly

Regards

-- 
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/14525699-58bb-4ece-b76a-43ea92878400n%40googlegroups.com.

Reply via email to