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
Just a reminder: The purpose of this issue is to ensure that we have some mechanism to de-duplicate telemetry data for multiple deployments on a single cluster. For instance, a cluster may have more than one deployment of the KIC, or may have both the Operator and a KIC reporting the same metrics for the cluster. However this is done (and it might simply just be a matter of how we report to splunk, and "last update wins") we just need to ensure that we're not counting any duplicate data.
The text was updated successfully, but these errors were encountered:
Just a reminder: The purpose of this issue is to ensure that we have some mechanism to de-duplicate telemetry data for multiple deployments on a single cluster. For instance, a cluster may have more than one deployment of the KIC, or may have both the Operator and a KIC reporting the same metrics for the cluster. However this is done (and it might simply just be a matter of how we report to splunk, and "last update wins") we just need to ensure that we're not counting any duplicate data.
The text was updated successfully, but these errors were encountered: