...
A: The Cloudamize agent collects system and application-related performance and usage metrics such as CPU, memory, disk, network, and running applications.
...
A: The Cloudamize agent sends data to the Cloudamize server over SSL (TCP port 443).
Q: Do I need to open a firewall to send data to the Cloudamize server?
A: Yes, the Cloudamize agents send data to Cloudamize servers over SSL (TCP port 443). You need to make sure that outbound SSL (TCP port 443) access is permitted to the Cloudamizes. You do not need to open firewall access on the targeted server if you are using an internet proxyfrom the Agent server to the chosen Cloudamize endpoint.
Q: What if my physical/virtual servers do not have direct access to the Internet?
A: If your physical/virtual servers have access to an internet proxy server, Cloudamize agents will still be able to relay data via the internet proxy to the Cloudamize servers. This is configured during installation.
Q: Is there a proxy available to forward data from the physical/virtual machines that are not directly accessible by Internet?
A: No, Cloudamize does not provide a proxy server to forward data from the physical machines that are not directly accessible by Internet, but this is a use-case for the Cloudamize Agentless Data Collector.
Q: Is the Cloudamize agent a standalone executable (i.e. libc) or does it need Java or another framework preinstalled?
A: For Linux server hosts and virtual machines, the Cloudamize agent is a standalone binary executable. For Windows servers and virtual machines, the Cloudamize agent requires .NET framework 23.0 5 or greater.
Q: What is the performance overhead of running agents on physical/virtual servers?
...
A. Agent software is provided as-is, our guides can be used. Mass-installation is not supported by Cloudamize, but commonly done by scripting, SCCM, etcand similar methods.
Q: For ADC Where are credentials stored, Only on the data collector VM, or are they saved to Cloudamize in the console?
A. They are stored on C:\Program Files (x86)\CloudamizeAgentlessDC\HostInfo.xml or HostInfoBackup.xml, Only on the data collector VM. QThese credentials are not transmitted to Cloudamize in any form.
Q: Will CloudAmize Cloudamize help to discover the MS SQL database and application mapping? (When I discover the database name, will I be able to get the Application details running on the database, for eg: Application Host Name, Application IP address)?
A. Yes, for the details that will be you can find details of what MS SQL data is collected by Cloudamize for the MS SQL data on our Knowledge base at https://support.cloudamize.com/kb/Agentless-Overview.36852924700.html under Supported MS SQL data collected by Agent-Based and Agentless.basic-and-advanced-ms-sql-collected-by-agent-based
Q: What is the minimum version on OpenSSL/TLS that is supported by the current Cloudamize agent?
A. Cloudamize supports TLS 1.2 and above versions. The TLS version , though 1.3 is preferred where available. TLS versions below 1.2 is are not supported due to security reasons. Cloudamize Agent is currently using version 3.0.13. for the OpenSSLin order to keep data transmissions secure. The minimum required version of openSSL is 13.10.1 0 or higher.
Q: Does the watchdog restart the agents too or does it only kill the agents?
...
A. Installation of actual agents to collect data for an assessment requires a customer key that is only issued upon the opening of the console account. A free demo account can be provided that will give access to the Agent download and installer, but the dummy key will result in any gathered data being discarded upon receipt, and once you have the actual customer key you would have to uninstall and re-install again on all infrastructure using the customer key.The software is available with a no-op key for the purposes of testing system impact and viewing captured data, covered in this article: https://support.cloudamize.com/kb/analyzing-data-collected-by-agents
Q: Agentless data collector is limited to 500 hosts per subnet. How would you scale the data collector to deal with a larger subnet? Is it a vertical scale, or a horizontal scale?
A. We recommend increasing number of Agentless Data Collector. To scale the Cloudamize Agentless Data Collector to handle more than 500 hosts, it is recommended to use a horizontal scaling approach by installing additional data collectors on separate machines. We recommend increasing the number of Agentless Data Collectors as best practise. Each data collector can monitor up to 500 hosts by default, so for larger environments, it is highly recommended to deploy multiple data collectors across different machinesrecommended to deploy multiple data collectors across different machines. There is an option to expand the maximum number of hosts on a single ADC, however be aware that doing do without also scaling system resources may result in instability in the ADC.
Q: Can we schedule the data upload from data collector server to cloudamize SaaS server on any time which clients wish to schedule?
...
A. For the Nutanix hypervisor environment, Cloudamize only supports Agent and Agentless data collection methods. If the Nutanix hypervisor hides the CPU model for VMs where data is collected using Cloudamize Agent or ADC, the user will have to specify the CPU details manually. Cloudamize will assess VMs based on data collected by the Agent or ADC.
Q: Can we change the Installation Drive for Agent?
A. No, the Agent relies on being installed in the default drive where Windows in installed as it sits in the Program Files (x86) directory and utilises several Windows features from the OS drive. This is why the The GUI installer doesn’t will not prompt for an install location and why the usual .msi options that would change the location are disabled.
...
Q: What is the list of servers that must be reachable for the agents? am-de.cloudamize.commonly?A. It depends on the region chosen for the assessment, but if you’re using our EU collector then only must be reachable for the agents? am-de.cloudamize.com is required, traffic is not sent to/from anywhere elsecommonly?
A. The list of servers that must be reachable for from the Cloudamize agents to our servers at depends on the chosen endpoint: am.cloudamize.com for the US infrastructureendpoint, am-de.cloudamize.com for the EU infrastructureendpoint, or am-ae.cloudamize.com for UAE infrastructure over the the UAE endpoint, all using TCP port 443, either directly or through a corporate proxy.
...