Terminated containers still consuming HU's with k8s app-only?

[Enrico_F]

We use application-only monitoring on a managed OpenShift PaaS and recently I noticed that each of our dead container instances (showing up as "hosts" in unmonitored state) still happily consume host units even after they've been long restarted/terminated (it seems up to 72 hours). In our case this can be verified easily in the "Deployment state" view:

Each of the above "hosts" belongs to a terminated container. We have LOTS more of these and the total HU consumption is hugely significant (in our case it is almost 25% of our total HU volume).

If I manually hit "Disable monitoring" for these then they will no longer contribute to the HU consumption number.

Questions that come to mind:

1. Does anybody else agree with me that this is not expected?
2. Can anybody confirm the same behavior on their end?
3. Are HU consumed in this manner actually counted against the licensed HU volume?

We are currently on Managed 1.174.

Any feedback is welcome.

[skrystosik]

Are you sure that those HU are still consumed? On License dashboard in CMC there is the same?

Sebastian

[Enrico_F]

It's difficult to compare the HU consumption number in the deployemnt status with the one in the CMC because we have more than 400 hosts in our environment and simple filtering with Status=Unmonitored over all hosts is not possible (it's always limited to 400 hosts). Plus, there is a lot of fluctuation throughout the day and - if I'm not mistaken - the figure in the CMC is calculated once every 24h.

But using different filters in the deplyoment status view and adding the HU's manually I'm getting pretty close to the number in the CMC... so yes, I would say I'm pretty sure they are counted.

[skrystosik]

So you should open support ticket. It is not normal that unmonitored hosts consumes license. I’ve never faced such issue so far (I have application only monitoring as well on one client environment).

Sebastian