I have been working with AWS since 2012, specifically with AWS DevOps. I am speaking about Amazon Web Services when I mention AWS. I am into DevOps, so I have been using a lot of tools recently. For the detection of anomalies, if talking specifically about monitoring, I have been using a lot of tools. Nagios is there, Zabbix was there. But if talking about performance monitoring, New Relic was there, Site24x7 was there. Based on whatever is the requirement, we will deploy those tools. For incident management, it was mostly done earlier by some scripting tools. We would have the shell script to monitor the system and basically send us an alert, and then based on the budget, the company would decide on tools such as Atlassian or a long time back we had tools such as FileZilla or Bugzilla. But nowadays, with most of the companies that I have worked with in the last maybe nine or 10 years, most of them have been using Confluence. Recently, we added ClickUp as one of the tools. Some of them are also using monday.com. Based on the quorum, the tool was decided and incident management tools do help. We also use tools such as PagerDuty and Opsgenie for incident management. Of course, you need to choose the right set of tools for the deployment. Whether you are using this for DNS, whether you are using that for a database or simple application servers, you need to decide on what tools or what services you would want to use for those things. Then based on that, you design it and you decide it. I have not found any negative side to Amazon DevOps Guru. Maybe because of the experience that I have, I would find my way out and find a solution. But I would not say there is any negative side to that. Maybe somebody who has started using that newly could find some negative side, but as of now, all is good. I started out with AWS in 2007. I started with Azure in 2015 on the cloud side. But if talking about specifically DevOps, I started with DevOps on Azure first before going to AWS. If talking about the cloud journey, AWS has been the first cloud. But if talking about DevOps, because in AWS we were still using scripting, Ansible, Chef in the old days, and Puppet. But if talking about a proper tool from the cloud service provider, then Azure DevOps was the first one which I basically tried. I guess most of the services provided by any of these cloud service providers are the same. It is just a change in the names and the way they actually do things. It is just a personal preference. My overall rating for Amazon DevOps Guru is eight out of ten.
I have been working with AWS since 2012, specifically with AWS DevOps. I am speaking about Amazon Web Services when I mention AWS. I am into DevOps, so I have been using a lot of tools recently. For the detection of anomalies, if talking specifically about monitoring, I have been using a lot of tools. Nagios is there, Zabbix was there. But if talking about performance monitoring, New Relic was there, Site24x7 was there. Based on whatever is the requirement, we will deploy those tools. For incident management, it was mostly done earlier by some scripting tools. We would have the shell script to monitor the system and basically send us an alert, and then based on the budget, the company would decide on tools such as Atlassian or a long time back we had tools such as FileZilla or Bugzilla. But nowadays, with most of the companies that I have worked with in the last maybe nine or 10 years, most of them have been using Confluence. Recently, we added ClickUp as one of the tools. Some of them are also using monday.com. Based on the quorum, the tool was decided and incident management tools do help. We also use tools such as PagerDuty and Opsgenie for incident management. Of course, you need to choose the right set of tools for the deployment. Whether you are using this for DNS, whether you are using that for a database or simple application servers, you need to decide on what tools or what services you would want to use for those things. Then based on that, you design it and you decide it. I have not found any negative side to Amazon DevOps Guru. Maybe because of the experience that I have, I would find my way out and find a solution. But I would not say there is any negative side to that. Maybe somebody who has started using that newly could find some negative side, but as of now, all is good. I started out with AWS in 2007. I started with Azure in 2015 on the cloud side. But if talking about specifically DevOps, I started with DevOps on Azure first before going to AWS. If talking about the cloud journey, AWS has been the first cloud. But if talking about DevOps, because in AWS we were still using scripting, Ansible, Chef in the old days, and Puppet. But if talking about a proper tool from the cloud service provider, then Azure DevOps was the first one which I basically tried. I guess most of the services provided by any of these cloud service providers are the same. It is just a change in the names and the way they actually do things. It is just a personal preference. My overall rating for Amazon DevOps Guru is eight out of ten.