Monitoring - Revision history

Lakshmi at 06:25, 12 September 2025

2025-09-12T06:25:08Z

Show changes

Lakshmi at 06:26, 23 August 2023

2023-08-23T06:26:09Z

Lakshmi at 06:04, 23 August 2023

2023-08-23T06:04:31Z

Lakshmi at 04:45, 23 August 2023

2023-08-23T04:45:37Z

Lakshmi at 14:53, 22 August 2023

2023-08-22T14:53:51Z

Lakshmi at 13:54, 7 August 2023

2023-08-07T13:54:38Z

Lakshmi at 07:59, 3 August 2023

2023-08-03T07:59:49Z

Lakshmi at 10:51, 20 July 2023

2023-07-20T10:51:36Z

Show changes

Lakshmi at 08:17, 10 July 2023

2023-07-10T08:17:14Z

Admin at 10:59, 1 September 2020

2020-09-01T10:59:33Z

@@ Line 20: / Line 20: @@
 * Notification area
-A [[File:Resume_icon.jpg |45x45px]] is a normal state.
+A [[File:Resume_icon.jpg |25x25px]] is a normal state.
 [[File:Monitoring_EnvironmentsDetails.jpg |700px]]
@@ Line 55: / Line 55: @@
 ===Progress status===
 The Progress widget on the dashboard shows when the migration started, the proposed switchover date, and then a status bar to help determine if the switch-over date is achievable.
-It provides metrics of the peak transfer rates and these help to determine remaining time.
+It provides metrics of the peak transfer rates to understand the data transfer performance and to estimate the time required to complete transfer.
-[[File:Example.jpg ]]
+[[File:Monitoring_progress_status.jpg | 700px]]
 ===Catalog Migration status===
 The catalog migration graph shows the current state of the images. When hover over a segment, it will display the Percentage (in terms of size of those objects in the catalog) and the number of images.
@@ Line 62: / Line 64: @@
 Images in “red” segment requires investigation as they are failed during data transfer.  The issues need to be resolved and the failed images must be reverted to re-submit. The images can also be marked as <i>ignored</i> incase the images doesnt needs to be migrated.
 The refresh icon refreshes the data on the status widget.
 ===Duplication status===
@@ Line 68: / Line 72: @@
 The graph is updated initially by the Duplication Rules created on Selections
 During Transition, it shows the duplication status of selected images (duplication completed, In Progress, queued etc)
 ===Clients status===
@@ Line 77: / Line 83: @@
 * <b>Destination Connected</b>	Selected hosts that the destination can connect to
 * <b>Destination Switched</b>	Selected hosts that have been updated to have destination as the master.
 ===Config Migration status===
@@ Line 84: / Line 92: @@
 * <b>Exported</b>
 * <b>Deselected</b>
 ===Service Status===
@@ Line 90: / Line 100: @@
 The service can also stop/start or restarted from the logging screen.
 Clicking on the page icon on <b>Service Status</b> widget shows generic logs from Tranzman which are not related to specific actions.
 ===Resources===
@@ Line 96: / Line 108: @@
 * CPU usage
 * RAM usage
-A snapshot of report on the Agent usage can be viewed by clicking on the agent name
+A snapshot of report on the Agent usage can be viewed by clicking on the agent name.
-[[File:Resources.JPG | border|400x400px]]
+[[File:Monitoring_resources_agent.jpg | 700px]]

@@ Line 28: / Line 28: @@
 Environment status icon will be in dark blue shows that Tranzman is waiting for a response (Querying instances) from Agent for initial information.
 The state remains till it connects to an agent and perform the initial discovery.<br>
-[[File:Monitoring_querying_instance.jpg | 700px]]
+[[File:Monitoring_querying_instance.gif | 700px]]
@@ Line 50: / Line 50: @@
 Terminate hung processes, and/or restart the Agent to proceed with the Transition.
 A hung agent will also raise an Alert.<br>
-[[File:Monitoring_failed_instance.jpg | 700px]]
+[[File:Monitoring_failed_instance.gif | 700px]]

@@ Line 27: / Line 27: @@
 ====Querying====
 Environment status icon will be in dark blue shows that Tranzman is waiting for a response (Querying instances) from Agent for initial information.
-The state remains till it connects to an agent and perform the initial discovery.
+The state remains till it connects to an agent and perform the initial discovery.<br>
 [[File:Monitoring_querying_instance.jpg | 700px]]
@@ Line 33: / Line 33: @@
 ====Active====
 The Agent is active and connected to Tranzman Server. The agent will keep performing tasks at defined intervals.
-The status will in green color while active.
+The status will in green color while active.<br>
 [[File:Monitoring_active_instance.jpg | 700px]]
@@ Line 42: / Line 42: @@
 The issues must be resolved to resume the agent
 A change in the pause/resume state will be recorded in the <i>Environment History Report</i> along with its date and time.
