多云在屏幕上怎么册除
AIOps stands for Artificial Intelligence for IT Operations, and to explain this buzzword in layman terms, it roughly means enabling our IT infrastructure with the new intelligence to automatically discover what its users (humans, machines, or applications) need, then analyze the tradeoffs of those needs (of who and what is more or less important to the business), and finally making the necessary changes (by provisioning, allocating more or less resources) to apply and balance those tradeoffs. This cycle then continuously repeats itself.
AIOps代表用于IT运营的人工智能，并以通俗易懂的方式解释这个流行词，它大致意味着使我们的IT基础架构拥有新的智能功能，可以自动发现其用户(人员，机器或应用程序)的需求，然后分析其折衷方案。这些需求(对谁或什么对企业而言更重要)，最后进行必要的更改(通过配置，分配或多或少的资源)以应用和平衡这些权衡。 然后，此循环不断重复。
When AIOps is enabled for your applications deployed on Multicloud, it allows your applications to run smoothly and efficiently by continuously balancing resources in your Multicloud environment, and this can be automated via policies without users interventions.
为在Multicloud上部署的应用程序启用AIOps后，它可以通过持续平衡 Multicloud环境中的资源来使您的应用程序平稳高效地运行，并且可以通过策略自动执行，而无需用户干预。
AIOps的吨他积木 (The Building Blocks of AIOps)
Today, an effective AIOps technology stack begins with the discovery of your IT infrastructure, from containers, virtual machines and physical server clusters in your private cloud, to the virtual instances or Kubernetes clusters you deploy on the public clouds. Apart from IT infrastructure, visibility into your applications’ health allows events correlations between these applications and the infrastructure they are running on.
如今，有效的AIOps技术堆栈始于发现IT基础架构，从私有云中的容器，虚拟机和物理服务器群集，到部署在公共云上的虚拟实例或Kubernetes群集。 除了IT基础结构之外，对应用程序运行状况的可见性还允许这些应用程序与它们所运行的基础结构之间的事件关联。
Insight refers to the application of machine learning (ML) and data science to the data collected. Due to the sheer volume of these data, the analysis is often impossible to be done manually or accurately by human.
洞察力是指将机器学习(ML)和数据科学应用于收集的数据。 由于这些数据量巨大，因此通常无法人工或准确地进行分析。
Finally, the tradeoffs computed by the machine learning algorithms can be converted into actions to be applied to your IT infrastructure on the fly. For example, an outcome is scaling out compute resources (can be anywhere on the Multicloud) to improve the performance of your application depending on those resources.
最后，由机器学习算法计算出的折衷可以转换为要动态应用于您的IT基础架构的动作。 例如，结果是扩展计算资源(可以在Multicloud上的任何位置)以根据这些资源提高应用程序的性能。
实际了解AIOps (A practical look at AIOps)
In the rest of this article, I will demonstrate a practical example of AIOps for Application Performance Management (APM) with a microservices application deployed in a container based environment. In my example, I will use AppDynamics and Cisco Workload Optimization Manager (also as Turbonomics) to provide me with visibility into the state of my application and IT infrastructure.
在本文的其余部分中，我将演示在基于容器的环境中部署微服务应用程序的AIOps for Application Performance Management(APM)。 在我的示例中，我将使用AppDynamics和Cisco Workload Optimization Manager (也称为Turbonomics )为我提供有关应用程序和IT基础架构状态的可见性。
AppDynamics is an Application Performance Management software which can manage the performance and availability of applications across multicloud. CWOM uses AI driven analytics to optimize performance, compliance, and cost in real time. AppDynamics and CWOM can work together to match application demand to infrastructure supply to continuously ensure application performance.
AppDynamics是一个应用程序性能管理软件，可以管理跨多云的应用程序的性能和可用性。 CWOM使用AI驱动的分析来实时优化性能，合规性和成本。 AppDynamics和CWOM可以一起工作，以将应用程序需求与基础架构供应相匹配，以不断确保应用程序性能。
Both software can be deployed within your private cloud, or as a software as a service (SaaS) subscription on public clouds. I will be using the SaaS option for AppDynamics and the private cloud option for CWOM. I will also be deploying my demo application on a local Kubernetes cluster created in my private cloud. As such, my application and IT infrastructure are on private cloud, but as I will explain later on, these can be on any public clouds.
两种软件都可以部署在您的私有云中，也可以作为软件即服务(SaaS)订阅部署在公共云中。 我将对AppDynamics使用SaaS选项，对CWOM使用私有云选项。 我还将在私有云中创建的本地Kubernetes集群上部署演示应用程序。 因此，我的应用程序和IT基础架构位于私有云上，但是正如我稍后将解释的那样，它们可以位于任何公共云上。
对应用程序和IT基础架构状态的可见性 (Visibility into Application and IT infrastructure state)
First, I will need an application. For this, I am leveraging on the Online Boutique microservice demo application. AppDynamics supports different deployment options and use cases, ranging from code level application performance monitoring, cloud monitoring, end user monitoring, or infrastructure visibility.
首先，我需要一个应用程序。 为此，我利用Online Boutique微服务演示应用程序。 AppDynamics支持不同的部署选项和用例，包括代码级应用程序性能监视，云监视，最终用户监视或基础结构可见性。
For this article, I am using code level application performance monitoring and I am instrumenting its Golang SDK into the Golang source code of the frontend microservice in the Online Boutique demo application. This involves adding information and access key credentials of my AppDynamics SaaS controller into the main.go file as well as initializing calls to its Golang SDK at various Golang functions in the application where performance monitoring are warranted.
对于本文，我将使用代码级应用程序性能监视，并将其Golang SDK插入Online Boutique演示应用程序中的前端微服务的Golang源代码中。 这涉及到将AppDynamics SaaS控制器的信息和访问密钥凭据添加到main.go文件中，并在需要进行性能监视的应用程序中的各种Golang功能处初始化对其Golang SDK的调用。
After these instrumentation steps are completed, I compiled the Golang application source code into a docker container and deployed it together with the rest of the Online Boutique application’s containers on my Kubernetes cluster.
完成这些检测步骤后，我将Golang应用程序源代码编译到docker容器中，并将其与Online Boutique应用程序的其余容器一起部署到了Kubernetes集群上。
And, the logs from the frontend container show the AppDynamics Golang SDK agent is started successfully. At this point, the Golang SDK agent establishes connection to the AppDynamics controller with the AccessKey credentials. The information and AccessKey credentials of my AppDynamics controller are instrumented into the main.go file of the frontend container in an earlier section of this article.
并且，来自前端容器的日志显示AppDynamics Golang SDK代理已成功启动。 此时，Golang SDK代理将使用AccessKey凭据建立与AppDynamics控制器的连接。 本文前面的部分将AppDynamics控制器的信息和AccessKey凭据插入前端容器的main.go文件中。
Logging in to my AppDynamics dashboard, I can now see the Golang SDK agent has connected successfully and the controller is receiving application performance information from the container.
登录到我的AppDynamics仪表板，现在可以看到Golang SDK代理已成功连接，并且控制器正在从容器接收应用程序性能信息。
Next, I will need to setup my CWOM software to communicate with AppDynamics controller so that it can receive insights from AppDynamics controller regarding my application. I will now login to my CWOM software.
接下来，我将需要设置CWOM软件以与AppDynamics控制器通信，以便它可以从AppDynamics控制器接收有关我的应用程序的见解。 现在，我将登录到CWOM软件。
CWOM is agent-less and all that is required for communication between CWOM and AppDynamics controller is to setup my AppDynamics controller’s public address, username and password in CWOM.
CWOM是无代理程序的，在CWOM和AppDynamics控制器之间进行通信所需的全部工作就是在CWOM中设置AppDynamics控制器的公用地址，用户名和密码。
After a short while, CWOM now has the Application Performance Insights regarding my Online Boutique application from my AppDynamics controller.
不久之后，CWOM现在从我的AppDynamics控制器获得了有关我的Online Boutique应用程序的应用程序性能见解。
The next thing after this is to setup CWOM to gain visibility into my IT infrastructure, which in my case, is the local Kubernetes cluster where my Online Boutique application is running. To achieve this, I will deploy CWOM’s container pods in a non-default namespace on my Kubernetes cluster and these container pods will monitor the performance of running micro-services in Kubernetes Pods, as well as the efficiency of underlying infrastructure. My CWOM software’s credentials are setup in a ConfigMap object. Examples of the full Kubernetes YAML files are available at Turbonomics’ Github.
此后的下一件事是设置CWOM以了解我的IT基础结构，在我的情况下，该基础结构是运行我的Online Boutique应用程序的本地Kubernetes集群。 为此，我将在Kubernetes集群上的非默认名称空间中部署CWOM的容器Pod，这些容器Pod将监视Kubernetes Pod中运行微服务的性能以及基础架构的效率。 我的CWOM软件的凭据在ConfigMap对象中设置。 完整的Kubernetes YAML文件的示例可从Turbonomics的Github中获得 。
With this, the Visibility and Insight engines for my AIOps setup are complete.
这样，我的AIOps设置的可见性和Insight引擎就完成了。
具有可见性和洞察力的AIOps→行动 (AIOps with Visibility and Insights → Action)
Finally, I am now ready to validate Visibility of my Application Performance and IT infrastructure can lead to Insights and these Insights can then be translated into Actions.
最后，我现在准备验证应用程序性能的可见性，并且IT基础架构可以带来洞察力，然后可以将这些洞察力转化为行动。
To trigger this, I need to generate increased load to my Online Boutique application so that its Application Performance starts to degrade. When this happens, Insights regarding my Application Performance degeneration should trigger the Insight engine (CWOM) to execute the necessary Actions to adjust and balance IT infrastructure to restore my Application Performance.
要触发此操作，我需要为Online Boutique应用程序增加负载，以使其应用程序性能开始下降。 发生这种情况时，有关我的应用程序性能下降的见解应触发见解引擎(CWOM)执行必要的操作，以调整和平衡IT基础结构以恢复我的应用程序性能。
I increased the traffic generated by the load generator container pods to the frontend container pod in the Online Boutique application. After the traffic is increased, the application’s average response time has significantly increased from sub 100 milliseconds to above more than 300 milliseconds. In addition, from my AppDynamics’ controller Application Transaction Scorecard, I see Very Slow and Slow transactions are reported by the Golang SDK agent in the application’s container.
我在Online Boutique应用程序中将负载生成器容器容器生成的流量增加到前端容器容器。 流量增加后，应用程序的平均响应时间从不到100毫秒显着增加到超过300毫秒。 另外，从我的AppDynamics控制器的应用程序交易记分卡中，我看到Golang SDK代理在应用程序容器中报告了非常慢和慢速交易。
Logging back into my CWOM software, I see new Critical (red) and Warning (yellow) alerts related to the containers running the affected Online Boutique application.
回到我的CWOM软件，我看到与运行受影响的Online Boutique应用程序的容器有关的新的严重(红色)和警告(黄色)警报。
I will now create an Automation Policy in CWOM for Containers to dynamically balance resources to improve and restore Application Performance. After the policy is applied, CWOM executes vertical scaling to allocate more compute resources to the affected Container Pods.
现在，我将在CWOM中为容器创建一个自动化策略，以动态平衡资源以改善和恢复应用程序性能。 应用该策略后，CWOM将执行垂直扩展，以将更多的计算资源分配给受影响的Container Pod。
After the scalings Actions are completed, the average response time of the Online Boutique application is gradually restored, and the Transaction Scorecard is showing Normal transactions again.
扩展操作完成后，将逐渐恢复Online Boutique应用程序的平均响应时间，并且“交易记分卡”再次显示“正常交易”。
Lastly, I wanted to show how the entire AIOps use case can be viewed from a “single pane of glass”. I am leveraging on the REST APIs supported by AppDynamic and CWOM, and some basic NodeJS web programming.
最后，我想展示如何从“单个窗格”查看整个AIOps用例。 我利用了AppDynamic和CWOM支持的REST API，以及一些基本的NodeJS Web编程。
AIOps — Visibility, Insights and Actions — via AppDynamics and CWOM is validated to be working as I expected. What I have shown is based on a container environment setup in a private cloud, but the same use case explained in this article works on any of the public cloud provider managed service such as EKS, GKE or AKS.
通过AppDynamics和CWOM的AIOps(可见性，洞察力和行动)经过验证可正常运行。 我所显示的内容基于私有云中的容器环境设置，但是本文介绍的相同用例适用于任何公共云提供商托管的服务，例如EKS，GKE或AKS。
翻译自: https://medium.com/@jonchin75/digital-transformation-with-aiops-on-multicloud-4802da76e4be
多云在屏幕上怎么册除
2654
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
