This topic provides a description of the System Status page.
The left side of the System Status page provides you with an overview of the VMware Skyline Collector health, management capabilities. The system status includes Stop, Start, and Restart and each endpoint connected to the VMware Skyline Collector for the data collection.
The Overview section of the System Status page displays the overall health of the Skyline Collector, which typically is in a ‘Your collector is running’ state. Also, the health of each configured data endpoint is displayed.
The Collector section allows you to manage the Skyline Collector. From here, you can Restart, Stop, or Deregister the Skyline Collector service. The Skyline Collector ID and My VMware user which was used to register the Skyline Collector is displayed. The Skyline Collector ID is a unique identifier for your specific Skyline Collector instance. It is used to identify the information sent back to VMware. You can also use the Skyline Collector friendly name to identify your Skyline Collector instance when working with VMware Global Support Services (GSS). The Entitlement number and support type (Production Support or Premier Services) are also displayed. The entitlement accounts link the Skyline Collector data to support requests. Entitlement accounts are managed through https://my.vmware.com.
If needed, the most recent Skyline Collector log activity can be displayed within the user interface.
For each vCenter Server that the Skyline Collector is connected to, there are three endpoints configured. Also, the endpoint health is displayed.
The VC_CHANGES endpoint type collects vCenter topology and configuration information.
The VC_EVENTS endpoint type collects vCenter event information.
The VC_HOSTS endpoint type collects ESXi event information (through vCenter Server).
For each NSX Manager that the Skyline Collector is connected to, there are three endpoints configured. Also, the endpoint health is displayed.
The NSX endpoint type collects NSX product and configuration information.
The NSX_TELEMETRY endpoint type collects NSX operational metrics information, such as CPU, memory, and disk use.
The NSX_EVENTS endpoint type collects NSX event information.
Each endpoint displays the name of the product instance that it is connected to, the account currently used to capture data and the last time data collected by that endpoint collection instance. Endpoints that are started and actively collecting data is shown in green, while endpoints that are stopped or have issues are shown in red.