Central manager - some practical questions

Hi,

This is more to F5 guys here, hopefully somebody will answer..

I struggle to understand how we're supposed to work with Central Manager (CM).

I checked some vids at youtube, git issues, documentation, but:

1. I see list of services in "My application Services" and the health of each. All are green, health is good, I am confused because this is LAB without any connectivity to pool members, then I find out that it shows "Health good" on all services which are not yet published. Why so? Can't you use something else, like N/A for example for such services? This is just confusing.
2. second question is where are the pool member health info? When I open deployed service detail I see something like this:

   Whole screen filled with with something what doesn't help me at all, I can click to alert and check logs, but why I cannot click to members and check their current status?

3. According to this article there's this table related to service health:
    
   Why are you mixing health (healthcheck result) and traffic into one "service status"? Also why "member status unknown" causes Critical service status? That makes no sense, unknown state is either caused by waiting for the health-check result or it's on purpose because I simply don't care what's the health of the server, what is critical on that?
4. Why list of services don't show IP addresses and ports, you really want your customers to rely only on service name?
5. OK lets rely on service name, why migration tool (from UCS to CM) completely renamed all my services and created something like this? Name "application_xx" is not really helpful...

    

6. CM seems to not have any partitions/tenants, are we supposed to have all objects in one bucket? We have, for example,  >1000 certificates, I don't like that idea
7. And last one, when we can see APM features in CM?