You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As "SRE" I want "a functionality" So that "i can monitor multiple K8up deployed on many kubernetes which send metrics to one pushgateway and be able to identify each backup job easily with the name of the cluster. In fact, some Kubernetes clusters may be backing up the same configurations and the same namespaces, so the metrics sent to pushgateway will be overwritten one after the other. By using a clusterName label identifying the Kubernetes cluster, we can identify each of the clusters and therefore have a time series dedicated to each K8UP environment on each of the clusters."
Context
We use K8up on multiple clusters. These multiple clusters perform backups of namespaces with the same name. All the metrics are sent in the same pushgateway.
As the metrics have the same labels, we cannot have a detailed overview by cluster. This is the way K8UP currently works, which does not allow metric labels to be overloaded. This PR makes it possible to add a clusterName label per Kubernetes cluster.
So in pushgateway we have backup metrics per Kubernetes cluster and per namespace, which improves monitoring of the execution of backups per Kubernetes cluster.
Out of Scope
No response
Further links
No response
Acceptance Criteria
No response
Implementation Ideas
No response
The text was updated successfully, but these errors were encountered:
Summary
As "SRE"
I want "a functionality"
So that "i can monitor multiple K8up deployed on many kubernetes which send metrics to one pushgateway and be able to identify each backup job easily with the name of the cluster. In fact, some Kubernetes clusters may be backing up the same configurations and the same namespaces, so the metrics sent to pushgateway will be overwritten one after the other. By using a clusterName label identifying the Kubernetes cluster, we can identify each of the clusters and therefore have a time series dedicated to each K8UP environment on each of the clusters."
Context
We use K8up on multiple clusters. These multiple clusters perform backups of namespaces with the same name. All the metrics are sent in the same pushgateway.
As the metrics have the same labels, we cannot have a detailed overview by cluster. This is the way K8UP currently works, which does not allow metric labels to be overloaded. This PR makes it possible to add a clusterName label per Kubernetes cluster.
So in pushgateway we have backup metrics per Kubernetes cluster and per namespace, which improves monitoring of the execution of backups per Kubernetes cluster.
Out of Scope
No response
Further links
No response
Acceptance Criteria
No response
Implementation Ideas
No response
The text was updated successfully, but these errors were encountered: