Transition from On-Premise to the Cloud
Migrating an application from a data center to the cloud requires careful planning and preparation. This involves a significant business risk resulting from unexpected delays, missed deadlines and possible customers downtime. Often overlooked is the fact that existing tools, specifically monitoring solutions, are likely not to be transferable to a cloud environment. The dynamic nature of the cloud makes monitoring even more important than before. In addition, proper visualization of the architecture can play a key role in a successful transition.
You should be able to answer questions such as
- Can I visualize the architecture of a newly transitioned application in the cloud?
- Is my map of the architecture updating automatically as changes are applied?
- What are the dependencies between my application components?
- Can I visualize those dependencies?
- Can I monitor the operational metrics on the application running in the cloud?
- Do I have a way to be alerted when certain metrics of the applications becomes abnormal?
- Can I quickly understand my service KPIs without having to dive to the level of individual instances?
- Do I have architecture documentation that is truly up to date (up to 15 minutes ago) in the new cloud environment?
Using ITculate, all this information is available to you. Using simple and clean visualizations of the architecture and dependencies. ITculate identifies all the components and how they interconnect. Start from the level of your applications, traverse the relationships between and within services. Stop at the layer that is relevant to your issue and use the rolled up metrics from the underlying dynamic layers. Use the automatically provided KPIs per component or add / remove metrics as needed. ITculate’s meta-information engine knows the metrics units and places metrics to compare on the same chart. With ITculate, you can track the progress of the transition to the cloud, make sure that everything works correctly and troubleshoot the application if it is not working correctly.
ITculate discover automatically the relationships between components. Specialized algorithms project these relationships and identifies clusters, groups and services. These algorithms also find higher level relationships (e.g. between services) using the lower level ones. In addition the system can leverage predefined environment Tags or the ITculate REST SDK. Groups and services are displayed as collapsible elements to enable the user to manage the context.
Whenever a component or a service metric becomes abnormal, a detailed message is provided with detailed description of the issues, related charts and suggested remediation actions. This enables DevOps to be proactive and address impending issues before they materialize.
Relevant posts for cloud migration:
- Understanding resources connectivity, to answer questions like
- How to control the costs as you move to the cloud: AWS Cost Savings.
- Learn about the technology: Discovering and visualizing a new cloud environment
- Moving on-premise storage to the cloud: Monitoring ONTAP Cloud
ITculate collector gather information on how the environment performs. It can not access your data. We recommend installing it without access to your network, using strict Read-Only credentials and contained in a way that provides the user full control (e.g. using AWS IAM role). See full security related information here.