spiffe/spire
Fix the "expiring" and "outdated" metrics emitted during entry sync to be accurate across the whole cache
Offen
#2.437 geöffnet am 03.08.2021
help wantedpriority/backlog
Repository-Metriken
- Stars
- (2.443 Sterne)
- PR-Merge-Metriken
- (PR-Metriken ausstehend)
Beschreibung
// TODO: this values are not real, we may remove
if expiring > 0 {
telemetry_agent.AddCacheManagerExpiredSVIDsSample(m.c.Metrics, float32(expiring))
m.c.Log.WithField(telemetry.ExpiringSVIDs, expiring).Debug("Updating expiring SVIDs in cache")
}
if outdated > 0 {
telemetry_agent.AddCacheManagerOutdatedSVIDsSample(m.c.Metrics, float32(outdated))
m.c.Log.WithField(telemetry.OutdatedSVIDs, outdated).Debug("Updating SVIDs with outdated attributes in cache")
}
It's not clear what is meant by "[these] values are not real" and why (I'm assuming) the metric blocks may be removed?
- If this logic or similar may be removed, let's go ahead and remove it for this issue
- If removal can't be done yet, let's update that comment to be more specific, and add a github issue number tracking removal
- If the removal can't or is not foreseen as ever removable, let's get rid of the comment