[10:23:39] <volans>	 lmata et al.: I've a small request for you, as the VO rotation for clinic duty is still not authoritative and can create confusion, for the time being could we do 1) rename the rotation on VO to make explicit it's not used/authoritative and 2) remove it from the "Oncall schedule" Google calendar ? Thoughts?
[12:09:34] <cdanis>	 volans: I can do the latter
[12:10:25] <lmata>	 I’ll add a note to make #1 explicit it’s not in use yet
[12:12:41] <volans>	 thanks both!
[13:58:58] <elukey>	 hello folks
[13:59:52] <elukey>	 I'd need to put in place some prometheus metrics rewrite config for the k8s-mlserve instance, and I am looking for some examples in puppet but so far I have found only label renaming
[14:00:40] <elukey>	 an example of my use case is to rename
[14:00:41] <elukey>	 envoy_cluster_discovery_wmnet_upstream_cx_length_ms_bucket
[14:01:02] <elukey>	 to envoy_cluster_upstream_cx_length_ms_bucket (removing the discovery_wmnet bits)
[14:01:46] <elukey>	 (for some $horror in Istio I cannot easily do it before publishing the metric, this is why I am trying to see if the rewrite is an option) 
[14:21:27] <godog>	 elukey: yeah rewrite is definitely an option, the metric name can be accessed as __name__ label
[14:21:36] <godog>	 the rest works the same really
[14:36:21] <elukey>	 godog: perfect! Is it ok even for k8s instances? (that have auto-discovery bits via apis etc..) ?
[14:37:50] <godog>	 elukey: yeah __name__ is always the metric name