...
When you have configured your assessment Assessment and added all infrastructure, you are ready to begin collecting data. Your Settings screen’s Assessment tab will look something like this:
...
Starting the Assessment, Step-by-Step
Starting the assessment Assessment consists of three stages:
...
Cloudamize refers to servers you have added to the assessment Assessment as “nodes”. In this first stage, you can review the following values:
Purchased Nodes: The total number of licenses purchased for this assessment, ie Assessment, i.e., the maximum number of servers that can have assessment results published in this assessmentAssessment.
Consumed Nodes: The current number of licenses that will be used with the given settings, ie i.e., the number of servers that are included in the Assessment scope.
Installed Agents: The current number of servers that have been added to the Assessment via one or more of the data collection methods (Agent, Agentless, etc). This includes both in-scope and out-of-scope servers.
If the number of Consumed Nodes would be is greater than the number of Purchased Nodes, you won’t be able to move to the next step, and the “Next” button will be disabled:
...
Stage 2: Select Assessment Regions
On this screen, you will see a list of Cloud Services Providers (CSP) which that are available for this Assessment, and a Region dropdown menu will be visible next to each of them.
...
You should select for each CSP the default region for cloud recommendations to be based upon for each CSP. The Total Cost of Ownership (TCO) and cloud instance recommendations (ie i.e., the assessment deliverables) will be built using the selected region, basing results on the availability and cost of cloud instance types in that region.
...
Cloudamize will, typically, collect data over a period of time set by you , before processing final results following the end of this data collection period, then deliver those results on a final date. At this stage, you can set these dates:
...
There are three dates here:
...
You may customize the Start and End Data Processing dates, though a minimum period of 11 days between them is enforced to allow sufficient data collection. You should aim to include any period of particular interest in this range (eg e.g., typical heavy usage periods, spikes, etc.) to allow for the most accurate results.
The Results Ready Date cannot be customized , and is fixed to a minimum of 3 working days after the End Data Processing date (adjusted for availability). The cases in which this might be longer are as follows:
Based We might add additional days based on the size of your infrastructure and our current delivery load we might add additional days.
If we have intentionally blocked days due to any reason, that might also add to delivery days.
No deliveries take place on Weekends, being delayed to the start of the following week instead.
...
It is possible to stop a running Assessment during the Data Collection period. A “Stop Assessment” button is available during this time to perform this:
...
Finally, once started, your Assessment status will also be shown on the Console Landing Page:
...