Bug 1473760

Summary:	Using hawkular-tenant and curling the hawkular-metrics endpoint provides pods that aren't necessarily running
Product:	OpenShift Container Platform	Reporter:	Eric Jones <erjones>
Component:	Hawkular	Assignee:	Matt Wringe <mwringe>
Status:	CLOSED NOTABUG	QA Contact:	Junqi Zhao <juzhao>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.4.1	CC:	aos-bugs
Target Milestone:	---	Keywords:	Unconfirmed
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-07-24 16:18:56 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Eric Jones 2017-07-21 14:46:48 UTC

Description of problem:
Manually curling the metricsPublicURL and providing the Hawkular-Tenant header and specifying a namespace does not only specify the pods that are currently running.

Looking at the output in more detail it almost seems to show every version of that pod that has run.

Version-Release number of selected component (if applicable):
3.4.1

Providing more details soon in private update.

Comment 2 Matt Wringe 2017-07-24 16:18:56 UTC

We don't only store metrics for the currently running pods.

If you are running a replica set with 10 pods, you may want to know the usage for that replica set overtime. That requires knowing about all the pods which were running under that replica set and not just the current ones.

For data for the pods should automatically expire after a set time, and in more recent version the metrics definitions will automatically expire was well.

This is the intended behaviour.