Can you elaborate/share a screenshot or recording of what you're seeing?

Of course!

What's wrong with that? Do you see the same thing when you select a different time interval (e.g. 6h)?

If it's saying 0 vCPU, it means it's not using any CPU (or is using a very very minimal amount that we don't bill for)

The problem is that we're using very heavily the app now, and today it was showing the ammount just fine. When I select 6 hours for example, it shows the ammout used until now, but when I select 1 hour it doesn't as in the print. Now I know the 1hr option is the only one not working so there is no big problem. So, just reporting that it is happening.

When I select 6 hours for example, it shows the ammout used until now, but when I select 1 hour it doesn't as in the print.

That would suggest that your current usage isn't enough to register (<0.1vCPU)

Are you facing any performance issues?

So, when I see the 6 hours window, it shows that the app is using processing power right now, but when I see the 1hr it doesn't show it. It seems it is using the cpu, but it isn't showing in the 1hr windows specifically, as it shows the last hour usage on the 6 hr one.

Ah I get what you mean about the 1hr window now. There's some oddities on how we aggregate metrics for smaller time windows, so a small bump will not register in that 1h window.

The 6hr/1day view will be the most accurate representation of CPU usage right now.