-The status turns to black if the agent is paused.
+The status turns to black if the agent is paused.<br>
 [[File:Monitoring_pause_instance.jpg | 700px]]
@@ Line 49: / Line 49: @@
 The red blinking dot tells the Agent is not responding for more than 1 hour. This could be either the agent services not running, or there are hung processes (probably CURL).
 Terminate hung processes, and/or restart the Agent to proceed with the Transition.
-A hung agent will also raise an Alert.
+A hung agent will also raise an Alert.<br>
 [[File:Monitoring_failed_instance.jpg | 700px]]
@@ Line 56: / Line 56: @@
 The Progress widget on the dashboard shows when the migration started, the proposed switchover date, and then a status bar to help determine if the switch-over date is achievable.
 It provides metrics of the peak transfer rates and these help to determine remaining time.
+[[File:Example.jpg ]]
 ===Catalog Migration status===
 The catalog migration graph shows the current state of the images. When hover over a segment, it will display the Percentage (in terms of size of those objects in the catalog) and the number of images.

@@ Line 20: / Line 20: @@
 * Notification area
-A  [[File:Resume.JPG | border|45x45px]]  is a normal state.
+A [[File:Resume_icon.jpg |45x45px]] is a normal state.
 ====Querying====
 Environment status icon will be in dark blue shows that Tranzman is waiting for a response (Querying instances) from Agent for initial information.
 The state remains till it connects to an agent and perform the initial discovery.
 ====Active====
 The Agent is active and connected to Tranzman Server. The agent will keep performing tasks at defined intervals.
 The status will in green color while active.
 ====Paused====
@@ Line 38: / Line 43: @@
 A change in the pause/resume state will be recorded in the <i>Environment History Report</i> along with its date and time.
 The status turns to black if the agent is paused.
 ====Hung/Failed====
@@ Line 43: / Line 50: @@
 Terminate hung processes, and/or restart the Agent to proceed with the Transition.
 A hung agent will also raise an Alert.
 ===Progress status===

@@ Line 146: / Line 146: @@
-----
 {| class="wikitable"  style="margin:auto;width:100%;color:blue;text-align:center;borderstyle=ridge;"
 |-

@@ Line 24: / Line 24: @@
 [[File:EnvironmentsDetails.JPG | border|1100x800px]]
-====Querying===
+====Querying====
 Environment status icon will be in dark blue shows that Tranzman is waiting for a response (Querying instances) from Agent for initial information.
 The state remains till it connects to an agent and perform the initial discovery.
@@ Line 101: / Line 101: @@
 To view the <b>Environment History</b>, Navigate to <b>Views</b> -> <b>Reports</b> and click on the <b>Environment History</b> icon.
 A pop-up window showing the history report of environment, the state and the reason for the change in state
@@ Line 148: / Line 138: @@
 The different State are:
-<b>deselected</b>: The configuration item is excluded by rules in Selections
+<b>deselected</b>: The configuration item is excluded by rules in Selections.
 <b>exported</b>: List the configurations available on origin
 <b>imported</b>: list the configurations migrated to Destination

@@ Line 1: / Line 1: @@
-== Headline ==
+===Introduction===
-The Tranzman Dashboard provides the ability to check state of Environments, Tranzman Resources(CPU, RAM, Tranzman specific filesystems), Migration State, Service Status , Progress and Config Migration.
+The <b>Tranzman</b> dashboard gives an overview of the progress and status of the various aspects of the Transition
-Tranzman UI is very flexible as it enables end user to perform majority of migration related steps through UI.
+It porvides below details for easy reporting.
-Below is a brief of all the sections :
+* State of the added Environments
-===Tranzman Resources===
+Detailed information can be found below:
 [[File:Resources.JPG | border|400x400px]]
 A  [[File:Resume.JPG | border|45x45px]]  is a normal state.
 [[File:EnvironmentsDetails.JPG | border|1100x800px]]
 This section reports the progress of the catalog migrated (for same vendor migrations) ????
 [[File:MigrationState.JPG | border|400x400px]]
+===Catalog Migration reporting===
 This section highlights the state of different services like NFS Service ,Audit service etc. Any red icon in this sections means the service is not running and need to be checked.
 [[File:ServiceStatus.JPG | border|400x400px]]
+===Config Migration reporting===
 The Progress section has details like migration start date,planned switchover date , possible switchover date based on transfer speed.
@@ Line 56: / Line 60: @@
-===Config Migration===
+===Clients status reporting===

@@ Line 68: / Line 68: @@
 Once transition is completed you can jump to the Recovery Documentation section to start restoring the data.
 [[ Manage Hosts | Jump to Host Management for managing certificates ]]
 [[ Recoverydocs | Jump to Recovery Documentation for restoring data ]]