![]() You can filter connections by the following: During the scan, current data is displayed. Scan a specific root, node, or workspace. ![]() However, the root isn't monitored or visible. If a root, node, or workspace is deleted, the history is maintained. However, the root isn't monitored or visible until it is active again. If the root, node, or workspace is suspended, the history is maintained. ![]() When a workspace is disconnected it is no longer scanned, and isn't counted as a license unit. The following actions are available for each entry in the list:Ĭonnect to scan a specific root hierarchy or workspace. The hierarchy type can be one of the following: The name of the root, folder, or workspace. This workspace won't be scanned until the status is changed from Suspended to Scan. If a fix is available, the user can see it by placing the cursor/mouse over the workspace status. For example, CEM's permissions were removed, or CEM activity was blocked by the user's environment. Something failed while this workspace was being scanned. The workspace status is up to date and isn't currently being scanned.ĬEM is currently scanning this workspace for data acquisition and analytics. The user can set CEM to start monitoring it if there is an available license. The initial connection failed and CEM has no permissions on this workspace.ĬEM is waiting for permissions to be granted by the user via the AWS stack deployment process.ĬEM has permissions over this workspace, but the workspace is currently not being monitored. The initial discovery, where a root is currently being scanned for its workspaces. The page displays the following details about each entry in the list: Status elements From the Setup > Platform management > page, you can view and manage connections to workspaces.
0 Comments
Leave a Reply. |