This document outlines the new features that are being pushed on to CloudRecon Prod environment. Customers will be able to leverage these new features by taking this document as a guideline.
This document is an outline of the new features that are being rolled out on CloudRecon portal in August 2021. Customers will be able to use this document as a guide to leverage the benefits of these new features.
This document is to be used as a reference with target audience which includes company internal personnel, customers, partners.
Use case: CloudRecon will now let you apply some new filters in Lift & Shift Report. You can filter the results in the reports by applying these filters.
To use these filters, navigate to Lift&Shift(IaaS) report and the top right of the report you will get the option to apply role-based filters.
To use these filters, navigate to Lift&Shift(IaaS) report and the top right of the report you will get the option to apply workload-based filters.
You can also click on edit option against any machine in the report as shown below in Fig 3, and that will give you the edit screen where you could apply role-based tags against your machine.
Select the dropdown for “Role” under Tole & Org/Unit to apply a role-based filter to a machine as shown below on Fig 4.
You can add a workload-based tag under “Application & Grouping Tagging” as shown in Fig 5. Simply type in the tag name or create any custom tag if you like.
Introducing two new reports in CloudRecon. The PostgreSQL to Azure PostgreSQL report and the MySQL to Azure MySQL report.
Use Case: You can now utilize this report to get Azure cost estimation and related information if you would choose to move your on-premises PostgreSQL environment to Azure PostgreSQL.
Navigate to the “Data Estate” section in your inventory and select “Postgre-> PostgreSQL” as shown below in Fig 6.
This report will show you cost estimations on Azure PostgreSQL against deployment models like Single Server, Flexible Server, Hyperscale(Citus) and will provide you compute and storage cost estimations for the same.
You can also select which DBs are ignored from the “Default DB(No considered)” tab and also view which databases have been considered for this report from the “Considered Databases” tab in this report.
Use case: This new report will provide Azure cost estimation if you would choose to move your on-premises MySQL environment to Azure MySQL DB against single server and flexible server deployment models.
Navigate to the “Data Estate” section in your inventory and select “MySQL DB” as shown below in Fig 7.
You can also select which MySQL DBs are ignored from the “Default MySQL DB” tab and also view which databases have been considered for this report from the “MySQL DB sizing” tab in this report and understand how the sizing has been done.
Use Case: You can now update software inventory details and server workload info by uploading the software inventory export .xlsx file from Azure Migrate.
Use Case: You can now upload your on-premises MySQL data by running the CloudRecon client installer application which can also be downloaded from CloudRecon itself.
Use Case: You can now upload your on-premises PostgreSQL data by running the CloudRecon client installer application which can also be downloaded from CloudRecon itself.