Describe the feature:
On the stack monitoring page for Cloud users, the UI currently shows the license level, expiry date and a link to the license management page.
This creates confusion because Cloud has their own SaaS subscription levels that users buy into which is separate from stack licenses which also have the same name. Furthermore, Cloud users are not required to manage any stack licenses for any clusters that they deploy.
Improvement
For any Cloud clusters, hide the license information on the Stack Monitoring page.

CC @elastic/cloud-pms
Pinging @elastic/stack-monitoring
I think this should be possible. I will take a look. Thanks for filing this!
cc: @chrisronline It could be worth thinking about whether or not differentiate between Cloud and non-Cloud for the types of Alerts we will send when we get to the point of building them out. I'll find a home for further discussion about this and tag you on it.
++ to do this.
Separately, we should also see about disabling/hiding the "license is about to expire" Cluster alert in Cloud. In theory, we shouldn't ever hit it, but if can just disable it, it's guaranteed to not be an issue.
We actually have a setting for this that the cloud folks could use if they want and they could use it across released versions. It's 'xpack.monitoring.show_license_expiration'. This would be my preference. Any thoughts on that @zanbel ?
If we do want to try to do detection, though, we could try something like this: https://github.com/elastic/kibana/pull/45257/files
I'm +1 on showing a message that will be useful and informative for cloud users.
Ideally my suggestion will be to identify enhance the current mechanism to distinguish between the different deployment options, i.e. self-managed, ECE, ESS, and ECK, and showing a relevant message. E.g.:
Alternatively we can start with what @cachedout is suggesting and use that indication to display a custom license message to cloud users.
In any case, I agree the current information displayed is confusing and doesn't provide a good indication about the license status.
It appears that at one point, at least, the cloud team discussed doing this: https://github.com/elastic/cloud/issues/4655
I have opened https://github.com/elastic/cloud/issues/39788 to follow-up and see if it's still set or if it can be turned back on.
@osmanis You don't by chance still have access to the cluster that's exhibiting this behavior, do you? This shouldn't be happening and we're trying to figure out why.
@cachedout this was raised by a customer in a support case where they were running 7.2. I just tested and can re-create this on 7.2.0 and 7.3.0 in ESS. Let me know if you want access to those but you should be able to also re-create in Cloud.
@osmanis If you have something up right now, we can have @nachogiljaldo double-check it and make sure xpack.monitoring.show_license_expiration is set to false.
I sent the details to @nachogiljaldo.
@cachedout
[root@0ffa1780c6ec /]# cat /app/config/kibana.yml | grep -i license
xpack.monitoring.show_license_expiration: false
xpack.license_management.enabled: false
I wonder if those 2 do not play well with each other?
I found it. Fix is here: https://github.com/elastic/kibana/pull/45537
Thanks for your help, @osmanis and @nachogiljaldo